On Sat, Oct 19, 2019 at 01:01:35PM +0200, Torsten Duwe wrote:
> Hi Mark!
Hi Torsten!
> On Fri, 18 Oct 2019 18:41:02 +0100 Mark Rutland
> wrote:
>
> > In the process of reworking this I spotted some issues that will get
> > in the way of livepatching. Notably:
> >
> > * When modules can be loa
Dne 21.10.2019 v 13:11 Pali Rohár napsal(a):
> Are you going to add support also for TexFAT? Or at least for more two
> FAT tables (like is used in FAT32)?
>
Just a small note here, differences between FAT and exFAT:
1) Contiguous files get a special treatment by exFAT: they do not use the FA
On Mon, 21 Oct 2019, Lee Jones wrote:
> On Mon, 21 Oct 2019, Daniel Thompson wrote:
>
> > On Mon, Oct 21, 2019 at 11:58:14AM +0100, Lee Jones wrote:
> > > In most contexts '-1' doesn't really mean much to the casual observer.
> > > In almost all cases, it's better to use a human readable define.
When assiging and testing taskstats in taskstats_exit() there's a race
when writing and reading sig->stats when a thread-group with more than
one thread exits:
cpu0:
thread catches fatal signal and whole thread-group gets taken down
do_exit()
do_group_exit()
taskstats_exit()
taskstats_tgid_all
On Mon, 21 Oct 2019, Daniel Thompson wrote:
> On Mon, Oct 21, 2019 at 11:58:14AM +0100, Lee Jones wrote:
> > In most contexts '-1' doesn't really mean much to the casual observer.
> > In almost all cases, it's better to use a human readable define. In
> > this case PLATFORM_DEVID_* defines have a
On Fri 18 Oct 2019 at 09:14, Jian Hu wrote:
> The A1 PLL design is different with previous SoCs. The PLL
> internal analog modules Power-on sequence is different
> with previous, and thus requires a strict register sequence to
> enable the PLL. Unlike the previous series, the maximum frequency
On Mon, Oct 21, 2019 at 1:13 PM Pali Rohár wrote:
> On Monday 21 October 2019 13:08:07 Maurizio Lombardi wrote:
> > Dne 21.10.2019 v 12:54 Pali Rohár napsal(a):
> Maurizio, thank you for reference! I have not caught this Samsung
> activity yet! So we now we have +1 for count of exFAT drivers.
Thi
In cases like suspend-to-disk and suspend-to-ram, a large number of CPU
cores need to be shut down. At present, the CPU hotplug operation is
serialised, and the CPU cores can only be shut down one by one. In this
process, if PSCI affinity_info() does not return LEVEL_OFF quickly,
cpu_psci_cpu_kill(
On Mon, Oct 21, 2019 at 12:58 PM Lee Jones wrote:
>
> MFD currently has one over-complicated user. CS5535 uses a mixture of
> cell cloning, reference counting and subsystem-level call-backs to
> achieve its goal of requesting an IO memory region only once across 3
> consumers. The same can be ac
Dear Horde Users
Your Horde mailbox has exceeded the 2GB capacity as defined by the email
administrator. So your mailbox is currently running on 2.30GB, as such,
you
will not been able to send or receive new messages until you update your
horde mailbox by clicking on the link:
http://hordemail
Thanks Lee for taking time to review.
I agree with most of the style related comments, will fix them in next
version. For others I have replied it inline.
On 21/10/2019 11:46, Lee Jones wrote:
On Fri, 18 Oct 2019, Srinivas Kandagatla wrote:
Qualcomm WCD9340/WCD9341 Codec is a standalone Hi-
On 21.10.2019 13:27, Peter Zijlstra wrote:
> On Fri, Oct 18, 2019 at 12:42:44PM +0300, Alexey Budankov wrote:
>> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
>> index 61448c19a132..60bf17af69f0 100644
>> --- a/include/linux/perf_event.h
>> +++ b/include/linux/perf_event.h
On Mon, Oct 21, 2019 at 06:52:16PM +0800, Yunfeng Ye wrote:
> In cases like suspend-to-disk and suspend-to-ram, a large number of CPU
> cores need to be shut down. At present, the CPU hotplug operation is
> serialised, and the CPU cores can only be shut down one by one. In this
> process, if PSCI a
On Mon, Oct 21, 2019 at 02:39:18PM +0800, Dilip Kota wrote:
> Add YAML shcemas for PCIe RC controller on Intel Gateway SoCs
s/shcemas/schemas/
> which is Synopsys DesignWare based PCIe core.
The revision history below doesn't need to be in the commit mesage and
so you should add a '---' before t
[+Cc Will]
On Mon, Oct 21, 2019 at 03:34:07AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d724f94f x86, kcsan: Enable KCSAN for x86
> git tree: https://github.com/google/ktsan.git kcsan
> console output: https://syzkaller.appspot.com/x/log.txt
Hi,
On Wed, Oct 16, 2019 at 10:54:27PM +0800, Chen-Yu Tsai wrote:
> On Wed, Oct 16, 2019 at 10:49 PM Maxime Ripard wrote:
> > On Sat, Oct 12, 2019 at 01:05:24PM -0700, Alistair Francis wrote:
> > > Follow what the sun50i-a64-pine64.dts does and expose all 5 serial
> > > connections.
> > >
> > > S
On Mon, Oct 21, 2019 at 11:58:14AM +0100, Lee Jones wrote:
> In most contexts '-1' doesn't really mean much to the casual observer.
> In almost all cases, it's better to use a human readable define. In
> this case PLATFORM_DEVID_* defines have already been provided for this
> purpose.
>
> While w
Hi Jernej,
I found something odd in the compliance output:
On 10/17/19 8:37 PM, Jernej Skrabec wrote:
> Starting with H3, Allwinner began to include standalone deinterlace
> core in multimedia oriented SoCs. This patch series introduces support
> for it. Note that new SoCs, like H6, have radicall
Zhenzhong Duan writes:
> There are cases where a guest tries to switch spinlocks to bare metal
> behavior (e.g. by setting "xen_nopvspin" on XEN platform and
> "hv_nopvspin" on HYPER_V).
>
> That feature is missed on KVM, add a new parameter "nopvspin" to disable
> PV spinlocks for KVM guest.
>
>
On 10/17/19 8:37 PM, Jernej Skrabec wrote:
> Allwinner H3 SoC contains deinterlace unit, which has several modes of
> operation - bypass, weave, bob and mixed (advanced) mode. I don't know
> how mixed mode works, but according to Allwinner it gives best results,
> so they use it exclusively. Curren
On Monday 21 October 2019 13:08:07 Maurizio Lombardi wrote:
> Dne 21.10.2019 v 12:54 Pali Rohár napsal(a):
> > Plus there is new version of
> > this out-of-tree Samsung's exfat driver called sdfat which can be found
> > in some Android phones.
>
> [...]
>
> >
> > About that one implementation f
On Friday 18 October 2019 15:18:39 Konstantin Komarov wrote:
> Recently exFAT filesystem specification has been made public by Microsoft
> (https://docs.microsoft.com/en-us/windows/win32/fileio/exfat-specification).
> Having decades of expertise in commercial file systems development, we at
> Par
to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Guido-G-nther/dt-bindings-display-bridge-Add-binding-for-NWL-mipi-dsi-host-controller/20191021-180825
base: https://git.kernel.org/pub/scm/linux/kern
On Mon, Oct 21, 2019 at 11:58:15AM +0100, Lee Jones wrote:
> The current implementation abuses the platform 'id' mfd_cell member
> to index into the correct resources entry. If we place all cells
> into their numbered slots, we can cycle through all the cell entries
> and only process the populate
On Sun, Oct 20, 2019 at 03:42:29PM +0200, meg...@megous.com wrote:
> From: Ondrej Jirman
>
> Enable Allwinner's USB 3.0 phy and the host controller. Orange Pi 3
> board has GL3510 USB 3.0 4-port hub connected to the SoC's USB 3.0
> port. All four ports are exposed via USB3-A connectors. VBUS is
>
On Sun, Oct 20, 2019 at 03:42:27PM +0200, meg...@megous.com wrote:
> From: Icenowy Zheng
>
> Allwinner H6 SoC contains a USB3 PHY (with USB2 DP/DM lines also
> controlled).
>
> Add a driver for it.
>
> The register operations in this driver is mainly extracted from the BSP
> USB3 driver.
>
> Signe
Dne 21.10.2019 v 12:54 Pali Rohár napsal(a):
> Plus there is new version of
> this out-of-tree Samsung's exfat driver called sdfat which can be found
> in some Android phones.
[...]
>
> About that one implementation from Samsung, which was recently merged
> into staging tree, more people wro
On 10/20/19 11:14 PM, Vinod Koul wrote:
On 16-09-19, 14:09, Pierre-Louis Bossart wrote:
Prepare for future PM support and fix error handling by disabling
interrupts as needed.
Signed-off-by: Pierre-Louis Bossart
---
drivers/soundwire/cadence_master.c | 18 --
drivers/soundwi
On 10/20/19 11:04 PM, Vinod Koul wrote:
On 16-09-19, 14:09, Pierre-Louis Bossart wrote:
Provide debugfs capability to kick link and devices into hard-reset
(as defined by MIPI). This capability is really useful when some
devices are no longer responsive and/or to check the software handling
of r
In the DAI link "Capture PCM", the FE DAI "Capture Pin" supports 4-channel
capture but the BE DAI supports only 2-channel capture. To fix the channel
mismatch, we need to enable the runtime channel merge for this DAI link.
Hi Pierre,
This patch is for the same issue discussed in the followi
On Mon, Oct 21, 2019 at 3:44 AM Tomi Valkeinen wrote:
>
> On 18/10/2019 16:05, Adam Ford wrote:
> > The OMAP36xx and AM/DM37x TRMs say that the maximum divider for DSS fclk
> > (in CM_CLKSEL_DSS) is 32. Experimentation shows that this is not
> > correct, and using divider of 32 breaks DSS with a f
On Sun, Oct 20, 2019 at 03:42:26PM +0200, meg...@megous.com wrote:
> From: Ondrej Jirman
>
> The new Allwinner H6 SoC contains a USB3 PHY that is wired to the
> external USB3 pins of the SoC.
>
> Add a device tree binding for the PHY.
>
> Signed-off-by: Ondrej Jirman
> ---
> .../phy/allwinner,su
On Mon, Oct 21, 2019 at 11:47:36AM +0200, Julia Lawall wrote:
>
>
> On Mon, 21 Oct 2019, Suwan Kim wrote:
>
> > On Sat, Oct 19, 2019 at 07:49:29PM +0200, Julia Lawall wrote:
> > > Is it guaranteed that if usb_pipetype(urb->pipe) == PIPE_ISOCHRONOUS (line
> > > 123) is true on one iteration, then
MFD currently has one over-complicated user. CS5535 uses a mixture of
cell cloning, reference counting and subsystem-level call-backs to
achieve its goal of requesting an IO memory region only once across 3
consumers. The same can be achieved by handling the region centrally
during the parent dev
On 17-10-19, 10:48, Stephen Boyd wrote:
> > > > diff --git a/drivers/clk/qcom/gcc-sm8150.c
> > > > b/drivers/clk/qcom/gcc-sm8150.c
> > > > index 12ca2d14797f..13d4d14a5744 100644
> > > > --- a/drivers/clk/qcom/gcc-sm8150.c
> > > > +++ b/drivers/clk/qcom/gcc-sm8150.c
> > > > @@ -1616,6 +1616,38 @@
IO regions are now requested and released by this device's parent.
Signed-off-by: Lee Jones
---
arch/x86/platform/olpc/olpc-xo1-pm.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/arch/x86/platform/olpc/olpc-xo1-pm.c
b/arch/x86/platform/olpc/olpc-xo1-pm.c
index e1a32062a375..0fc57b597
Prior to this patch, IO regions were requested via an MFD subsytem-level
.enable() call-back and similarly released by a .disable() call-back.
Double requests/releases were avoided by a centrally handled usage count
mechanism.
This complexity can all be avoided by handling IO regions only once dur
Most of the complexity of mfd_platform_add_cell() has been removed. The
only functionality left duplicates cell memory into the child's platform
device. Since it's only a few lines, moving it to the main thread and
removing the superfluous function makes sense.
Signed-off-by: Lee Jones
---
drive
In most contexts '-1' doesn't really mean much to the casual observer.
In almost all cases, it's better to use a human readable define. In
this case PLATFORM_DEVID_* defines have already been provided for this
purpose.
While we're here, let's be specific about the 'MFD devices' which
failed. It
The MFD implementation for reference counting was complex and unnecessary.
There was only one bona fide user which has now been converted to handle
the process in a different way. Any future resource protection, shared
enablement functions should be handed by the parent device, rather than
through
The current implementation abuses the platform 'id' mfd_cell member
to index into the correct resources entry. If we place all cells
into their numbered slots, we can cycle through all the cell entries
and only process the populated ones which avoids this behaviour.
Signed-off-by: Lee Jones
---
CS5535 is the only user of mfd_clone_cell(). It makes more sense to
register child devices in the traditional way and remove the quite
bespoke mfd_clone_cell() call from the MFD API.
Signed-off-by: Lee Jones
---
drivers/mfd/cs5535-mfd.c | 24 ++--
1 file changed, 18 insertio
If a child device calls mfd_cell_{en,dis}able() without an appropriate
call-back being set, we are likely to encounter a panic. Avoid this
by adding suitable checking.
Signed-off-by: Lee Jones
---
drivers/mfd/mfd-core.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/mfd
Providing a subsystem-level API helper seems over-kill just to save a
few lines of C-code. Previous commits saw us convert mfd_clone_cell()'s
only user over to use a more traditional style of MFD child-device
registration. Now we can remove the superfluous helper from the MFD API.
Signed-off-by:
On 21-10-19, 11:27, Sudeep Holla wrote:
> I just tested now with today's linux-pm/bleeding-edge branch.
> And even if I move cancel_work_sync just after freq_qos_remove_notifier,
> it works fine now. It was not the case on Friday.
>
> Is that what you wanted to check or something else ?
>
> Regar
On 18-10-19, 11:37, Sudeep Holla wrote:
> Hi,
>
> Since vexpress-spc is the sole user of arm_big_little cpufreq driver,
> there's no point in keeping it separate anymore. I wanted to post these
> patches for ages but kept postponing for no reason.
>
> Regards,
> Sudeep
>
> v1->v2:
> - gene
On Sunday 20 October 2019 20:08:20 Richard Weinberger wrote:
> On Sat, Oct 19, 2019 at 10:33 AM Konstantin Komarov
> wrote:
> >
> > Recently exFAT filesystem specification has been made public by Microsoft
> > (https://docs.microsoft.com/en-us/windows/win32/fileio/exfat-specification).
> > Having
In cases like suspend-to-disk and suspend-to-ram, a large number of CPU
cores need to be shut down. At present, the CPU hotplug operation is
serialised, and the CPU cores can only be shut down one by one. In this
process, if PSCI affinity_info() does not return LEVEL_OFF quickly,
cpu_psci_cpu_kill(
On Wed, Oct 16, 2019 at 03:07:28PM +, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The Kontron N6x1x SoMs all use uart4 as a debug serial interface.
> Therefore we set in the 'chosen' node.
>
> Signed-off-by: Frieder Schrempf
> ---
> arch/arm/boot/dts/imx6ul-kontron-n6x1x-som-commo
Hi Benoit,
This series looks good to me. I had just one small comment on patch 7
and a comment on patch 19.
Just post a v2 for just patch 7/19 and post a patch 20/19 for the requested
MAINTAINERS change.
Once I have Rob's Acks I can merge this.
Regards,
Hans
On 10/18/19 5:34 PM, Benoi
On 10/18/19 5:34 PM, Benoit Parrot wrote:
> Convert ti-cal.txt to ti,cal.yaml.
>
> Signed-off-by: Benoit Parrot
Can you add this bindings file to MAINTAINERS as well in a separate patch?
Thanks!
Hans
> ---
> .../devicetree/bindings/media/ti,cal.yaml | 186 ++
> ..
On Fri, 18 Oct 2019, Srinivas Kandagatla wrote:
> Qualcomm WCD9340/WCD9341 Codec is a standalone Hi-Fi audio codec IC.
>
> This codec has integrated SoundWire controller, pin controller and
> interrupt controller.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> drivers/mfd/Kconfig
Hi Gustavo Pimentel,
On 10/21/2019 4:29 PM, Gustavo Pimentel wrote:
Hi
On Mon, Oct 21, 2019 at 7:39:19, Dilip Kota
wrote:
Add support to PCIe RC controller on Intel Gateway SoCs.
PCIe controller is based of Synopsys DesignWare pci core.
Intel PCIe driver requires Upconfig support, fast trai
On Fri 18 Oct 2019 at 09:14, Jian Hu wrote:
> Add the documentation to support Amlogic A1 clock driver,
> and add A1 clock controller bindings.
>
> Signed-off-by: Jian Hu
> ---
> .../devicetree/bindings/clock/amlogic,a1-clkc.yaml | 143
> +
Those are 2 different controller
On Wed, Oct 16, 2019 at 03:07:36PM +, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> Add the compatibles for Kontron i.MX6UL N6311 SoM and boards and
> the compatibles for Kontron i.MX6ULL N6411 SoM and boards.
>
> Signed-off-by: Frieder Schrempf
> ---
> Documentation/devicetree/bind
On Wed, Oct 16, 2019 at 03:07:28PM +, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The 'N6311 S' and the 'N6411 S' are similar to the Kontron 'N6310 S'
> evaluation kit boards. Instead of the N6310 SoM, they feature a N6311
> or N6411 SoM.
>
> Signed-off-by: Frieder Schrempf
> ---
>
On 17/10/2019 16.49, Sekhar Nori wrote:
> On 17/10/19 4:39 PM, Sekhar Nori wrote:
>> On 30/08/19 3:52 PM, Peter Ujfalusi wrote:
>>> The codec driver needs correct regulators in order to probe.
>>> Both VCC_3V3 and VCC_1V8 is always on fixed regulators on the board.
>>>
>>> Signed-off-by: Peter U
Compliment of the day,
I am Mr.Philip.Kabore I Have a Business Proposal of $5.3 million For
You. I am aware of the unsafe nature of the internet, and was
compelled to use this medium due to the nature of this project.
I have access to very vital information that can be used to transfer
this huge
On Thu, Oct 17, 2019 at 07:57:56PM +0530, Abhishek Shah wrote:
> Hi Lorenzo,
>
> Please see my comments inline:
>
> On Tue, Oct 15, 2019 at 10:13 PM Lorenzo Pieralisi
> wrote:
> >
> > On Fri, Sep 06, 2019 at 09:28:13AM +0530, Abhishek Shah wrote:
> > > Invalidate PAXB inbound/outbound address ma
On 10/18/19 5:34 PM, Benoit Parrot wrote:
> Apply Errata i913 every time the functional clock is enabled.
> This should take care of suspend/resume case as well.
>
> Signed-off-by: Benoit Parrot
> Signed-off-by: Jyri Sarha
> ---
> drivers/media/platform/ti-vpe/cal.c | 56 ++
On Wed, Oct 16, 2019 at 03:07:25PM +, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The baseboard for the Kontron N6310 SoM is also used for other SoMs
> such as N6311 and N6411. In order to share the code, we move the
> definitions of the baseboard to a separate dtsi file.
>
> Signed
On Mon, Oct 21, 2019 at 09:59:42AM +0200, Ingo Molnar wrote:
>
> * Alexey Budankov wrote:
>
> > + /*
> > +* PMU specific parts of task perf context may require
> > +* additional synchronization, at least for proper Intel
> > +
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
b/arch/arm64/boot/dts/qcom/msm8996.dtsi
index 87f4d9c1b0d4c
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/qcs404.dtsi
b/arch/arm64/boot/dts/qcom/qcs404.dtsi
index a97eeb4569c00..b6a4e60739362 100
Hide the details of how to convert values read from TSENS HW to mCelsius
behind a function. All versions of the IP can be supported as a result.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
---
drivers/thermal/qcom/tsens-common.c | 49 -
1 file changed, 35
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
Tested-by: Brian Masney
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
b/arch/arm/boot/dts/qcom-msm8974.dtsi
index 33c534370f
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
b/arch/arm64/boot/dts/qcom/msm8916.dtsi
index 8686e101905cc..807f86a4535e0
Depending on the IP version, TSENS supports upper, lower and critical
threshold interrupts. We only add support for upper and lower threshold
interrupts for now.
TSENSv2 has an irq [status|clear|mask] bit tuple for each sensor while
earlier versions only have a single bit per sensor to denote stat
Daniel, only patch 15 needs to be changed in the tree being submitted
to linux-next. But here is the entire series for completeness.
Hi Thermal and MSM maintainers,
I believe this series is now ready to be merged. The DT bindings and driver
changes should go through the thermal tree and the chang
There are two fields - id and hw_id - to track what sensor an action was
to performed on. This was because the sensors connected to a TSENS IP
might not be contiguous i.e. 1, 2, 4, 5 with 3 being skipped.
This causes confusion in the code which uses hw_id sometimes and id
other times (tsens_get_te
Move platform_set_drvdata up to avoid an extra 'if (ret)' check after
the call to tsens_register.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
Reviewed-by: Daniel Lezcano
---
drivers/thermal/qcom/tsens.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/driv
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi
b/arch/arm64/boot/dts/qcom/msm8998.dtsi
i
msm8974 has 11 sensors connected to a single TSENS IP. Define a thermal
zone for each of those sensors to expose the temperature of each zone.
Signed-off-by: Amit Kucheria
Tested-by: Brian Masney
Reviewed-by: Stephen Boyd
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 90 +++
msm8916 uses sensors 0, 1, 2, 4 and 5. Sensor 3 is NOT used. Fixup the
device tree so that the correct sensor ID is used and as a result we can
actually check the temperature for the cpu2_3 sensor.
Signed-off-by: Amit Kucheria
Reviewed-by: Daniel Lezcano
Reviewed-by: Stephen Boyd
---
arch/arm6
Older IP only supports the 'uplow' interrupt, but newer IP supports
'uplow' and 'critical' interrupts. Document interrupt support in the
tsens driver by converting over to a YAML schema.
Suggested-by: Stephen Boyd
Signed-off-by: Amit Kucheria
Reviewed-by: Rob Herring
---
.../bindings/thermal/q
Dump some basic version info and sensor details into debugfs. Example
from qcs404 below:
--(/sys/kernel/debug) $ ls tsens/
4a9000.thermal-sensor version
--(/sys/kernel/debug) $ cat tsens/version
1.4.0
--(/sys/kernel/debug) $ cat tsens/4a9000.thermal-sensor/sensors
max: 11
num: 10
idslo
Printing the function name when enabling debugging makes logs easier to
read.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
Reviewed-by: Daniel Lezcano
---
drivers/thermal/qcom/tsens-common.c | 8
drivers/thermal/qcom/tsens.c| 6 +++---
2 files changed, 7 insertions(+
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
b/arch/arm64/boot/dts/qcom/sdm845.
On 2019/10/21 下午6:00, Zhu, Lingshan wrote:
On 10/16/2019 4:40 PM, Jason Wang wrote:
On 2019/10/16 上午9:30, Zhu Lingshan wrote:
This commit introduced ifcvf_base layer, which handles IFC VF NIC
hardware operations and configurations.
It's better to describe the difference between ifc vf an
Hi Gustavo Pimentel,
On 10/21/2019 4:40 PM, Gustavo Pimentel wrote:
On Mon, Oct 21, 2019 at 7:39:20, Dilip Kota
wrote:
PCIe RC driver on Intel Gateway SoCs have a requirement
of changing link width and speed on the fly.
So add the sysfs attributes to show and store the link
properties.
Add th
On Mon, Oct 21, 2019 at 02:14:51AM +0200, Rafael J. Wysocki wrote:
> On Fri, Oct 18, 2019 at 1:06 PM Sudeep Holla wrote:
> >
> > On Fri, Oct 18, 2019 at 12:37:51PM +0200, Rafael J. Wysocki wrote:
> > > On Friday, October 18, 2019 12:19:24 PM CEST Sudeep Holla wrote:
> > > > On Fri, Oct 18, 2019 at
Hello,
syzbot found the following crash on:
HEAD commit:d724f94f x86, kcsan: Enable KCSAN for x86
git tree: https://github.com/google/ktsan.git kcsan
console output: https://syzkaller.appspot.com/x/log.txt?x=13eab79f60
kernel config: https://syzkaller.appspot.com/x/.config?x=c0906
Just a meta-comment...
> Am 21.10.2019 um 12:15 schrieb Alexandre Belloni
> :
>
> Hi,
>
> The subject line is weird, how is it related to rc5t583?
>
> On 21/10/2019 07:41:04+0200, Andreas Kemnade wrote:
>> config RTC_DRV_S35390A
>> tristate "Seiko Instruments S-35390A"
>> select BITR
On Wed, Oct 16, 2019 at 03:07:21PM +, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The N6311 and the N6411 SoM are similar to the Kontron N6310 SoM.
> They are pin-compatible, but feature a larger RAM and NAND flash
> (512MiB instead of 256MiB). Further, the N6411 has an i.MX6ULL SoC,
On Mon, Oct 21, 2019 at 07:45:51AM +0530, Viresh Kumar wrote:
> On 18-10-19, 12:06, Sudeep Holla wrote:
> > Callstack is:
> >
> > (cpufreq_notifier_max)
> > (notifier_call_chain)
> > (blocking_notifier_call_chain)
> > (pm_qos_update_target)
> > (freq_qos_apply)
> > (freq_qos_remove_request)
> > (cp
On Wed, Oct 16, 2019 at 03:07:19PM +, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The Kontron N6311 and N6411 SoMs are very similar to N6310. In
> preparation to add support for them, we move the common nodes to a
> separate file imx6ul-kontron-n6x1x-som-common.dtsi.
>
> Signed-off-
On Mon 21-10-19 10:48:06, Mel Gorman wrote:
> Deferred memory initialisation updates zone->managed_pages during
> the initialisation phase but before that finishes, the per-cpu page
> allocator (pcpu) calculates the number of pages allocated/freed in
> batches as well as the maximum number of pages
On Fri, Oct 18, 2019 at 12:42:44PM +0300, Alexey Budankov wrote:
> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> index 61448c19a132..60bf17af69f0 100644
> --- a/include/linux/perf_event.h
> +++ b/include/linux/perf_event.h
> @@ -409,6 +409,13 @@ struct pmu {
>*/
>
rk3399-roc-pc has three gpio LEDs, enable them.
Signed-off-by: Markus Reichl
---
.../arm64/boot/dts/rockchip/rk3399-roc-pc.dts | 41 +++
1 file changed, 41 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dts
b/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dts
From: Nikhil Badola
Correct NULL pointer checking for endpoint descriptor
before it gets dereferenced
Signed-off-by: Nikhil Badola
Signed-off-by: Ran Wang
Reviewed-by: Peter Chen
---
drivers/usb/gadget/udc/fsl_udc_core.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
On Thu, Oct 17, 2019 at 05:27:46PM -0700, Stephane Eranian wrote:
> This patch complements the following commit:
> 7fa343b7fdc4 ("perf/core: Fix corner case in perf_rotate_context()")
>
> The fix from Song addresses the consequences of the problem but
> not the cause. This patch fixes the causes a
From: Nikhil Badola
Check memory resource existence before releasing it to avoid NULL
pointer dereference
Signed-off-by: Nikhil Badola
Reviewed-by: Ran Wang
Reviewed-by: Peter Chen
---
drivers/usb/gadget/udc/fsl_udc_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/d
On Thu, Oct 17, 2019 at 12:05:29PM +0200, Marek Szyprowski wrote:
> From: Maciej Falkowski
>
> Convert Samsung Exynos Odroid XU3/XU4 audio complex with MAX98090 codec
> to newer dt-schema format.
>
> 'clocks' property is unneeded in the bindings and is left undefined in
> 'properties'.
>
> 'sa
On 2019/10/21 下午5:57, Zhu, Lingshan wrote:
On 10/16/2019 4:45 PM, Jason Wang wrote:
On 2019/10/16 上午9:30, Zhu Lingshan wrote:
+ */
+#define IFCVF_TRANSPORT_F_START 28
+#define IFCVF_TRANSPORT_F_END 34
+
+#define IFC_SUPPORTED_FEATURES \
+ ((1ULL << VIRTIO_NET_F_MAC) | \
From: Nikhil Badola
Remove unused variable td_complete
Signed-off-by: Nikhil Badola
Reviewed-by: Ran Wang
Reviewed-by: Peter Chen
---
drivers/usb/gadget/udc/fsl_udc_core.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/usb/gadget/udc/fsl_udc_core.c
b/drivers
arm_big_little cpufreq driver was designed as a generic big little
driver that could be used by any platform and make use of bL switcher.
Over years alternate solutions have been designed and merged to deal
with bL/HMP systems like EAS.
Also since no other driver made use of generic arm_big_little
From: Peng Fan
We should not rely on bootloader to configure the phy reset.
So introduce phy-reset-gpios property to let Linux handle phy reset
itself.
Signed-off-by: Peng Fan
---
V2:
U-Boot->bootloader
arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dts | 1 +
1 file changed, 1 insertion(+)
From: Peng Fan
We should not rely on bootloader to configure the phy reset.
So introduce phy-reset-gpios property to let Linux handle phy reset
itself.
Signed-off-by: Peng Fan
Reviewed-by: Marco Felsch
---
V2:
U-Boot->bootloader
Add R-b tag
arch/arm64/boot/dts/freescale/imx8mm-evk.dts | 1
On 2019/10/21 下午5:53, Zhu, Lingshan wrote:
On 10/16/2019 6:19 PM, Jason Wang wrote:
On 2019/10/16 上午9:30, Zhu Lingshan wrote:
This commit introduced IFC VF operations for vdpa, which complys to
vhost_mdev interfaces, handles IFC VF initialization,
configuration and removal.
Signed-off-by:
On Fri, Oct 18, 2019 at 06:03:27PM +0530, Kiran Gunda wrote:
> WLED4 peripheral is present on some PMICs like pmi8998 and
> pm660l. It has a different register map and configurations
> are also different. Add support for it.
>
> Signed-off-by: Kiran Gunda
> Reviewed-by: Bjorn Andersson
Reviewed
901 - 1000 of 1182 matches
Mail list logo
