Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

* Frank Rowand [160908 12:18]: > > On 09/08/16 08:58, Tony Lindgren wrote: > >> Just to consider other ways of doing it, we could use the compatible > >> flag to tag devices that need to be just idled on probe, but that does > >> not seem like generic solution to me. > >

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

* Frank Rowand [160908 12:18]: > > On 09/08/16 08:58, Tony Lindgren wrote: > >> Just to consider other ways of doing it, we could use the compatible > >> flag to tag devices that need to be just idled on probe, but that does > >> not seem like generic solution to me. > > > > Yuck. Again

Re: [PATCH v1] i2c: designware: save the preset value of DW_IC_SDA_HOLD

On Sat, Aug 27, 2016 at 03:39:30PM +0800, Zhuo-hao Lee wrote: > There are several ways to set the SDA hold time for i2c controller, > including: Device Tree, built-in device properties and ACPI. However, > if the SDA hold time is not specified by above method, we should > read the value, where it

Re: [PATCH v1] i2c: designware: save the preset value of DW_IC_SDA_HOLD

On Sat, Aug 27, 2016 at 03:39:30PM +0800, Zhuo-hao Lee wrote: > There are several ways to set the SDA hold time for i2c controller, > including: Device Tree, built-in device properties and ACPI. However, > if the SDA hold time is not specified by above method, we should > read the value, where it

Re: [PATCH] ARM: mmp: replace NO_IRQ

On Tuesday, September 6, 2016 10:22:06 PM CEST Russell King - ARM Linux wrote: > oak uses NCR5380. NCR5380 is shared across multiple architectures > which have a random selection of NO_IRQ defined as 0 or -1. To > convert this without regression takes a multi-step process: > > 1. Verify all

Re: [PATCH] ARM: mmp: replace NO_IRQ

On Tuesday, September 6, 2016 10:22:06 PM CEST Russell King - ARM Linux wrote: > oak uses NCR5380. NCR5380 is shared across multiple architectures > which have a random selection of NO_IRQ defined as 0 or -1. To > convert this without regression takes a multi-step process: > > 1. Verify all

Re: [PATCH 0/5] nbd improvements

On 09/08/2016 01:33 PM, Josef Bacik wrote: This is a patch series aimed at bringing NBD into 2016. The two big components of this series is converting nbd over to using blkmq and then allowing us to provide more than one connection for a nbd device. The NBD user space server doesn't care about

Re: [PATCH 0/5] nbd improvements

On 09/08/2016 01:33 PM, Josef Bacik wrote: This is a patch series aimed at bringing NBD into 2016. The two big components of this series is converting nbd over to using blkmq and then allowing us to provide more than one connection for a nbd device. The NBD user space server doesn't care about

drivers/gpio/gpiolib.c:3215: undefined reference to `of_get_named_gpiod_flags'

Hi Linus, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d71f058617564750261b673ea9b3352382b9cde4 commit: 2527ecc9195e9c66252af24c4689e8a67cd4ccb9 gpio: Fix OF build problem on UM date: 3 weeks

drivers/gpio/gpiolib.c:3215: undefined reference to `of_get_named_gpiod_flags'

Hi Linus, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d71f058617564750261b673ea9b3352382b9cde4 commit: 2527ecc9195e9c66252af24c4689e8a67cd4ccb9 gpio: Fix OF build problem on UM date: 3 weeks

[PATCH] sched/deadline: document behavior of sched_yield()

This is a documentation only patch, explaining the behavior of sched_yield() when a SCHED_DEADLINE task calls it (give up remaining runtime and suspend till next period). --- Documentation/scheduler/sched-deadline.txt | 13 + 1 file changed, 13 insertions(+) diff --git

Re: [PATCH v4 1/4] firmware: Move umh locking code into fw_load_from_user_helper()

On Thu, Sep 08, 2016 at 11:37:54PM +0800, Ming Lei wrote: > On Wed, Sep 7, 2016 at 4:45 PM, Daniel Wagner wrote: > > From: Daniel Wagner > > > > When we load the firmware directly we don't need to take the umh > > lock. > > I am wondering if it can be

[PATCH] usb: gadget: remove variable ret and remove unnecessary if statement

From: Colin Ian King the if statement in lb_modinit is unnecessary so we can totally remove the variable ret and just return the return value from the call to usb_function_register. Signed-off-by: Colin Ian King ---

Re: [PATCH v2 27/33] x86/intel_rdt_rdtgroup.c: Implement resctrl file system commands

On Thu, 8 Sep 2016, Fenghua Yu wrote: > +static struct kernfs_syscall_ops rdtgroup_kf_syscall_ops = { > + .mkdir = rdtgroup_mkdir, > + .rmdir = rdtgroup_rmdir, > +}; > + > +static struct file_system_type rdt_fs_type = { > + .name = "resctrl", > + .mount =

[PATCH] sched/deadline: document behavior of sched_yield()

This is a documentation only patch, explaining the behavior of sched_yield() when a SCHED_DEADLINE task calls it (give up remaining runtime and suspend till next period). --- Documentation/scheduler/sched-deadline.txt | 13 + 1 file changed, 13 insertions(+) diff --git

Re: [PATCH v4 1/4] firmware: Move umh locking code into fw_load_from_user_helper()

On Thu, Sep 08, 2016 at 11:37:54PM +0800, Ming Lei wrote: > On Wed, Sep 7, 2016 at 4:45 PM, Daniel Wagner wrote: > > From: Daniel Wagner > > > > When we load the firmware directly we don't need to take the umh > > lock. > > I am wondering if it can be wrong. If you disable the firmware UMH why

[PATCH] usb: gadget: remove variable ret and remove unnecessary if statement

From: Colin Ian King the if statement in lb_modinit is unnecessary so we can totally remove the variable ret and just return the return value from the call to usb_function_register. Signed-off-by: Colin Ian King --- drivers/usb/gadget/function/f_loopback.c | 8 ++-- 1 file changed, 2

Re: [PATCH v2 27/33] x86/intel_rdt_rdtgroup.c: Implement resctrl file system commands

On Thu, 8 Sep 2016, Fenghua Yu wrote: > +static struct kernfs_syscall_ops rdtgroup_kf_syscall_ops = { > + .mkdir = rdtgroup_mkdir, > + .rmdir = rdtgroup_rmdir, > +}; > + > +static struct file_system_type rdt_fs_type = { > + .name = "resctrl", > + .mount =

Re: [PATCH v3 0/8] clk: sunxi-ng: Introduce support for A23 and A33 CCUs

On Thu, Sep 08, 2016 at 11:48:35AM +0200, Maxime Ripard wrote: > Hi everyone, > > Here is the migration for the A23 and A33 clocks to the sunxi-ng > framework. > > It has been tested on SinA33 board, and I made sure that everything > was reported at the exact same rate, that the MMC was still

Re: [PATCH v3 0/8] clk: sunxi-ng: Introduce support for A23 and A33 CCUs

On Thu, Sep 08, 2016 at 11:48:35AM +0200, Maxime Ripard wrote: > Hi everyone, > > Here is the migration for the A23 and A33 clocks to the sunxi-ng > framework. > > It has been tested on SinA33 board, and I made sure that everything > was reported at the exact same rate, that the MMC was still

Re: [PATCH] pstore: drop pmsg bounce buffer

On Thu, Sep 1, 2016 at 8:13 AM, Mark Salyzyn wrote: > Removing a bounce buffer copy operation in the pmsg driver path is > always better. We also gain in overall performance by not requesting > a vmalloc on every write as this can cause precious RT tasks, such > as user

Re: [PATCHv8 1/2] usb: USB Type-C connector class

On Thu, Sep 01, 2016 at 02:49:47PM +0300, Heikki Krogerus wrote: > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role swapping, and when the port

Re: [PATCH] pstore: drop pmsg bounce buffer

On Thu, Sep 1, 2016 at 8:13 AM, Mark Salyzyn wrote: > Removing a bounce buffer copy operation in the pmsg driver path is > always better. We also gain in overall performance by not requesting > a vmalloc on every write as this can cause precious RT tasks, such > as user facing media operation, to

Re: [PATCHv8 1/2] usb: USB Type-C connector class

On Thu, Sep 01, 2016 at 02:49:47PM +0300, Heikki Krogerus wrote: > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role swapping, and when the port

[PATCH v2] ASoC: sun4i-codec: Distinguish sun4i from sun7i

Introduce mechanism to detect sun7i and provide a different regmap and different controls for it - different compared to sun4i Allwinner A10. The controls will be extended in a forthcoming patch - it is necessary to distinguish between sun4i and sun7i controls because the mic gains are in

[PATCH v2] ASoC: sun4i-codec: Distinguish sun4i from sun7i

Introduce mechanism to detect sun7i and provide a different regmap and different controls for it - different compared to sun4i Allwinner A10. The controls will be extended in a forthcoming patch - it is necessary to distinguish between sun4i and sun7i controls because the mic gains are in

[PATCH 2/2] x86/e820: Use much less memory for e820/e820_saved, save up to 120k

The maximum size of e820 map array for EFI systems is defined as E820_X_MAX (E820MAX + 3 * MAX_NUMNODES). In x86_64 defconfig, this ends up with E820_X_MAX = 320, e820 and e820_saved are 6404 bytes each. With larger configs, for example Fedora kernels, E820_X_MAX = 3200, e820 and e820_saved are

[PATCH 2/2] x86/e820: Use much less memory for e820/e820_saved, save up to 120k

The maximum size of e820 map array for EFI systems is defined as E820_X_MAX (E820MAX + 3 * MAX_NUMNODES). In x86_64 defconfig, this ends up with E820_X_MAX = 320, e820 and e820_saved are 6404 bytes each. With larger configs, for example Fedora kernels, E820_X_MAX = 3200, e820 and e820_saved are

[PATCH 1/2] x86/e820: mark some static functions __init

They are all called only from other __init functions. Signed-off-by: Denys Vlasenko CC: Ingo Molnar CC: Andy Lutomirski CC: "H. Peter Anvin" CC: Borislav Petkov CC: Brian Gerst CC:

[PATCH 1/2] x86/e820: mark some static functions __init

They are all called only from other __init functions. Signed-off-by: Denys Vlasenko CC: Ingo Molnar CC: Andy Lutomirski CC: "H. Peter Anvin" CC: Borislav Petkov CC: Brian Gerst CC: x...@kernel.org CC: linux-kernel@vger.kernel.org --- arch/x86/kernel/e820.c | 12 ++-- 1 file

Re: [PATCH 4/4] clk: mediatek: Add MT6797 clock support

On 09/08/2016 03:49 AM, Mars Cheng wrote: > Add MT6797 clock support, include topckgen, apmixedsys, > infracfg and subsystem clocks. > > Signed-off-by: Mars Cheng > --- > arch/arm64/boot/dts/mediatek/mt6797.dtsi | 66 ++- Please don't combine dts and clk driver changes

Re: [PATCH 4/4] clk: mediatek: Add MT6797 clock support

On 09/08/2016 03:49 AM, Mars Cheng wrote: > Add MT6797 clock support, include topckgen, apmixedsys, > infracfg and subsystem clocks. > > Signed-off-by: Mars Cheng > --- > arch/arm64/boot/dts/mediatek/mt6797.dtsi | 66 ++- Please don't combine dts and clk driver changes together. We generally

Re: [PATCH 4/8] ARM: dts: bcm283x: Add a new EMMC pin group from the downstream tree.

Hi Gerd/Eric On 16-09-08 12:44 AM, Gerd Hoffmann wrote: On Mi, 2016-09-07 at 20:13 +0200, Stefan Wahren wrote: Gerd Hoffmann hat am 7. September 2016 um 12:31 geschrieben: From: Eric Anholt This will be used for having EMMC (sdhci-bcm2835.c) drive the

Re: [PATCH 4/8] ARM: dts: bcm283x: Add a new EMMC pin group from the downstream tree.

Hi Gerd/Eric On 16-09-08 12:44 AM, Gerd Hoffmann wrote: On Mi, 2016-09-07 at 20:13 +0200, Stefan Wahren wrote: Gerd Hoffmann hat am 7. September 2016 um 12:31 geschrieben: From: Eric Anholt This will be used for having EMMC (sdhci-bcm2835.c) drive the wireless. sdhci-bcm2835.c has been

Re: [RFC/RFT][PATCH 0/4] cpufreq / sched: iowait boost in intel_pstate and schedutil

On Thu, 2016-09-08 at 12:26 -0700, Steve Muckle wrote: > On Wed, Sep 07, 2016 at 05:35:50PM -0700, Srinivas Pandruvada wrote: > > > > Did you see any performance regression on Android workloads? > > I did a few AnTuTU runs and did not observe a regression. Thanks. -Srinivas > thanks, > Steve

Re: [RFC/RFT][PATCH 0/4] cpufreq / sched: iowait boost in intel_pstate and schedutil

On Thu, 2016-09-08 at 12:26 -0700, Steve Muckle wrote: > On Wed, Sep 07, 2016 at 05:35:50PM -0700, Srinivas Pandruvada wrote: > > > > Did you see any performance regression on Android workloads? > > I did a few AnTuTU runs and did not observe a regression. Thanks. -Srinivas > thanks, > Steve

Re: [PATCH v2 26/33] Task fork and exit for rdtgroup

On Thu, 8 Sep 2016, Fenghua Yu wrote: > > cgroup_exit(tsk); > + rdtgroup_exit(tsk); So this actually does: > +void rdtgroup_exit(struct task_struct *tsk) > +{ > + > + if (!list_empty(>rg_list)) { > + struct rdtgroup *rdtgrp = tsk->rdtgroup; > + > +

Re: [PATCH v2 26/33] Task fork and exit for rdtgroup

On Thu, 8 Sep 2016, Fenghua Yu wrote: > > cgroup_exit(tsk); > + rdtgroup_exit(tsk); So this actually does: > +void rdtgroup_exit(struct task_struct *tsk) > +{ > + > + if (!list_empty(>rg_list)) { > + struct rdtgroup *rdtgrp = tsk->rdtgroup; > + > +

[PATCH v6 1/2] sdhci-of-arasan: Add device tree parameter xlnx-fails-without-test-cd bit

The sdhci controller on xilinx zynq devices will not function unless the CD bit is provided. http://www.xilinx.com/support/answers/61064.html In cases where it is impossible to provide the CD bit in hardware, setting the controller to test mode and then setting inserted to true will get the

[PATCH v6 1/2] sdhci-of-arasan: Add device tree parameter xlnx-fails-without-test-cd bit

The sdhci controller on xilinx zynq devices will not function unless the CD bit is provided. http://www.xilinx.com/support/answers/61064.html In cases where it is impossible to provide the CD bit in hardware, setting the controller to test mode and then setting inserted to true will get the

[PATCH v6 2/2] sdhci-of-arasan: Set controller to test mode when xlnx-fails-without-test-cd is present

The sdhci controller on xilinx zynq devices will not function unless the CD bit is provided. http://www.xilinx.com/support/answers/61064.html In cases where it is impossible to provide the CD bit in hardware, setting the controller to test mode and then setting inserted to true will get the

[PATCH v6 2/2] sdhci-of-arasan: Set controller to test mode when xlnx-fails-without-test-cd is present

The sdhci controller on xilinx zynq devices will not function unless the CD bit is provided. http://www.xilinx.com/support/answers/61064.html In cases where it is impossible to provide the CD bit in hardware, setting the controller to test mode and then setting inserted to true will get the

Re: [PATCH v2 02/33] Documentation, ABI: Add a document entry for cache id

On Thu, 8 Sep 2016, Fenghua Yu wrote: > +What:/sys/devices/system/cpu/cpu*/cache/index*/id > +Date:July 2016 > +Contact: Linux kernel mailing list > +Description: Cache id > + > + The id identifies a hardware cache of

Re: [PATCH v2 02/33] Documentation, ABI: Add a document entry for cache id

On Thu, 8 Sep 2016, Fenghua Yu wrote: > +What:/sys/devices/system/cpu/cpu*/cache/index*/id > +Date:July 2016 > +Contact: Linux kernel mailing list > +Description: Cache id > + > + The id identifies a hardware cache of the system within a given > +

[PATCH] ARCv2: Implement atomic64 based on LLOCKD/SCONDD instructions

ARCv2 ISA provides 64-bit exclusive load/stores so use them to implement the 64-bit atomics and elide the spinlock based generic 64-bit atomics boot tested with atomic64 self-test (and GOD bless the person who wrote them, I realized my inline assmebly is sloppy as hell) One thing I'm not sure of

[PATCH] ARCv2: Implement atomic64 based on LLOCKD/SCONDD instructions

ARCv2 ISA provides 64-bit exclusive load/stores so use them to implement the 64-bit atomics and elide the spinlock based generic 64-bit atomics boot tested with atomic64 self-test (and GOD bless the person who wrote them, I realized my inline assmebly is sloppy as hell) One thing I'm not sure of

Re: [REPOST PATCH 2/2] pstore/core: drop cmpxchg based updates

On Thu, Sep 8, 2016 at 4:48 AM, Sebastian Andrzej Siewior wrote: > I have here a FPGA behind PCIe which exports SRAM which I use for > pstore. Now it seems that the FPGA no longer supports cmpxchg based > updates and writes back 0xff…ff and returns the same. This leads to

Re: [REPOST PATCH 2/2] pstore/core: drop cmpxchg based updates

On Thu, Sep 8, 2016 at 4:48 AM, Sebastian Andrzej Siewior wrote: > I have here a FPGA behind PCIe which exports SRAM which I use for > pstore. Now it seems that the FPGA no longer supports cmpxchg based > updates and writes back 0xff…ff and returns the same. This leads to > crash during crash

Re: [REPOST PATCH 1/2] pstore/ramoops: fixup driver removal

On Thu, Sep 8, 2016 at 4:48 AM, Sebastian Andrzej Siewior wrote: > A basic rmmod ramoops segfaults. Let's see why. > > Since commit 34f0ec82e0a9 ("pstore: Correct the max_dump_cnt clearing of > ramoops") sets ->max_dump_cnt to zero before looping over ->przs but we > didn't

Re: [REPOST PATCH 1/2] pstore/ramoops: fixup driver removal

On Thu, Sep 8, 2016 at 4:48 AM, Sebastian Andrzej Siewior wrote: > A basic rmmod ramoops segfaults. Let's see why. > > Since commit 34f0ec82e0a9 ("pstore: Correct the max_dump_cnt clearing of > ramoops") sets ->max_dump_cnt to zero before looping over ->przs but we > didn't use it before that

Re: [RFC/RFT][PATCH 0/4] cpufreq / sched: iowait boost in intel_pstate and schedutil

On Wed, Sep 07, 2016 at 05:35:50PM -0700, Srinivas Pandruvada wrote: > Did you see any performance regression on Android workloads? I did a few AnTuTU runs and did not observe a regression. thanks, Steve

Re: [RFC/RFT][PATCH 0/4] cpufreq / sched: iowait boost in intel_pstate and schedutil

On Wed, Sep 07, 2016 at 05:35:50PM -0700, Srinivas Pandruvada wrote: > Did you see any performance regression on Android workloads? I did a few AnTuTU runs and did not observe a regression. thanks, Steve

Re: [GIT PULL 1/4] ARM: exynos: SoC/Mach for v4.9

On Mon, Sep 05, 2016 at 10:06:14AM +0200, Sylwester Nawrocki wrote: > On 09/02/2016 06:32 PM, Krzysztof Kozlowski wrote: > > On Fri, Sep 02, 2016 at 06:26:42PM +0200, Arnd Bergmann wrote: > >> On Tuesday, August 30, 2016 11:18:59 AM CEST Krzysztof Kozlowski wrote: > >>> Samsung mach/soc update for

Re: [GIT PULL 1/4] ARM: exynos: SoC/Mach for v4.9

On Mon, Sep 05, 2016 at 10:06:14AM +0200, Sylwester Nawrocki wrote: > On 09/02/2016 06:32 PM, Krzysztof Kozlowski wrote: > > On Fri, Sep 02, 2016 at 06:26:42PM +0200, Arnd Bergmann wrote: > >> On Tuesday, August 30, 2016 11:18:59 AM CEST Krzysztof Kozlowski wrote: > >>> Samsung mach/soc update for

Re: [PATCH v2] leds: Introduce userspace leds driver

> This driver creates a userspace leds driver similar to uinput. nitpicking below > New leds are created by opening /dev/uleds and writing a uleds_user_dev > struct. A new leds class device is registered with the name given in the > struct. Reading will return a single byte that is the current

Re: [PATCH v2] leds: Introduce userspace leds driver

> This driver creates a userspace leds driver similar to uinput. nitpicking below > New leds are created by opening /dev/uleds and writing a uleds_user_dev > struct. A new leds class device is registered with the name given in the > struct. Reading will return a single byte that is the current

Re: [PATCH v4 0/5] kexec_file: Add buffer hand-over for the next kernel

Am Mittwoch, 07 September 2016, 09:19:40 schrieb Eric W. Biederman: > ebied...@xmission.com (Eric W. Biederman) writes: > > Thiago Jung Bauermann writes: > >> Hello, > >> > >> The purpose of this new version of the series is to fix a small issue > >> that I found,

Re: [PATCH v4 0/5] kexec_file: Add buffer hand-over for the next kernel

Am Mittwoch, 07 September 2016, 09:19:40 schrieb Eric W. Biederman: > ebied...@xmission.com (Eric W. Biederman) writes: > > Thiago Jung Bauermann writes: > >> Hello, > >> > >> The purpose of this new version of the series is to fix a small issue > >> that I found, which is that the kernel

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On 09/08/16 12:09, Frank Rowand wrote: > On 09/08/16 08:58, Tony Lindgren wrote: >> * Rob Herring [160908 06:38]: >>> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote: * Frank Rowand [160831 13:51]: > I am still opposed

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On 09/08/16 12:09, Frank Rowand wrote: > On 09/08/16 08:58, Tony Lindgren wrote: >> * Rob Herring [160908 06:38]: >>> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote: * Frank Rowand [160831 13:51]: > I am still opposed to using the status property for this purpose. > > The

Re: [PATCH] vme: fake: fix build for 64-bit dma_addr_t

On Tue, Sep 06, 2016 at 02:59:41PM +0200, Arnd Bergmann wrote: > casting between dma_addr_t and a pointer is generally tricky, > as they might not be the same size and almost never point into > the same address space. With 32-bit ARM systems and LPAE, we > get this warning for the vme_fake driver

Re: [PATCH] vme: fake: fix build for 64-bit dma_addr_t

On Tue, Sep 06, 2016 at 02:59:41PM +0200, Arnd Bergmann wrote: > casting between dma_addr_t and a pointer is generally tricky, > as they might not be the same size and almost never point into > the same address space. With 32-bit ARM systems and LPAE, we > get this warning for the vme_fake driver

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On 09/08/16 08:58, Tony Lindgren wrote: > * Rob Herring [160908 06:38]: >> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote: >>> * Frank Rowand [160831 13:51]: I am still opposed to using the status property for this

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On 09/08/16 08:58, Tony Lindgren wrote: > * Rob Herring [160908 06:38]: >> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote: >>> * Frank Rowand [160831 13:51]: I am still opposed to using the status property for this purpose. The status property is intended to report an

Re: [RFC PATCH 1/2] macb: Add 1588 support in Cadence GEM.

On Thu, Sep 08, 2016 at 10:22:43AM +0530, Harini Katakam wrote: > >> + /* get GEM internal time */ > >> + sech = gem_readl(bp, TSH); > >> + secl = gem_readl(bp, TSL); > > > > Does reading TSH latch the time? The TRM is silent about that, and > > most other designs latch on reading the

Re: [RFC PATCH 1/2] macb: Add 1588 support in Cadence GEM.

On Thu, Sep 08, 2016 at 10:22:43AM +0530, Harini Katakam wrote: > >> + /* get GEM internal time */ > >> + sech = gem_readl(bp, TSH); > >> + secl = gem_readl(bp, TSL); > > > > Does reading TSH latch the time? The TRM is silent about that, and > > most other designs latch on reading the

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On 09/08/16 06:38, Rob Herring wrote: > On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote: >> * Frank Rowand [160831 13:51]: >>> On 08/29/16 15:35, Tony Lindgren wrote: if (of_device_is_incomplete(pdev->dev.of_node, status)) {

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On 09/08/16 06:38, Rob Herring wrote: > On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote: >> * Frank Rowand [160831 13:51]: >>> On 08/29/16 15:35, Tony Lindgren wrote: if (of_device_is_incomplete(pdev->dev.of_node, status)) { if (!strcmp("hw-incomplete-pins",

Re: [PATCH 2/3] config: android: set SELinux as default security mode

On Thu, Sep 8, 2016 at 11:59 AM, Rob Herring wrote: > Android won't boot without SELinux enabled, so make it the default. > > Signed-off-by: Rob Herring Acked-by: John Stultz thanks -john

Re: [PATCH 3/3] config: android: enable CONFIG_SECCOMP

On Thu, Sep 8, 2016 at 11:59 AM, Rob Herring wrote: > As of Android N, SECCOMP is required. Without it, we will get > mediaextractor error: > > E /system/bin/mediaextractor: libminijail: prctl(PR_SET_SECCOMP, > SECCOMP_MODE_FILTER): Invalid argument > > Signed-off-by: Rob

Re: [PATCH 2/3] config: android: set SELinux as default security mode

On Thu, Sep 8, 2016 at 11:59 AM, Rob Herring wrote: > Android won't boot without SELinux enabled, so make it the default. > > Signed-off-by: Rob Herring Acked-by: John Stultz thanks -john

Re: [PATCH 3/3] config: android: enable CONFIG_SECCOMP

On Thu, Sep 8, 2016 at 11:59 AM, Rob Herring wrote: > As of Android N, SECCOMP is required. Without it, we will get > mediaextractor error: > > E /system/bin/mediaextractor: libminijail: prctl(PR_SET_SECCOMP, > SECCOMP_MODE_FILTER): Invalid argument > > Signed-off-by: Rob Herring Acked-by:

Re: [PATCH 1/3] config: android: move device mapper options to recommended

On Thu, Sep 8, 2016 at 11:59 AM, Rob Herring wrote: > CONFIG_MD is in recommended, but other dependent options like DM_CRYPT > and DM_VERITY options are in base. The result is the options in base don't > get enabled when applying both base and recommended fragments. Move all >

Re: [PATCH 1/3] config: android: move device mapper options to recommended

On Thu, Sep 8, 2016 at 11:59 AM, Rob Herring wrote: > CONFIG_MD is in recommended, but other dependent options like DM_CRYPT > and DM_VERITY options are in base. The result is the options in base don't > get enabled when applying both base and recommended fragments. Move all > the options to

[PATCH v2] leds: Introduce userspace leds driver

This driver creates a userspace leds driver similar to uinput. New leds are created by opening /dev/uleds and writing a uleds_user_dev struct. A new leds class device is registered with the name given in the struct. Reading will return a single byte that is the current brightness. The poll()

[PATCH v2] leds: Introduce userspace leds driver

This driver creates a userspace leds driver similar to uinput. New leds are created by opening /dev/uleds and writing a uleds_user_dev struct. A new leds class device is registered with the name given in the struct. Reading will return a single byte that is the current brightness. The poll()

[ANNOUNCE] 4.6.7-rt12

Dear RT folks! I'm pleased to announce the v4.6.7-rt12 patch set. Changes since v4.6.7-rt11: - The update to v4.6.7-rt11 introduced a performance regression especially visible when compiling a kernel on /dev/shm. It is fixed by invoking less often the "chill" function. Reported by

[ANNOUNCE] 4.6.7-rt12

Dear RT folks! I'm pleased to announce the v4.6.7-rt12 patch set. Changes since v4.6.7-rt11: - The update to v4.6.7-rt11 introduced a performance regression especially visible when compiling a kernel on /dev/shm. It is fixed by invoking less often the "chill" function. Reported by

[PATCH 2/3] config: android: set SELinux as default security mode

Android won't boot without SELinux enabled, so make it the default. Signed-off-by: Rob Herring --- kernel/configs/android-base.config | 1 + 1 file changed, 1 insertion(+) diff --git a/kernel/configs/android-base.config b/kernel/configs/android-base.config index

[PATCH 2/3] config: android: set SELinux as default security mode

Android won't boot without SELinux enabled, so make it the default. Signed-off-by: Rob Herring --- kernel/configs/android-base.config | 1 + 1 file changed, 1 insertion(+) diff --git a/kernel/configs/android-base.config b/kernel/configs/android-base.config index 19eb7ac..859fa27 100644 ---

[PATCH 1/3] config: android: move device mapper options to recommended

CONFIG_MD is in recommended, but other dependent options like DM_CRYPT and DM_VERITY options are in base. The result is the options in base don't get enabled when applying both base and recommended fragments. Move all the options to recommended. Signed-off-by: Rob Herring ---

[PATCH 1/3] config: android: move device mapper options to recommended

CONFIG_MD is in recommended, but other dependent options like DM_CRYPT and DM_VERITY options are in base. The result is the options in base don't get enabled when applying both base and recommended fragments. Move all the options to recommended. Signed-off-by: Rob Herring ---

[PATCH 3/3] config: android: enable CONFIG_SECCOMP

As of Android N, SECCOMP is required. Without it, we will get mediaextractor error: E /system/bin/mediaextractor: libminijail: prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER): Invalid argument Signed-off-by: Rob Herring --- kernel/configs/android-base.config | 1 + 1 file changed,

[PATCH 3/3] config: android: enable CONFIG_SECCOMP

As of Android N, SECCOMP is required. Without it, we will get mediaextractor error: E /system/bin/mediaextractor: libminijail: prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER): Invalid argument Signed-off-by: Rob Herring --- kernel/configs/android-base.config | 1 + 1 file changed, 1 insertion(+)

Re: [PATCH] xfrm: fix header file comment reference to struct xfrm_replay_state_esn

On 16/09/08, Richard Guy Briggs wrote: > Reported-by: Paul Wouters Oops, this above should read "nohats.ca". > Signed-off-by: Richard Guy Briggs > --- > include/uapi/linux/xfrm.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH] xfrm: fix header file comment reference to struct xfrm_replay_state_esn

On 16/09/08, Richard Guy Briggs wrote: > Reported-by: Paul Wouters Oops, this above should read "nohats.ca". > Signed-off-by: Richard Guy Briggs > --- > include/uapi/linux/xfrm.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/uapi/linux/xfrm.h

[PATCH 1/2] config: move x86 kvm_guest.config to a common locaton

kvm_guest.config is useful for KVM guests on other arches, and nothing in it appears to be x86 specific, so just move the whole file. Kbuild will find it in either location. Signed-off-by: Rob Herring Cc: Christoffer Dall Cc: Marc Zyngier

[PATCH 1/2] config: move x86 kvm_guest.config to a common locaton

kvm_guest.config is useful for KVM guests on other arches, and nothing in it appears to be x86 specific, so just move the whole file. Kbuild will find it in either location. Signed-off-by: Rob Herring Cc: Christoffer Dall Cc: Marc Zyngier Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc:

Re: [PATCH v2 5/8] sched,x86: Enable Turbo Boost Max Technology

On Thu, 2016-09-08 at 20:33 +0200, Peter Zijlstra wrote: > On Thu, Sep 08, 2016 at 11:28:48AM -0700, Srinivas Pandruvada wrote: > > > > > Do we need to send v3 to include these changes? > > Might as well I suppose. Then we need to figure out who is going to > merge what where ;-) Preferably

[PATCH 2/2] kvmconfig: add virtio-gpu to config frag

virtio-gpu is used for VMs, so add it to the kvm config. Signed-off-by: Rob Herring Cc: Christoffer Dall Cc: Marc Zyngier Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc:

[PATCH 2/2] kvmconfig: add virtio-gpu to config frag

virtio-gpu is used for VMs, so add it to the kvm config. Signed-off-by: Rob Herring Cc: Christoffer Dall Cc: Marc Zyngier Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: kvm...@lists.cs.columbia.edu Cc: k...@vger.kernel.org --- kernel/configs/kvm_guest.config | 1 + 1 file changed, 1 insertion(+)

Re: [PATCH v2 5/8] sched,x86: Enable Turbo Boost Max Technology

On Thu, 2016-09-08 at 20:33 +0200, Peter Zijlstra wrote: > On Thu, Sep 08, 2016 at 11:28:48AM -0700, Srinivas Pandruvada wrote: > > > > > Do we need to send v3 to include these changes? > > Might as well I suppose. Then we need to figure out who is going to > merge what where ;-) Preferably

Re: checkpatch.pl: Use of uninitialized value $str in split at ./scripts/checkpatch.pl line 1079.

On Thu, 2016-09-08 at 08:23 +0200, Charlemagne Lasse wrote: > I've noticed that checkpatch prints an error in linux-next. This can > be reproduced via > ./scripts/checkpatch.pl --strict --file net/batman-adv/bat_iv_ogm.c > This problem seems to be introduced by d369873d2f53 ("Merge branch >

Re: checkpatch.pl: Use of uninitialized value $str in split at ./scripts/checkpatch.pl line 1079.

On Thu, 2016-09-08 at 08:23 +0200, Charlemagne Lasse wrote: > I've noticed that checkpatch prints an error in linux-next. This can > be reproduced via > ./scripts/checkpatch.pl --strict --file net/batman-adv/bat_iv_ogm.c > This problem seems to be introduced by d369873d2f53 ("Merge branch >

Re: [PATCH] lockdep: Quiet gcc about dangerous __builtin_return_address() operations

On Thu, 8 Sep 2016 20:33:13 +0200 Borislav Petkov wrote: > On Thu, Sep 08, 2016 at 12:34:33PM -0400, Steven Rostedt wrote: > > [ > > Boris, does this quiet gcc for you? > > I haven't fully tested this yet, as I still don't have a compiler > > that does the warning. > >

Re: [PATCH] lockdep: Quiet gcc about dangerous __builtin_return_address() operations

On Thu, 8 Sep 2016 20:33:13 +0200 Borislav Petkov wrote: > On Thu, Sep 08, 2016 at 12:34:33PM -0400, Steven Rostedt wrote: > > [ > > Boris, does this quiet gcc for you? > > I haven't fully tested this yet, as I still don't have a compiler > > that does the warning. > > gcc 6.x should be

[PATCH] staging: comedi: comedi_fops: coding style fixes

- Fixed coding style in comedi_fops.c Symbolic to octal permission. Signed-off-by: Matias Mucciolo --- drivers/staging/comedi/comedi_fops.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/comedi/comedi_fops.c

[PATCH] staging: comedi: comedi_fops: coding style fixes

- Fixed coding style in comedi_fops.c Symbolic to octal permission. Signed-off-by: Matias Mucciolo --- drivers/staging/comedi/comedi_fops.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/comedi/comedi_fops.c b/drivers/staging/comedi/comedi_fops.c

Re: [PATCH v2 5/8] sched,x86: Enable Turbo Boost Max Technology

On Thu, Sep 08, 2016 at 11:28:48AM -0700, Srinivas Pandruvada wrote: > Do we need to send v3 to include these changes? Might as well I suppose. Then we need to figure out who is going to merge what where ;-)

Re: [PATCH v2 5/8] sched,x86: Enable Turbo Boost Max Technology

On Thu, Sep 08, 2016 at 11:28:48AM -0700, Srinivas Pandruvada wrote: > Do we need to send v3 to include these changes? Might as well I suppose. Then we need to figure out who is going to merge what where ;-)

<    1   2   3   4   5   6   7   8   9   10   >