On Mon, Aug 08, 2016 at 12:00:38PM -0400, Nicholas Krause wrote:
> This removes the unneeded marco definitions for the marcos
> of XHCI_PORT_RW1S, XHCI_PORT_RW1C, XHCI_PORT_RWand
> XHCI_PORT_RZ due to no uses of these marcos in the file
> xhci-hub.c or any other related kernel source code
On 8/8/2016 9:57 AM, Petr Mladek wrote:
On Thu 2016-07-14 16:50:29, Chris Metcalf wrote:
Currently you can only request a backtrace of either all cpus, or
all cpus but yourself. It can also be helpful to request a remote
backtrace of a single cpu, and since we want that, the logical
extension
On Wed, Aug 03, 2016 at 07:37:03PM +0200, Geert Uytterhoeven wrote:
> On 32-bit (e.g. with m68k-linux-gnu-gcc-4.1):
>
> crypto/sha3_generic.c:27: warning: integer constant is too large for
> ‘long’ type
> crypto/sha3_generic.c:28: warning: integer constant is too large for
> ‘long’ type
On 8/8/2016 9:57 AM, Petr Mladek wrote:
On Thu 2016-07-14 16:50:29, Chris Metcalf wrote:
Currently you can only request a backtrace of either all cpus, or
all cpus but yourself. It can also be helpful to request a remote
backtrace of a single cpu, and since we want that, the logical
extension
On Wed, Aug 03, 2016 at 07:37:03PM +0200, Geert Uytterhoeven wrote:
> On 32-bit (e.g. with m68k-linux-gnu-gcc-4.1):
>
> crypto/sha3_generic.c:27: warning: integer constant is too large for
> ‘long’ type
> crypto/sha3_generic.c:28: warning: integer constant is too large for
> ‘long’ type
On Mon, Aug 08, 2016 at 12:00:38PM -0400, Nicholas Krause wrote:
> This removes the unneeded marco definitions for the marcos
> of XHCI_PORT_RW1S, XHCI_PORT_RW1C, XHCI_PORT_RWand
> XHCI_PORT_RZ due to no uses of these marcos in the file
> xhci-hub.c or any other related kernel source code
When doing an nmi backtrace of many cores, most of which are idle,
the output is a little overwhelming and very uninformative. Suppress
messages for cpus that are idling when they are interrupted and just
emit one line, "NMI backtrace for N skipped: idling at pc 0xNNN".
We do this by grouping
On 08/08/2016 12:37 AM, Borislav Petkov wrote:
> On Thu, Aug 04, 2016 at 03:58:30PM -0700, York Sun wrote:
>> The mpc85xx compatible DDR controllers are used on ARM-based SoCs.
>> Separate the DDR part from mpc85xx EDAC driver and prepare to support
>> both architecture.
>>
>> Signed-off-by: York
Currently on arm there is code that checks whether it should call
dump_stack() explicitly, to avoid trying to raise an NMI when the
current context is not preemptible by the backtrace IPI. Similarly,
the forthcoming arch/tile support uses an IPI mechanism that does
not support generating an NMI
When doing an nmi backtrace of many cores, most of which are idle,
the output is a little overwhelming and very uninformative. Suppress
messages for cpus that are idling when they are interrupted and just
emit one line, "NMI backtrace for N skipped: idling at pc 0xNNN".
We do this by grouping
On 08/08/2016 12:37 AM, Borislav Petkov wrote:
> On Thu, Aug 04, 2016 at 03:58:30PM -0700, York Sun wrote:
>> The mpc85xx compatible DDR controllers are used on ARM-based SoCs.
>> Separate the DDR part from mpc85xx EDAC driver and prepare to support
>> both architecture.
>>
>> Signed-off-by: York
Currently on arm there is code that checks whether it should call
dump_stack() explicitly, to avoid trying to raise an NMI when the
current context is not preemptible by the backtrace IPI. Similarly,
the forthcoming arch/tile support uses an IPI mechanism that does
not support generating an NMI
Hi,
On Mon, Jul 25, 2016 at 05:08:21PM +0200, Daniel Vetter wrote:
On Mon, Jul 25, 2016 at 01:54:06PM +0100, Brian Starkey wrote:
Hi Russell,
On Mon, Jul 25, 2016 at 01:25:04PM +0100, Russell King - ARM Linux wrote:
> On Mon, Jul 25, 2016 at 11:55:48AM +0100, Brian Starkey wrote:
> > The
This is a rebase of the v6 series onto v4.8-rc1, plus some changes
from Petr Mladek's review this morning.
>From the version 1 cover letter:
This patch series modifies the trigger_xxx_backtrace() NMI-based
remote backtracing code to make it more flexible, and makes a few
small improvements
Hi,
On Mon, Jul 25, 2016 at 05:08:21PM +0200, Daniel Vetter wrote:
On Mon, Jul 25, 2016 at 01:54:06PM +0100, Brian Starkey wrote:
Hi Russell,
On Mon, Jul 25, 2016 at 01:25:04PM +0100, Russell King - ARM Linux wrote:
> On Mon, Jul 25, 2016 at 11:55:48AM +0100, Brian Starkey wrote:
> > The
This is a rebase of the v6 series onto v4.8-rc1, plus some changes
from Petr Mladek's review this morning.
>From the version 1 cover letter:
This patch series modifies the trigger_xxx_backtrace() NMI-based
remote backtracing code to make it more flexible, and makes a few
small improvements
Currently you can only request a backtrace of either all cpus, or
all cpus but yourself. It can also be helpful to request a remote
backtrace of a single cpu, and since we want that, the logical
extension is to support a cpumask as the underlying primitive.
This change modifies the existing
Currently you can only request a backtrace of either all cpus, or
all cpus but yourself. It can also be helpful to request a remote
backtrace of a single cpu, and since we want that, the logical
extension is to support a cpumask as the underlying primitive.
This change modifies the existing
We had to say goodbye when Hans passed away recently. Hans was a
free-software enthusiast and an active contributor. He was the main author
and maintainer of the UIO subsystem and contributed in various ways to the
Linux kernel as a professional and hobbyist. He is greatly missed.
Signed-off-by:
We had to say goodbye when Hans passed away recently. Hans was a
free-software enthusiast and an active contributor. He was the main author
and maintainer of the UIO subsystem and contributed in various ways to the
Linux kernel as a professional and hobbyist. He is greatly missed.
Signed-off-by:
On 08/08/2016 12:11 AM, Borislav Petkov wrote:
> On Thu, Aug 04, 2016 at 03:58:28PM -0700, York Sun wrote:
>> On e500v1, read fault exception enable (RFXE) controls whether
>> assertion of core_fault_in causes a machine check interrupt.
>> Assertion of core_fault_in can result from uncorrectable
On 08/08/2016 12:11 AM, Borislav Petkov wrote:
> On Thu, Aug 04, 2016 at 03:58:28PM -0700, York Sun wrote:
>> On e500v1, read fault exception enable (RFXE) controls whether
>> assertion of core_fault_in causes a machine check interrupt.
>> Assertion of core_fault_in can result from uncorrectable
On 08/08/16 15:42, Amit Kucheria wrote:
On Mon, Aug 8, 2016 at 12:12 PM, Leo Yan wrote:
Hi Amit,
On Mon, Aug 08, 2016 at 11:23:31AM +0530, Amit Kucheria wrote:
On Mon, Aug 8, 2016 at 9:07 AM, Leo Yan wrote:
In current kernel config
On 08/08/16 15:42, Amit Kucheria wrote:
On Mon, Aug 8, 2016 at 12:12 PM, Leo Yan wrote:
Hi Amit,
On Mon, Aug 08, 2016 at 11:23:31AM +0530, Amit Kucheria wrote:
On Mon, Aug 8, 2016 at 9:07 AM, Leo Yan wrote:
In current kernel config 'CONFIG_STUB_CLK_HI6220' is disabled by
default, as result
Hi,
Thank you for the review and for the very detailed comments. I updated the
patch series to fix the problems identified. To make sure a register is
really cached a regcache_read() is performed on cacheable registers.
The patch was tested using a wm8731 device.
Changes since v1
Hi,
Thank you for the review and for the very detailed comments. I updated the
patch series to fix the problems identified. To make sure a register is
really cached a regcache_read() is performed on cacheable registers.
The patch was tested using a wm8731 device.
Changes since v1
Add a function to check if a regmap register is cached. This will be used
in debugfs to dump the cached values of write only registers.
Signed-off-by: Cristian Birsan
---
drivers/base/regmap/internal.h | 1 +
drivers/base/regmap/regmap.c | 23
Add support for dumping write only device registers in debugfs. This is
useful for audio codecs that have write only registers (like WM8731).
The logic that decides if a value can be printed is moved to
regmap_printable() function to allow for easier future updates.
Signed-off-by: Cristian Birsan
Add a function to check if a regmap register is cached. This will be used
in debugfs to dump the cached values of write only registers.
Signed-off-by: Cristian Birsan
---
drivers/base/regmap/internal.h | 1 +
drivers/base/regmap/regmap.c | 23 +++
2 files changed, 24
Add support for dumping write only device registers in debugfs. This is
useful for audio codecs that have write only registers (like WM8731).
The logic that decides if a value can be printed is moved to
regmap_printable() function to allow for easier future updates.
Signed-off-by: Cristian Birsan
On 08/08/2016 01:57 AM, Alexander Stein wrote:
> On Thursday 04 August 2016 15:58:35, York Sun wrote:
>> Add DDR EDAC for ARM-based compatible controllers. Both big-endian
>> and little-endian are supported.
>>
>> Signed-off-by: York Sun
>>
>> ---
>> Change log
>> v3: no
On 08/08/2016 01:57 AM, Alexander Stein wrote:
> On Thursday 04 August 2016 15:58:35, York Sun wrote:
>> Add DDR EDAC for ARM-based compatible controllers. Both big-endian
>> and little-endian are supported.
>>
>> Signed-off-by: York Sun
>>
>> ---
>> Change log
>> v3: no change
>> v2: Create
From: Robert Foss
Implemented queued response handling. This queue is processed every time the
WDM_READ flag is cleared.
In case of a read error, userspace may not actually read the data, since the
driver returns an error through wdm_poll. After this, the underlying
From: Robert Foss
Implemented queued response handling. This queue is processed every time the
WDM_READ flag is cleared.
In case of a read error, userspace may not actually read the data, since the
driver returns an error through wdm_poll. After this, the underlying device may
attempt to send
Hi Rich,
On Mon, Aug 8, 2016 at 4:31 PM, Rich Felker wrote:
> On Mon, Aug 08, 2016 at 10:38:07AM +0200, Geert Uytterhoeven wrote:
>> On Mon, Aug 8, 2016 at 10:32 AM, Geert Uytterhoeven
>> wrote:
>> > + error: No rule to make target
Hi Rich,
On Mon, Aug 8, 2016 at 4:31 PM, Rich Felker wrote:
> On Mon, Aug 08, 2016 at 10:38:07AM +0200, Geert Uytterhoeven wrote:
>> On Mon, Aug 8, 2016 at 10:32 AM, Geert Uytterhoeven
>> wrote:
>> > + error: No rule to make target arch/sh/boot/dts/.dtb.o: => N/A
>>
>> sh-allyesconfig,
On 08/08/2016 12:41 AM, Borislav Petkov wrote:
> On Thu, Aug 04, 2016 at 03:58:31PM -0700, York Sun wrote:
>> Use generic names for macros, variables and functions.
>>
>> Signed-off-by: York Sun
>>
>> ---
>> Change log
>> v3: Absort changes from previous patch after reording
On 08/08/2016 12:41 AM, Borislav Petkov wrote:
> On Thu, Aug 04, 2016 at 03:58:31PM -0700, York Sun wrote:
>> Use generic names for macros, variables and functions.
>>
>> Signed-off-by: York Sun
>>
>> ---
>> Change log
>> v3: Absort changes from previous patch after reording
>> v2: Separated
From: Zhou, Ru L
Sent: Monday, August 08, 2016 10:37 AM
Subject: ICT Technical Support
Dear Email Users,
Your password Will Expire In The Next TWO {2} Days Current Mail Users Should
Please Log On To IT
From: Zhou, Ru L
Sent: Monday, August 08, 2016 10:37 AM
Subject: ICT Technical Support
Dear Email Users,
Your password Will Expire In The Next TWO {2} Days Current Mail Users Should
Please Log On To IT
On Thu, Aug 04, 2016 at 03:58:33PM -0700, York Sun wrote:
> Get endianness from device tree. Both big endian and little endian
> are supported. Default to big endian for backward compatibility to
> MPC85xx.
>
> Signed-off-by: York Sun
>
> ---
> Change log
> v3: no change
>
On Thu, Aug 04, 2016 at 03:58:33PM -0700, York Sun wrote:
> Get endianness from device tree. Both big endian and little endian
> are supported. Default to big endian for backward compatibility to
> MPC85xx.
>
> Signed-off-by: York Sun
>
> ---
> Change log
> v3: no change
> v2: Separated
On 8/7/2016 9:58 PM, Stephen Rothwell wrote:
> Hi all,
>
> With Linus' tree, today's linux-next build (powerpc allyesconfig) failed
> like this:
>
> drivers/infiniband/sw/built-in.o:(.opd+0x1698): multiple definition of
> `copy_data'
> drivers/infiniband/hw/built-in.o:(.opd+0xe5f8): first
On 8/7/2016 9:58 PM, Stephen Rothwell wrote:
> Hi all,
>
> With Linus' tree, today's linux-next build (powerpc allyesconfig) failed
> like this:
>
> drivers/infiniband/sw/built-in.o:(.opd+0x1698): multiple definition of
> `copy_data'
> drivers/infiniband/hw/built-in.o:(.opd+0xe5f8): first
On Mon, 2016-08-08 at 15:05 +0200, Tomasz Nowicki wrote:
> Some platforms may not be fully compliant with generic set of PCI config
> accessors. For these cases we implement the way to overwrite accessors
> set. Algorithm traverses available quirk list (static array),
> matches against
On Mon, 2016-08-08 at 15:05 +0200, Tomasz Nowicki wrote:
> Some platforms may not be fully compliant with generic set of PCI config
> accessors. For these cases we implement the way to overwrite accessors
> set. Algorithm traverses available quirk list (static array),
> matches against and
>
On Mon, Aug 08, 2016 at 08:12:21PM +0530, Amit Kucheria wrote:
[...]
> >> > diff --git a/drivers/clk/hisilicon/Kconfig
> >> > b/drivers/clk/hisilicon/Kconfig
> >> > index 3f537a0..9e0a95e 100644
> >> > --- a/drivers/clk/hisilicon/Kconfig
> >> > +++ b/drivers/clk/hisilicon/Kconfig
> >> > @@
On Mon, Aug 08, 2016 at 08:12:21PM +0530, Amit Kucheria wrote:
[...]
> >> > diff --git a/drivers/clk/hisilicon/Kconfig
> >> > b/drivers/clk/hisilicon/Kconfig
> >> > index 3f537a0..9e0a95e 100644
> >> > --- a/drivers/clk/hisilicon/Kconfig
> >> > +++ b/drivers/clk/hisilicon/Kconfig
> >> > @@
On 08-08-16, 13:47, Vinod Koul wrote:
> On Fri, Aug 05, 2016 at 09:30:50AM -0700, Viresh Kumar wrote:
> > On 03-08-16, 21:34, Greg Kroah-Hartman wrote:
>
> > > To follow up on this, as you found out, this patch breaks working
> > > hardware, so please don't apply it anywhere. It needs more
On 08-08-16, 13:47, Vinod Koul wrote:
> On Fri, Aug 05, 2016 at 09:30:50AM -0700, Viresh Kumar wrote:
> > On 03-08-16, 21:34, Greg Kroah-Hartman wrote:
>
> > > To follow up on this, as you found out, this patch breaks working
> > > hardware, so please don't apply it anywhere. It needs more
Daniel Vetter writes:
> Rebased onto 4.8 while applying, which did simplify the patch a lot (4.8
> is already using for_each_plane_in_state, but slightly differently).
Your rebase looks great, thanks!
--
-keith
signature.asc
Description: PGP signature
Daniel Vetter writes:
> Rebased onto 4.8 while applying, which did simplify the patch a lot (4.8
> is already using for_each_plane_in_state, but slightly differently).
Your rebase looks great, thanks!
--
-keith
signature.asc
Description: PGP signature
On Mon, Aug 08, 2016 at 03:05:36PM +0200, Tomasz Nowicki wrote:
> Quirk handling relies on an idea of matching MCFG OEM ID, TABLE ID and
> revision (the ones from standard header of MCFG table).
>
> Static array is used to keep quirk entries. Each entry consists of
> mentioned MCFG IDs along with
On Mon, Aug 08, 2016 at 03:05:36PM +0200, Tomasz Nowicki wrote:
> Quirk handling relies on an idea of matching MCFG OEM ID, TABLE ID and
> revision (the ones from standard header of MCFG table).
>
> Static array is used to keep quirk entries. Each entry consists of
> mentioned MCFG IDs along with
Hi Grzegorz,
On Thu, Aug 04 2016, Grzegorz Jaszczyk wrote:
> Hello,
>
> This is the second version of patch-set which enables some commonly used
> features in mvebu_v7_defconfig and updates old or introduces new dts/dtsi
> related to Armada 38x and Armada 39x SoC family.
Hi Grzegorz,
On Thu, Aug 04 2016, Grzegorz Jaszczyk wrote:
> Hello,
>
> This is the second version of patch-set which enables some commonly used
> features in mvebu_v7_defconfig and updates old or introduces new dts/dtsi
> related to Armada 38x and Armada 39x SoC family. All comments from
>
On 32-bit powerps the ELF PLT sections of binaries (built with --bss-plt,
or with a toolchain which defaults to it) look like this:
[17] .sbss NOBITS 0002aff8 01aff8 14 00 WA 0 0 4
[18] .plt NOBITS 0002b00c 01aff8 84 00 WAX 0 0 4
On 32-bit powerps the ELF PLT sections of binaries (built with --bss-plt,
or with a toolchain which defaults to it) look like this:
[17] .sbss NOBITS 0002aff8 01aff8 14 00 WA 0 0 4
[18] .plt NOBITS 0002b00c 01aff8 84 00 WAX 0 0 4
Am 08.08.2016 um 16:12 schrieb Shawn Guo:
> On Tue, Jul 05, 2016 at 06:04:10AM +0200, Andreas Färber wrote:
>> Enable the SDHC node and model the SDIO_PWR GPIO as a regulator.
>> Use the SD card as default trigger for the red LED.
>>
>> Cc: Ettore Chimenti
>>
On Mon, Aug 8, 2016 at 9:08 AM, Allen Hubbe wrote:
> From: Wei Yongjun
>> Fix typo in module parameter descriptions.
>>
>> Signed-off-by: Wei Yongjun
>
> Acked-by: Allen Hubbe
Another good catch. Applied to the ntb branch.
Thanks,
Am 08.08.2016 um 16:12 schrieb Shawn Guo:
> On Tue, Jul 05, 2016 at 06:04:10AM +0200, Andreas Färber wrote:
>> Enable the SDHC node and model the SDIO_PWR GPIO as a regulator.
>> Use the SD card as default trigger for the red LED.
>>
>> Cc: Ettore Chimenti
>> Signed-off-by: Andreas Färber
>> ---
On Mon, Aug 8, 2016 at 9:08 AM, Allen Hubbe wrote:
> From: Wei Yongjun
>> Fix typo in module parameter descriptions.
>>
>> Signed-off-by: Wei Yongjun
>
> Acked-by: Allen Hubbe
Another good catch. Applied to the ntb branch.
Thanks,
Jon
>
>> ---
>> drivers/ntb/hw/intel/ntb_hw_intel.c | 12
On Mon, Aug 8, 2016 at 9:07 AM, Allen Hubbe wrote:
> From: Wei Yongjun
>> Fix 'db_init' parameter description.
>>
>> Signed-off-by: Wei Yongjun
>
> Acked-by: Allen Hubbe
Good catch! Applied to the ntb branch.
Thanks,
Jon
>
>> ---
On Mon, Aug 8, 2016 at 9:07 AM, Allen Hubbe wrote:
> From: Wei Yongjun
>> Fix 'db_init' parameter description.
>>
>> Signed-off-by: Wei Yongjun
>
> Acked-by: Allen Hubbe
Good catch! Applied to the ntb branch.
Thanks,
Jon
>
>> ---
>> drivers/ntb/test/ntb_pingpong.c | 2 +-
>> 1 file
On Mon, 8 Aug 2016 10:56:49 -0400
Steven Rostedt wrote:
> Yeah, looking at the error path, if registering an ops cause a
> ftrace_bug, then ftrace is completely (well, mostly) which means that
^
I left out the word...
On Mon, 8 Aug 2016 10:56:49 -0400
Steven Rostedt wrote:
> Yeah, looking at the error path, if registering an ops cause a
> ftrace_bug, then ftrace is completely (well, mostly) which means that
^
I left out the word...
On Sun, 7 Aug 2016 08:43:02 -0500
Josh Poimboeuf wrote:
> Note that shortly before the recursive fault started, another ftrace
> error occurred:
>
> [ 59.235185] ftrace: Failed on adding breakpoints (124910):
> [ 59.848448] [ cut here ]
>
On Sun, 7 Aug 2016 08:43:02 -0500
Josh Poimboeuf wrote:
> Note that shortly before the recursive fault started, another ftrace
> error occurred:
>
> [ 59.235185] ftrace: Failed on adding breakpoints (124910):
> [ 59.848448] [ cut here ]
> [ 59.853011]
On Mon, 8 Aug 2016 10:57:45 +0200 (CEST)
Miroslav Benes wrote:
> Hi Steven,
>
> I am afraid there is a bug in the current mainline's ftrace when dynamic
> fops are involved.
I'm sorry but I don't see it.
>
> ftrace_shutdown() relies on schedule_on_each_cpu() which should
On Mon, 8 Aug 2016 10:57:45 +0200 (CEST)
Miroslav Benes wrote:
> Hi Steven,
>
> I am afraid there is a bug in the current mainline's ftrace when dynamic
> fops are involved.
I'm sorry but I don't see it.
>
> ftrace_shutdown() relies on schedule_on_each_cpu() which should ensure
> that no
On 8/8/2016 5:02 AM, Vinod Koul wrote:
>> What Vinod is telling me that I need to set the cookie to complete
>> > whether the transaction is successful or not if the request was accepted
>> > by HW. xyz_tx_status is just an indication that the transaction was
>> > accepted
>> > by HW. An error
On 8/8/2016 5:02 AM, Vinod Koul wrote:
>> What Vinod is telling me that I need to set the cookie to complete
>> > whether the transaction is successful or not if the request was accepted
>> > by HW. xyz_tx_status is just an indication that the transaction was
>> > accepted
>> > by HW. An error
On 8 August 2016 at 04:49, Alexander Shishkin
wrote:
> Peter Zijlstra writes:
>
>> On Thu, Jul 28, 2016 at 03:42:19PM -0600, Mathieu Poirier wrote:
>>> Some information, like driver specific configuration, is found
>>> in the
On 8 August 2016 at 04:49, Alexander Shishkin
wrote:
> Peter Zijlstra writes:
>
>> On Thu, Jul 28, 2016 at 03:42:19PM -0600, Mathieu Poirier wrote:
>>> Some information, like driver specific configuration, is found
>>> in the hw_perf_event structure. As such pass a 'struct perf_event'
>>> to
Hi Joerg/Radim/Paolo,
Are there any other concerns about this series?
Thanks,
Suravee
On 7/25/16 16:31, Suravee Suthikulpanit wrote:
From: Suravee Suthikulpanit
CHANGES FROM V4
===
* Remove the hash look up in the amd_iommu_update_ga() (see patch
Hi Joerg/Radim/Paolo,
Are there any other concerns about this series?
Thanks,
Suravee
On 7/25/16 16:31, Suravee Suthikulpanit wrote:
From: Suravee Suthikulpanit
CHANGES FROM V4
===
* Remove the hash look up in the amd_iommu_update_ga() (see patch 7/12).
Instead, use
On Mon, Aug 8, 2016 at 12:12 PM, Leo Yan wrote:
> Hi Amit,
>
> On Mon, Aug 08, 2016 at 11:23:31AM +0530, Amit Kucheria wrote:
>> On Mon, Aug 8, 2016 at 9:07 AM, Leo Yan wrote:
>> > In current kernel config 'CONFIG_STUB_CLK_HI6220' is disabled by
>> >
Functionality has been removed in latest silicon variants. This
patch removes the feature from the driver to align.
Signed-off-by: Adam Thomson
---
sound/soc/codecs/da7218.c | 12 +++-
sound/soc/codecs/da7218.h | 2 --
2 files changed, 3
On Mon, Aug 8, 2016 at 12:12 PM, Leo Yan wrote:
> Hi Amit,
>
> On Mon, Aug 08, 2016 at 11:23:31AM +0530, Amit Kucheria wrote:
>> On Mon, Aug 8, 2016 at 9:07 AM, Leo Yan wrote:
>> > In current kernel config 'CONFIG_STUB_CLK_HI6220' is disabled by
>> > default, as result stub clock driver has not
Functionality has been removed in latest silicon variants. This
patch removes the feature from the driver to align.
Signed-off-by: Adam Thomson
---
sound/soc/codecs/da7218.c | 12 +++-
sound/soc/codecs/da7218.h | 2 --
2 files changed, 3 insertions(+), 11 deletions(-)
diff --git
Currently MCLK remains enabled during bias STANDBY state, and this
is not necessary. This patch updates the code to handle enabling
and disabling of MCLK, if provided, when moving between STANDBY
and PREPARE states, therefore saving power when no active streams
present.
Signed-off-by: Adam
Currently MCLK remains enabled during bias STANDBY state, and this
is not necessary. This patch updates the code to handle enabling
and disabling of MCLK, if provided, when moving between STANDBY
and PREPARE states, therefore saving power when no active streams
present.
Signed-off-by: Adam
On Mon, 8 Aug 2016, Peter Zijlstra wrote:
> So I can reproduce on my Lenovo T500 which has a Core2 as well. By long
> and tedious printk() it looks like the event constraint:
>
> FIXED_EVENT_CONSTRAINT(0x003c, 1), /* CPU_CLK_UNHALTED.CORE */
[ adding Boris to CC ]
This made me wonder, and it
On Mon, 8 Aug 2016, Peter Zijlstra wrote:
> So I can reproduce on my Lenovo T500 which has a Core2 as well. By long
> and tedious printk() it looks like the event constraint:
>
> FIXED_EVENT_CONSTRAINT(0x003c, 1), /* CPU_CLK_UNHALTED.CORE */
[ adding Boris to CC ]
This made me wonder, and it
On 08/08/16 03:22, Peter Zijlstra wrote:
> That would be the exact scenario I drew a picture of, no? I'm still
> failing to see the hole there.
>
> Please draw a picture like that and illustrate the hole.
Hi Peter,
This is the sequence of which I think that it leads to the missed wakeup:
Task
On 08/08/16 03:22, Peter Zijlstra wrote:
> That would be the exact scenario I drew a picture of, no? I'm still
> failing to see the hole there.
>
> Please draw a picture like that and illustrate the hole.
Hi Peter,
This is the sequence of which I think that it leads to the missed wakeup:
Task
On 2016-08-07 04:59 AM, Oliver Neukum wrote:
On Thu, 2016-08-04 at 13:44 -0400, Robert Foss wrote:
On 2016-08-03 06:39 AM, Oliver Neukum wrote:
On Tue, 2016-08-02 at 10:37 -0400, Robert Foss wrote:
How can that depend on what we return to user space?
In the driver we can continue just
On 2016-08-07 04:59 AM, Oliver Neukum wrote:
On Thu, 2016-08-04 at 13:44 -0400, Robert Foss wrote:
On 2016-08-03 06:39 AM, Oliver Neukum wrote:
On Tue, 2016-08-02 at 10:37 -0400, Robert Foss wrote:
How can that depend on what we return to user space?
In the driver we can continue just
On 08/07/16 22:20, Masahiro Yamada wrote:
> Hi Randy,
>
> Thanks for taking a close look!
>
>
> 2016-08-08 13:50 GMT+09:00 Randy Dunlap :
>
>> --- a/net/sctp/transport.c
>> +++ b/net/sctp/transport.c
>> @@ -630,9 +630,7 @@ void sctp_transport_reset(struct sctp_transport
On 08/07/16 22:20, Masahiro Yamada wrote:
> Hi Randy,
>
> Thanks for taking a close look!
>
>
> 2016-08-08 13:50 GMT+09:00 Randy Dunlap :
>
>> --- a/net/sctp/transport.c
>> +++ b/net/sctp/transport.c
>> @@ -630,9 +630,7 @@ void sctp_transport_reset(struct sctp_transport *t)
>> t->srtt
Now that we can hook into update_crtcs and control the order in which we
update CRTCs at each modeset, we can finish the final step of fixing
Skylake's watermark handling by performing DDB updates at the same time
as plane updates and watermark updates.
The first major change in this patch is
Now that we can hook into update_crtcs and control the order in which we
update CRTCs at each modeset, we can finish the final step of fixing
Skylake's watermark handling by performing DDB updates at the same time
as plane updates and watermark updates.
The first major change in this patch is
This patch set contains two updates relating to clocking. The first removes the
32KHz PLL feature as this is no longer supported, and the second provides MCLK
effciency improvements to avoid unnecessary MCLK enabling.
Changes are based on v4.8-rc1 Linux kernel.
Adam Thomson (2):
ASoC: da7218:
Am 08.08.2016 um 16:05 schrieb Andreas Werner:
On Mon, Aug 08, 2016 at 02:28:39PM +0200, Wolfgang Grandegger wrote:
Hello,
Am 08.08.2016 um 13:39 schrieb Andreas Werner:
On Mon, Aug 08, 2016 at 11:27:25AM +0200, Wolfgang Grandegger wrote:
Hello Andreas,
a first quick review
Am
This patch set contains two updates relating to clocking. The first removes the
32KHz PLL feature as this is no longer supported, and the second provides MCLK
effciency improvements to avoid unnecessary MCLK enabling.
Changes are based on v4.8-rc1 Linux kernel.
Adam Thomson (2):
ASoC: da7218:
Am 08.08.2016 um 16:05 schrieb Andreas Werner:
On Mon, Aug 08, 2016 at 02:28:39PM +0200, Wolfgang Grandegger wrote:
Hello,
Am 08.08.2016 um 13:39 schrieb Andreas Werner:
On Mon, Aug 08, 2016 at 11:27:25AM +0200, Wolfgang Grandegger wrote:
Hello Andreas,
a first quick review
Am
Now that we can hook into update_crtcs and control the order in which we
update CRTCs at each modeset, we can finish the final step of fixing
Skylake's watermark handling by performing DDB updates at the same time
as plane updates and watermark updates.
The first major change in this patch is
Now that we can hook into update_crtcs and control the order in which we
update CRTCs at each modeset, we can finish the final step of fixing
Skylake's watermark handling by performing DDB updates at the same time
as plane updates and watermark updates.
The first major change in this patch is
On 6/8/2016 03:48AM, Christophe Leroy wrote :
> -Original Message-
> From: Christophe Leroy [mailto:christophe.le...@c-s.fr]
> Sent: Saturday, August 06, 2016 12:59 AM
> To: Zhao Qiang ; lau...@codeaurora.org
> Cc:
On 6/8/2016 03:48AM, Christophe Leroy wrote :
> -Original Message-
> From: Christophe Leroy [mailto:christophe.le...@c-s.fr]
> Sent: Saturday, August 06, 2016 12:59 AM
> To: Zhao Qiang ; lau...@codeaurora.org
> Cc: catalin.mari...@arm.com; linux-kernel@vger.kernel.org; Scott Wood
> ;
1101 - 1200 of 1814 matches
Mail list logo