With each bus implementing its own DMA configuration callback,
there is no need for bus to explicitly have force_dma in its
global structure. This patch modifies of_dma_configure API to
accept an input parameter which specifies if implicit DMA
configuration is required even when it is not described
It's bus specific aspect to map a given device on the bus and
relevant firmware description of its DMA configuration.
So, this change introduces '/dma_configure/' as bus callback
giving flexibility to busses for implementing its own dma
configuration function.
The change eases the addition of new
This patch series is a continue of discussion from here,
https://patchwork.kernel.org/patch/9986293/
that some users may want to handle all available clocks from device
tree without need to know the detailed clock information likes clock
numbers and names. This is useful in writing some generic dri
Hi Peter,
On 03/21/2018 07:53 AM, Peter Rosin wrote:
> On 2018-03-21 00:24, Vladimir Zapolskiy wrote:
>> Hi Peter,
>>
>> On 03/20/2018 11:31 AM, Peter Rosin wrote:
>>> In preparation for PCA9641 support, convert the mybus and busoff macros
>>> to functions, and in the process prefix them with pca9
Perf list with flags -d and -v print a description (-d) or
a very verbose explanation (-v) of CPU specific counter events.
These descriptions are provided with the json files in
directory pmu-events/arch/s390/*.json.
Display of these descriptions on s390 requires the
corresponding json files.
On
Looks good. Thanks!
regards,
dan carpenter
Check memory allocation result for cachetag in mount option
parsing and fix potential memory leak in the error case.
Signed-off-by: Chengguang Xu
---
fs/9p/v9fs.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/fs/9p/v9fs.c b/fs/9p/v9fs.c
index 8fb89dd..e622f0f 100644
--- a/fs/9p/v9fs
From: Rafael J. Wysocki
Add a new pointer argument to cpuidle_select() and to the ->select
cpuidle governor callback to allow a boolean value indicating
whether or not the tick should be stopped before entering the
selected state to be returned from there.
Make the ladder governor ignore that po
Hi Alexandre,
After merging the rtc tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/rtc/rtc-st-lpc.c: In function 'st_rtc_probe':
drivers/rtc/rtc-st-lpc.c:198:18: warning: unused variable 'tm_check'
[-Wunused-variable]
struct rtc_time tm_check;
On (03/21/18 10:10), Maninder Singh wrote:
> (Added cover letter to avoid much text in patch description)
>
> LZ4 specification defines 2 byte offset length for 64 KB data.
> But in case of ZRAM we compress data per page and in most of
> architecture PAGE_SIZE is 4KB. So we can decide offset lengt
On Tuesday, March 20, 2018 10:03:50 PM CET Doug Smythies wrote:
> Summary: My results with kernel 4.16-rc6 and V8 of the patch set
> are completely different, and now show no clear difference
> (a longer test might reveal something).
Does this mean that you see the "powernightmares" pattern with
* Linus Torvalds wrote:
> And even if you ignore that "maintenance problems down the line" issue
> ("we can fix them when they happen") I don't want to see games like
> this, because I'm pretty sure it breaks the optimized xsave by tagging
> the state as being dirty.
That's true - and it would
Hi Bjorn,
Thanks for the review.
On 03/19/2018 04:14 AM, Bjorn Andersson wrote:
On Wed 14 Mar 02:21 PDT 2018, Sibi S wrote:
+- reg:
+ Usage: required
+ Value type:
+ Definition: must specify the base address and size of the register
+ space.
+
+
Double emp
Hi all,
Today's linux-next merge of the userns tree got a conflict in:
fs/fuse/dev.c
between commits:
dbf107b2a7f3 ("fuse: Remove the buggy retranslation of pids in
fuse_dev_do_read")
c9582eb0ff7d ("fuse: Fail all requests with invalid uids or gids")
8cb08329b080 ("fuse: Support fuse f
The phys has already been initialized when add primary hcd,
including usb2 phys and usb3 phys also if exist, so needn't
re-parse "phys" property again.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 1 +
drivers/usb/host/xhci-plat.c | 1 +
2 files changed, 2 insertions(+)
diff -
On 03/20/2018 09:40 PM, Rajkumar Rampelli wrote:
Add fan device attribute fan1_input in pwm-fan driver
to read speed of fan in rotations per minute.
Signed-off-by: Rajkumar Rampelli
---
V2: Removed generic-pwm-tachometer driver and using pwm-fan driver as per
suggestions
to read fan spee
On Wed, 2018-03-21 at 13:52 +0800, Kathleen Chang wrote:
>
>
> On Fri, 2018-03-16 at 10:51 +0100, Peter Zijlstra wrote:
> > On Thu, Mar 15, 2018 at 03:36:10PM +0800, Kathleen Chang wrote:
> > > hi,
> > >
> > > We found the vruntime might update incorrectly when use rt_mutex.
> >
> > That's n
Hi Niklas,
On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote:
> In order to properly handle 64-bit BARs, we need to know what BAR width
> that was actually set-up by specific pci_epc_set_bar() implementations.
>
> This is done so that we can know if we need to skip a BAR,
> since a 64-bit B
On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote:
> A 64-bit BAR consists of a BAR pair, where the second BAR has the
> upper bits, so we cannot simply call pci_ioremap_bar() on every single
> BAR index.
>
> The second BAR in a BAR pair will not have the IORESOURCE_MEM resource
> flag set
Hi Niklas,
On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote:
> Since a 64-bit BAR consists of a BAR pair, we need to write to both
> BARs in the BAR pair to clear the BAR properly.
>
> Signed-off-by: Niklas Cassel
> ---
> drivers/pci/dwc/pcie-designware-ep.c | 7 +++
> 1 file changed
On 2018-03-21 00:24, Vladimir Zapolskiy wrote:
> Hi Peter,
>
> On 03/20/2018 11:31 AM, Peter Rosin wrote:
>> In preparation for PCA9641 support, convert the mybus and busoff macros
>> to functions, and in the process prefix them with pca9541_. Also prefix
>> remaining chip specific macros with PCA
hi,
Thanks for your feedback.
On Fri, 2018-03-16 at 10:51 +0100, Peter Zijlstra wrote:
> On Thu, Mar 15, 2018 at 03:36:10PM +0800, Kathleen Chang wrote:
> > hi,
> >
> > We found the vruntime might update incorrectly when use rt_mutex.
>
> That's nice, on what kernel?
>
> Also, your email
Hi Niklas,
On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote:
> Since a 64-bit BAR consists of a BAR pair, we need to write to both
> BARs in the BAR pair to setup the BAR properly.
>
> Signed-off-by: Niklas Cassel
> ---
> drivers/pci/dwc/pcie-designware-ep.c | 11 +--
> 1 file ch
On Wednesday 21 March 2018 08:15 AM, Mark Brown wrote:
On Wed, Mar 21, 2018 at 01:30:40PM +1100, Stephen Rothwell wrote:
Caused by commit
363fe37948e2 ("ASoC: amd: dma driver changes for BT I2S controller instance")
I have used the sound-asoc tree from next-20180320 for today
Hi Peter,
At 03/20/2018 08:39 PM, Peter Zijlstra wrote:
On Tue, Mar 20, 2018 at 07:04:30PM +0800, Dou Liyang wrote:
case 1: no | no | no | --> min (setup_possible_cpus, nr_cpu_ids,
setup_max_cpus)
case 2: no | no | yes| --> min (setup_possible_cpus, nr_cpu_ids)
case 3: no | yes | no | -
Update the compatible string for UFS QMP PHY on SDM845.
Signed-off-by: Can Guo
---
Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
b/Documentation/devicetree/bindi
This patch series adds support for UFS QMP PHY on SDM845 and the
compitable string for it. This patch series depends on the current
proposed QMP V3 USB3 UNI PHY support for sdm845 driver [1] and also based
on the DT bindings for the QMP V3 USB3 PHYs based dirver [2]. This series
can only be merged
Add UFS PHY support to make SDM845 UFS work with common PHY framework.
Signed-off-by: Can Guo
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 122 +++-
drivers/phy/qualcomm/phy-qcom-qmp.h | 8 +++
2 files changed, 127 insertions(+), 3 deletions(-)
diff --git a/driver
stfsm_probe() misses error handling of mtd_device_register().
Signed-off-by: Arushi Singhal
---
drivers/mtd/devices/st_spi_fsm.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/devices/st_spi_fsm.c b/drivers/mtd/devices/st_spi_fsm.c
index 7bc29d7..e1aa4f8 1
Resolved checkpatch warning "sizeof t should be sizeof(t)"
issue found by checkpatch.
Signed-off-by: Devang Panchal
---
drivers/misc/eeprom/at25.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/eeprom/at25.c b/drivers/misc/eeprom/at25.c
index 9282ffd..6a7d4a2 10
Hi Peter,
At 03/20/2018 08:37 PM, Peter Zijlstra wrote:
On Tue, Mar 20, 2018 at 07:04:28PM +0800, Dou Liyang wrote:
+ possible_cpus= [s390,x86_64] Use this to set hotpluggable cpus.
+ This option sets possible_cpus bits in cpu_possible_map.
+
On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote:
> If a BAR supports 64-bit width or not depends on the hardware,
> and should thus not depend on sizeof(dma_addr_t).
>
> Since this driver is generic, default to always using BAR width
> of 32-bits. 64-bit BARs can easily be tested by repl
On Tue, Mar 20, 2018 at 06:32:00AM -0700, Guenter Roeck wrote:
> On 03/19/2018 11:04 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.123 release.
> > There are 134 patches in this series, all will be posted as a response
> > to this one. If anyone has any
USB3 hubs don't support global suspend.
USB3 specification 10.10, Enhanced SuperSpeed hubs only support selective
suspend and resume, they do not support global suspend/resume where the
hub downstream facing ports states are not affected.
When system enters hibernation it first enters freeze proc
Thanks Bjorn for the review comments,
On 21/03/18 11:35, Bjorn Andersson wrote:
On Tue 20 Mar 17:28 HKT 2018, Srinivas Kandagatla wrote:
From: Srinivas Kandagatla
This patch adds support to external pcie refclk.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/dts/qcom-apq8064-db600c
On 03/19/2018 07:00 PM, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> There is no point in differentiating between a range for which there
> is not even a directory (and thus entries) and empty entry (pte_none()
> or pmd_none() returns true).
>
> Simply drop the distinction ie remove HMM_P
Hi Joerg,
On Tue, 2018-03-20 at 13:57 -0500, Joerg Roedel wrote:
> On Sun, Mar 18, 2018 at 09:52:54AM +0800, Yong Wu wrote:
> > To avoid adding this complex macro or a new function, I put
> > it in the code and backup its value in the suspend registers.
>
> Missing Signed-off-by.
Signed-off-by a
Since d5d332d3f7e8, a couple of links in scripts/dtc/include-prefixes
are additionally required in order to build device trees with the header
package.
Signed-off-by: Jan Kiszka
---
scripts/package/builddeb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/package/build
Dear Greg,
This is extcon-next pull request for v4.17. I add detailed description of
this pull request on below. Please pull extcon with following updates.
Best Regards,
Chanwoo Choi
The following changes since commit 4a3928c6f8a53fa1aed28ccba227742486e8ddcb:
Linux 4.16-rc3 (2018-02-25 18:50
On 03/19/2018 07:00 PM, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> No functional change, just create one function to handle pmd and one
> to handle pte (hmm_vma_handle_pmd() and hmm_vma_handle_pte()).
>
> Signed-off-by: Jérôme Glisse
> Cc: Evgeny Baskakov
> Cc: Ralph Campbell
> Cc: M
On Tue, Mar 20, 2018 at 09:21:33PM -0700, Figo.zhang wrote:
> suppose that in free_one_page() will try to merge to high order anytime ,
> but now in your patch,
> those merge has postponed when system in low memory status, it is very easy
> let system trigger
> low memory state and get poor perform
Add pwm fan driver support on Tegra186 SoC.
Signed-off-by: Rajkumar Rampelli
---
V2: Removed generic-pwm-tachometer driver dt node and using pwm-fan driver
for reading fan speed.
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/b
The following patches adds support for PWM based Tegra Tachometer driver
which implements PWM capture interface to analyze the PWM signal of a
electronic fan and reports it in periods and duty cycles.
Added fan device attribute fan1_input in pwm-fan driver to monitor the
speed of fan in rotations
(Added cover letter to avoid much text in patch description)
LZ4 specification defines 2 byte offset length for 64 KB data.
But in case of ZRAM we compress data per page and in most of
architecture PAGE_SIZE is 4KB. So we can decide offset length based
on actual offset value. For this we can reser
Tegra Tachometer driver implements PWM capture to measure
period. Enable this driver as a module in the ARM64 defconfig.
Signed-off-by: Rajkumar Rampelli
---
V2: No changes in this patch
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconf
Enable pwm-fan driver to make use of a PWM interface to
read speed of a fan in rotations per minute.
Signed-off-by: Rajkumar Rampelli
---
V2: Added pwm-fan driver support as a loadable module.
Removed generic-pwm-tachometer driver support which was added as part of v1
arch/arm64/configs/de
Add fan device attribute fan1_input in pwm-fan driver
to read speed of fan in rotations per minute.
Signed-off-by: Rajkumar Rampelli
---
V2: Removed generic-pwm-tachometer driver and using pwm-fan driver as per
suggestions
to read fan speed.
Added fan device attribute to report speed of
LZ4 specification defines 2 byte offset length for 64 KB data.
But in case of ZRAM we compress data per page and in most of
architecture PAGE_SIZE is 4KB. So we can decide offset length based
on actual offset value. For this we can reserve 1 bit to decide offset
length (1 byte or 2 byte). 2 byte re
PWM Tachometer driver capture the PWM signal which is output of FAN
in general and provide the period of PWM signal which is converted to
RPM by SW.
Add Tegra Tachometer driver which implements the pwm-capture to
measure period.
Signed-off-by: Rajkumar Rampelli
Signed-off-by: Laxman Dewangan
--
Add support for pwm HW driver which has only capture functionality.
This helps to implement the PWM based Tachometer driver which reads
the PWM output signals from electronic fans.
PWM Tachometer captures the period and duty cycle of the PWM signal
Add conditional checks for callabacks enable(),
The NVIDIA Tegra186 SoC has a Tachometer Controller that analyzes the
PWM signal of a Fan and reports the period value through pwm interface.
Signed-off-by: Rajkumar Rampelli
---
V2: Renamed clock-names/reset-names dt properties values to "tachometer"
Renamed compatible property value to "nv
The NVIDIA Tegra186 SoC has a PWM controller which is
used in FAN control use case.
Signed-off-by: Rajkumar Rampelli
---
V2: no changes in this patch
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra186.dt
Supply Device tree binding documentation for the NVIDIA
Tegra186 SoC's Tachometer Controller
Signed-off-by: Rajkumar Rampelli
---
V2: Renamed compatible string to "nvidia,tegra186-pwm-tachometer"
Renamed dt property values of clock-names and reset-names to "tachometer"
from "tach"
.../
It needs to free of allocated params value in the goto error statement.
Signed-off-by: Ji-Hun Kim
---
Changes since v2:
- add kfree(params) on the error case of the function
- rename unclear goto statement name
- declare the params value at start of the function, so it can be free
end o
On 03/19/2018 07:00 PM, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> User of hmm_vma_fault() and hmm_vma_get_pfns() provide a flags array
> and pfn shift value allowing them to define their own encoding for HMM
> pfn that are fill inside the pfns array of the hmm_range struct. With
> this
There is no failure checking on the param value which will be allocated
memory by kmalloc. Add a null pointer checking statement. Then goto error:
and return -ENOMEM error code when kmalloc is failed.
Signed-off-by: Ji-Hun Kim
---
Changes since v1:
- Return with -ENOMEM directly, instead of got
This patch fixes "5f48f0bd4e368425db4424b9afd1bd251d32367a".
(mm, page_owner: skip unnecessary stack_trace entries)
Because if we skip first two entries then logic of checking count
value as 2 for recursion is broken and code will go in one depth
recursion.
so we need to check only one call of _R
Hi all,
On Wed, 21 Mar 2018 15:31:27 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the ftrace tree got a conflict in:
>
> Documentation/trace/ftrace.txt
> (converted to Documentation/trace/ftrace.rst)
There was another conflict involving
Documentation/trace/events.{txt,r
Cleanup a few messy sections of code by replacing constructs
like `len__ > TMP_BUF_MAX ? TMP_BUF_MAX : len__` with
`min_t(u32, len__, TMP_BUF_MAX)` and naming identifiers
more descriptively (where appropriate).
A few sections were nested pretty deeply and have been
replaced with shallower (but sem
Hi Steven,
Today's linux-next merge of the ftrace tree got a conflict in:
Documentation/trace/ftrace.txt
(converted to Documentation/trace/ftrace.rst)
between commit:
1f198e22bc3a ("trace doc: convert trace/ftrace.txt to rst format")
from the jc_docs tree and commit:
2c1ea60b195d ("tr
Similar to other region attributes, do not emit the persistence_domain
attribute if its contents are empty.
Fixes: 96c3a239054a ("libnvdimm: expose platform persistence attr...")
Cc: Dave Jiang
Signed-off-by: Dan Williams
---
drivers/nvdimm/region_devs.c |7 +++
1 file changed, 7 insert
On 03/19/2018 07:00 PM, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> This code was lost in translation at one point. This properly call
> mmu_notifier_unregister_no_release() once last user is gone. This
> fix the zombie mm_struct as without this patch we do not drop the
> refcount we have
On 03/19/2018 07:00 PM, jgli...@redhat.com wrote:
> From: Ralph Campbell
>
> The hmm_mirror_register() function registers a callback for when
> the CPU pagetable is modified. Normally, the device driver will
> call hmm_mirror_unregister() when the process using the device is
> finished. However,
On Mon, Mar 19, 2018 at 04:52:34PM +, Lorenzo Pieralisi wrote:
> On Thu, Mar 08, 2018 at 02:33:25PM +0100, Niklas Cassel wrote:
> > PCI endpoint fixes to improve the way 64-bit BARs are handled.
> >
> >
> > There are still future improvements that could be made:
> >
> > pci-epf-test.c always
Hi Eric,
On Wed, Mar 14, 2018 at 06:51:39PM -0700, Eric Biggers wrote:
> On Mon, Mar 12, 2018 at 10:29:06PM -0600, Tycho Andersen wrote:
> > We're interested in getting rid of all of the stack allocated arrays in the
> > kernel [1]. This patch removes one in keys by switching to malloc/free.
> > N
Hi Eric,
On Wed, Mar 14, 2018 at 07:21:12PM -0700, Eric Biggers wrote:
> On Mon, Mar 12, 2018 at 10:29:07PM -0600, Tycho Andersen wrote:
> > Similarly to the previous patch, we would like to get rid of stack
> > allocated arrays: https://lkml.org/lkml/2018/3/7/621
> >
> > In this case, we can als
Hello Greg,
Lorenzo is fine with this series
( https://marc.info/?l=linux-kernel&m=152147837619191&w=2 )
However, he wants your ack on this patch before merging.
Could you please have a look at this patch?
Kind regards,
Niklas
On Thu, Mar 08, 2018 at 02:33:30PM +0100, Niklas Cassel wrote:
>
Le mardi 20 mars 2018 à 20:04 +0200, Laurent Pinchart a écrit :
> Hi Nicolas,
>
> On Tuesday, 20 March 2018 19:45:51 EET Nicolas Dufresne wrote:
> > Le mardi 20 mars 2018 à 13:20 +0100, Paul Menzel a écrit :
> > > Dear Linux folks,
> > >
> > >
> > > On the Dell XPS 13 9370, Linux 4.16-rc6 output
On Tue 20 Mar 17:28 HKT 2018, Srinivas Kandagatla wrote:
> From: Srinivas Kandagatla
>
> This patch adds support to external pcie refclk.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> arch/arm/boot/dts/qcom-apq8064-db600c.dts | 27 +++
> 1 file changed, 27 insertions(
Hi Can,
On 3/21/2018 8:12 AM, c...@codeaurora.org wrote:
> On 2018-03-20 19:30, Can Guo wrote:
>> Add UFS PHY support to make SDM845 UFS work with common PHY framework.
>>
>> Signed-off-by: Can Guo
>> ---
>> drivers/phy/qualcomm/phy-qcom-qmp.c | 120
>> +++-
>>
Hi Paul,
Today's linux-next merge of the selinux tree got a conflict in:
security/selinux/hooks.c
between commit:
6b4f3d01052a ("usb, signal, security: only pass the cred, not the secid, to
kill_pid_info_as_cred and security_task_kill")
from the security tree and commit:
6b6bc6205d98 (
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Wednesday, March 21, 2018 6:38 AM
>
> On Mon, 19 Mar 2018 07:51:58 +
> "Tian, Kevin" wrote:
>
> > > From: Shameer Kolothum
> > > Sent: Friday, March 16, 2018 12:35 AM
> > >
> > > This retrieves the reserved regions associate
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Wednesday, March 21, 2018 6:55 AM
>
> On Mon, 19 Mar 2018 08:28:32 +
> "Tian, Kevin" wrote:
>
> > > From: Shameer Kolothum
> > > Sent: Friday, March 16, 2018 12:35 AM
> > >
> > > This series introduces an iova list associate
This patch introduces of_clk_bulk_get_all and clk_bulk_x_all APIs
to users who just want to handle all available clocks from device tree
without need to know the detailed clock information likes clock numbers
and names. This is useful in writing some generic drivers to handle clock
part.
Cc: Steph
This patch introduces the managed version of clk_bulk_get_all.
Cc: Michael Turquette
Cc: Stephen Boyd
Signed-off-by: Dong Aisheng
---
v1->v2:
* new patch
---
drivers/clk/clk-devres.c | 24
include/linux/clk.h | 23 +++
2 files changed, 47 inse
Switching to use clk_bulk API to simplify clock operations.
Cc: Hans de Goede
Cc: Bartlomiej Zolnierkiewicz
Cc: linux-fb...@vger.kernel.org
Cc: Masahiro Yamada
Cc: Stephen Boyd
Signed-off-by: Dong Aisheng
---
v1->v2:
* switch to clk_bulk_get_all from of_clk_bulk_get_all
---
drivers/video/fb
'clock-names' property is optional in DT, so of_clk_bulk_get() is
introduced here to handle this for DT users without 'clock-names'
specified. Later clk_bulk_get_all() will be implemented on top of
it and this API will be kept private until someone proves they need
it because they don't have a stru
This patch series is a continue of discussion from here,
https://patchwork.kernel.org/patch/9986293/
that some users may want to handle all available clocks from device
tree without need to know the detailed clock information likes clock
numbers and names. This is useful in writing some generic dri
On Tue, Mar 20, 2018 at 01:17:14PM -0500, Alan Tull wrote:
> On Tue, Mar 20, 2018 at 2:10 AM, Wu Hao wrote:
> > On Mon, Mar 19, 2018 at 03:10:28PM -0500, Alan Tull wrote:
> >> On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote:
> >>
> >> Hi Hao,
> >>
> >> > From: Xiao Guangrong
> >> >
> >> > User Acc
On Tue, 2018-03-20 at 13:19 +, Wei Yongjun wrote:
> Fix the missing clk_disable_unprepare() before return
> from mtk_phy_init() in the error handling case.
>
> Signed-off-by: Wei Yongjun
> ---
> drivers/phy/mediatek/phy-mtk-tphy.c | 11 +--
> 1 file changed, 9 insertions(+), 2 deleti
Since commit 3af5a67c86a3 ("MIPS: Fix early CM probing") the MT7621
has not been able to boot.
This patched caused mips_cm_probe() to be called before
mt7621.c::proc_soc_init().
prom_soc_init() has a comment explaining that mips_cm_probe()
"wipes out the bootloader config" and means that configu
On Tue, Mar 20 2018, Matt Redfearn wrote:
> Hi Neil,
>
>
> On 20/03/18 08:22, NeilBrown wrote:
>>
>> Further testing showed that the original version of this
>> patch wasn't 100% reliable. Very occasionally the read
>> of SYSC_REG_CHIP_NAME0 returns garbage. Repeating the
>> read seems to be re
On Tue, Mar 20, 2018 at 03:32:34PM -0500, Alan Tull wrote:
> On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote:
>
> Hi Hao,
>
> Elsewhere we discussed moving #defines used only in this driver either
> to this .c file or to a similarly named .h file. A couple minor
> things below.
Hi Alan,
Yes, I
DIN pin of SPI-NOR muxed with I2C3_SDA which connected to one gpio expand
chip, thus have to disable all those module which compacted by those gpios
if enable SPI-NOR support on Sabreauto board.
Signed-off-by: Robin Gong
---
arch/arm/boot/dts/Makefile | 2 ++
arch/arm/boot/dts
2018-03-21 1:11 GMT+08:00 Palmer Dabbelt :
> On Thu, 15 Mar 2018 01:50:40 PDT (-0700), z...@andestech.com wrote:
>>
>> These patches resolve the some issues of loadable module.
>> - symbol out of ranges
>> - unknown relocation types
>>
>> The reference of external variable and function symbols
The Allwinner H6 CCU has a "HDMI Slow Clock", which is currently missing
in the ccu-sun50i-h6 driver.
Add this missing clock to the driver.
Fixes: 542353ea ("clk: sunxi-ng: add support for the Allwinner H6 CCU")
Signed-off-by: Icenowy Zheng
---
Changes in v2:
- Rearrange clock slice numbers.
d
On Wed, Mar 21, 2018 at 01:30:40PM +1100, Stephen Rothwell wrote:
> Caused by commit
> 363fe37948e2 ("ASoC: amd: dma driver changes for BT I2S controller
> instance")
> I have used the sound-asoc tree from next-20180320 for today.
Dropped.
signature.asc
Description: PGP signature
On Mon, Mar 19, 2018 at 04:22:55PM -0700, Matthias Kaehlcke wrote:
> arch/x86/mm/pti.o: warning: objtool: pti_init() falls through to next
> function pti_user_pagetable_walk_pmd()
> s/debugfs/file.o: warning: objtool: full_proxy_llseek() falls through to next
> function full_proxy_read()
> fs/debu
On 2018-03-20 19:30, Can Guo wrote:
Add UFS PHY support to make SDM845 UFS work with common PHY framework.
Signed-off-by: Can Guo
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 120
+++-
drivers/phy/qualcomm/phy-qcom-qmp.h | 8 +++
2 files changed, 126 insertions
On Fri, Mar 16, 2018 at 06:09:11PM -0700, David Collins wrote:
> Introduce bindings for RPMh regulator devices found on some
> Qualcomm Technlogies, Inc. SoCs. These devices allow a given
Please use subject lines matching the style for the subsystem. This
makes it easier for people to identify r
On 2018-03-20 19:30, Can Guo wrote:
This patch series adds support for UFS QMP PHY on SDM845 and updates
the
compitable string for it.
Can Guo (2):
phy: Add QMP phy based UFS phy support for sdm845
dt-bindings: phy-qcom-qmp: Update UFS phy compitable string for
sdm845
.../devicetree/bin
On 2018-03-20 19:30, Can Guo wrote:
Update the compatible string for UFS QMP PHY on SDM845.
Signed-off-by: Can Guo
---
Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/phy/qcom-qmp-phy
On 03/15/2018 12:47 PM, John Garry wrote:
> On 15/03/2018 15:53, William Cohen wrote:
>> On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote:
>>> On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote:
On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote:
> Hi Will Cohen,
>
> On Wed, Mar
DIN pin of SPI-NOR muxed with I2C3_SDA which connected to one gpio expand
chip, thus have to disable all those module which compacted by those gpios
if enable SPI-NOR support on Sabreauto board.
Signed-off-by: Robin Gong
---
arch/arm/boot/dts/Makefile | 2 ++
arch/arm/boot/dts
From: Tom Zanussi
The ring_buffer event can provide a timestamp that may be useful to
various triggers - pass it into the handlers for that purpose.
Link:
http://lkml.kernel.org/r/6de592683b59fa70ffa5d43d0109896623fc1367.1516069914.git.tom.zanu...@linux.intel.com
Signed-off-by: Tom Zanussi
Si
From: Tom Zanussi
Add a new option flag indicating whether or not the ring buffer is in
'absolute timestamp' mode.
Currently this is only set/unset by hist triggers that make use of a
common_timestamp. As such, there's no reason to make this writeable
for users - its purpose is only to allow us
/soc/amd/acp-pcm-dma.c:1049:8: error: 'I2S_SP_INSTANCE' undeclared (first
use in this function); did you mean 'I2S_BT_INSTANCE'?
case I2S_SP_INSTANCE:
^~~
I2S_BT_INSTANCE
Caused by commit
363fe37948e2 ("ASoC: amd: dma driver changes for BT I2S controller instance")
I have used the sound-asoc tree from next-20180320 for today.
--
Cheers,
Stephen Rothwell
pgpHM3jB3z8xI.pgp
Description: OpenPGP digital signature
From: Tom Zanussi
Define a new function, tracing_set_time_stamp_abs(), which can be used
to enable or disable the use of absolute timestamps rather than time
deltas for a trace array.
Only the interface is added here; a subsequent patch will add the
underlying implementation.
Link:
http://lkml
From: Vedang Patel
We now have the logic to detect and remove duplicates in the
tracing_map hash table. The code which merges duplicates in the
histogram is redundant now. So, modify this code just to detect
duplicates. The duplication detection code is still kept to ensure
that any rare race con
From: Vedang Patel
A duplicate in the tracing_map hash table is when 2 different entries
have the same key and, as a result, the key_hash. This is possible due
to a race condition in the algorithm. This race condition is inherent to
the algorithm and not a bug. This was fine because, until now, w
1 - 100 of 973 matches
Mail list logo
