[RFC PATCH] ARM: dts: DRA7: Modify pcie1 dt node for EP mode

Modify pcie1 dt node in order for the controller to operate in endpoint mode. This is used only for testing EP mode. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/dra7.dtsi | 43 +++ 1 file changed, 11 insertions(+), 32 deletions(-) diff

[RFC PATCH] pci: endpoint: functions: add an EP function to test PCI

This adds a new endpoint function driver (to program the virtual test device) making use of the EP-core library. The complete usage of the test function is described in Documentation/PCI/pci-test.txt (included in this commit). Signed-off-by: Kishon Vijay Abraham I --- Documentation/PCI/00-INDEX

[RFC PATCH] pci: controller: dra7xx: Add EP mode support

The PCIe controller integrated in dra7xx SoCs is capable of operating in endpoint mode. Add support for dra7xx SoCs to operate in endpoint mode. Signed-off-by: Kishon Vijay Abraham I --- Documentation/devicetree/bindings/pci/ti-pci.txt | 30 ++- drivers/pci/controller/Kconfig

[RFC PATCH] pci: rename *host* directory to *controller*

No functional change. Renamed the *host* directory present inside drivers/pci to *controller*. Some of the controllers present in drivers/pci/host is capable of operating in endpoint mode. So having these drivers in *host* directory might not be appropriate. This is in preparation for adding

[RFC PATCH] misc: add a new host side PCI endpoint test driver

Add PCI endpoint test driver that can verify base address register and legacy interrupt. (TODO: buffer tests and MSI interrupt). The corresponding pci-epf-test function driver should be used on the EP side. Signed-off-by: Kishon Vijay Abraham I --- drivers/misc/Kconfig

Re: [PATCH v3 07/15] lockdep: Implement crossrelease feature

On Wed, Sep 14, 2016 at 12:05 AM, Peter Zijlstra wrote: > > > So the idea is to add support for non-owner serialization primitives, > like completions/semaphores, and so far I've not looked at the code yet. > I did spend 2+ hours trying to decipher your documentation thing,

[RFC PATCH] HACK: pci: controller: dra7xx: disable smart idle

Smart idle prevents RC to access the memory space of this controller. Set the idle mode to smart idle wakeup. This should ideally be done in hwmod. Till it's figured out how to configure it in hwmod, mark this as HACK. Signed-off-by: Kishon Vijay Abraham I ---

[RFC PATCH] misc: add a new host side PCI endpoint test driver

Add PCI endpoint test driver that can verify base address register and legacy interrupt. (TODO: buffer tests and MSI interrupt). The corresponding pci-epf-test function driver should be used on the EP side. Signed-off-by: Kishon Vijay Abraham I --- drivers/misc/Kconfig |7 +

Re: [PATCH v3 07/15] lockdep: Implement crossrelease feature

On Wed, Sep 14, 2016 at 12:05 AM, Peter Zijlstra wrote: > > > So the idea is to add support for non-owner serialization primitives, > like completions/semaphores, and so far I've not looked at the code yet. > I did spend 2+ hours trying to decipher your documentation thing, but am > still

[RFC PATCH] HACK: pci: controller: dra7xx: disable smart idle

Smart idle prevents RC to access the memory space of this controller. Set the idle mode to smart idle wakeup. This should ideally be done in hwmod. Till it's figured out how to configure it in hwmod, mark this as HACK. Signed-off-by: Kishon Vijay Abraham I ---

[RFC PATCH] pci: controller: split designware into *core* and *host*

No functional change. Split the designware core driver into *core* driver and *host* only driver. This is in preparation to add endpoint support in designware. The *endpoint* driver will reuse the *core* driver. This also modifies the dra7xx code to use the new architecture. TODO: All other

[RFC PATCH] pci: controller: split designware into *core* and *host*

No functional change. Split the designware core driver into *core* driver and *host* only driver. This is in preparation to add endpoint support in designware. The *endpoint* driver will reuse the *core* driver. This also modifies the dra7xx code to use the new architecture. TODO: All other

[RFC PATCH] Documentation: PCI: guide to use PCI Endpoint Core Layer

Add Documentation to let users enable endpoint mode in the PCI controller and add new PCI endpoint function. Signed-off-by: Kishon Vijay Abraham I --- Documentation/PCI/00-INDEX |2 + Documentation/PCI/pci-endpoint.txt | 199 2

[RFC PATCH] Documentation: PCI: guide to use PCI Endpoint Core Layer

Add Documentation to let users enable endpoint mode in the PCI controller and add new PCI endpoint function. Signed-off-by: Kishon Vijay Abraham I --- Documentation/PCI/00-INDEX |2 + Documentation/PCI/pci-endpoint.txt | 199 2 files changed,

Re: [PATCH 3/3] net-next: dsa: add new driver for qca8xxx family

Hi Andrew, Andrew Lunn writes: >> ok, i will simply substract 1 from the phy_addr inside the mdio >> callbacks. this would make the code more readable and make the DT >> binding compliant with the ePAPR spec. > > It does however need well commenting. It is setting a trap for

[RFC PATCH] pci: support for configurable PCI endpoint

This patch series *) adds PCI endpoint core layer *) modifies designware/dra7xx driver to be configured in EP mode *) adds a PCI endpoint *test* function driver Known Limitation: *) Does not support multi-function devices TODO: *) access buffers in RC

Re: [PATCH 3/3] net-next: dsa: add new driver for qca8xxx family

Hi Andrew, Andrew Lunn writes: >> ok, i will simply substract 1 from the phy_addr inside the mdio >> callbacks. this would make the code more readable and make the DT >> binding compliant with the ePAPR spec. > > It does however need well commenting. It is setting a trap for anybody > who puts

[RFC PATCH] pci: support for configurable PCI endpoint

This patch series *) adds PCI endpoint core layer *) modifies designware/dra7xx driver to be configured in EP mode *) adds a PCI endpoint *test* function driver Known Limitation: *) Does not support multi-function devices TODO: *) access buffers in RC

Re: [PATCH 3/3] net-next: dsa: add new driver for qca8xxx family

On 09/13/2016 08:59 AM, Andrew Lunn wrote: >> Hi Andrew, >> >> this function does indeed duplicate the functionality of >> phy_ethtool_get_eee() with the small difference, that e->eee_active is >> also set which phy_ethtool_get_eee() does not set. >> >> dsa_slave_get_eee() will call

Re: [PATCH 3/3] net-next: dsa: add new driver for qca8xxx family

On 09/13/2016 08:59 AM, Andrew Lunn wrote: >> Hi Andrew, >> >> this function does indeed duplicate the functionality of >> phy_ethtool_get_eee() with the small difference, that e->eee_active is >> also set which phy_ethtool_get_eee() does not set. >> >> dsa_slave_get_eee() will call

Re: KVM patches applied in weird order in -stable

On 13/09/2016 18:57, Greg KH wrote: > >> [0] commit 4e422bdd2f84 ("KVM: x86: fix missed hardware breakpoints") > >> [1] commit 172b2386ed16 ("KVM: x86: fix missed hardware breakpoints") > >> [2] commit 70e4da7a8ff6 ("KVM: x86: fix root cause for missed > >> hardware

Re: KVM patches applied in weird order in -stable

On 13/09/2016 18:57, Greg KH wrote: > >> [0] commit 4e422bdd2f84 ("KVM: x86: fix missed hardware breakpoints") > >> [1] commit 172b2386ed16 ("KVM: x86: fix missed hardware breakpoints") > >> [2] commit 70e4da7a8ff6 ("KVM: x86: fix root cause for missed > >> hardware

[PATCH 1/2] clocksource: mips-gic-timer: Print an error if IRQ setup fails

We've checked for errors from setup_irq_percpu since commit f95ac8558b88 ("CLOCKSOURCE: mips-gic: Add missing error returns checks") but didn't print an error message in the failure case. This makes it very easy to overlook the GIC timer clock event driver not being registered, since we'll

[PATCH 1/2] clocksource: mips-gic-timer: Print an error if IRQ setup fails

We've checked for errors from setup_irq_percpu since commit f95ac8558b88 ("CLOCKSOURCE: mips-gic: Add missing error returns checks") but didn't print an error message in the failure case. This makes it very easy to overlook the GIC timer clock event driver not being registered, since we'll

[PATCH 2/2] clocksource: mips-gic-timer: Stop checking cpu_has_counter

The cpu_has_counter macro indicates whether the current CPU has a working coprocessor 0 count & compare registers, and has no bearing on the GIC. Stop checking it. Signed-off-by: Paul Burton Cc: Daniel Lezcano Cc: Thomas Gleixner

[PATCH 2/2] clocksource: mips-gic-timer: Stop checking cpu_has_counter

The cpu_has_counter macro indicates whether the current CPU has a working coprocessor 0 count & compare registers, and has no bearing on the GIC. Stop checking it. Signed-off-by: Paul Burton Cc: Daniel Lezcano Cc: Thomas Gleixner Cc: linux-kernel@vger.kernel.org Cc: linux-m...@linux-mips.org

[GIT PULL] MD update for 4.8-rc6

Hi Linus, A few bug fixes for MD. - Guoqing fixed a bug compiling md-cluster in kernel - I fixed a potential deadlock in raid5-cache superblock write, a hang in raid5 reshape resume and a race condition introduced in -rc4 Please pull! Thanks, Shaohua The following changes since commit

[GIT PULL] MD update for 4.8-rc6

Hi Linus, A few bug fixes for MD. - Guoqing fixed a bug compiling md-cluster in kernel - I fixed a potential deadlock in raid5-cache superblock write, a hang in raid5 reshape resume and a race condition introduced in -rc4 Please pull! Thanks, Shaohua The following changes since commit

Re: KVM patches applied in weird order in -stable

On Tue, Sep 13, 2016 at 06:26:12PM +0200, Paolo Bonzini wrote: > > > On 13/09/2016 16:58, Greg KH wrote: > > [adding stable@ as this is a stable issue, not a 'normal' issue] > > > > On Tue, Sep 13, 2016 at 03:51:00PM +0100, Matt Fleming wrote: > >> Folks, > >> > >> While hunting down a

Re: KVM patches applied in weird order in -stable

On Tue, Sep 13, 2016 at 06:26:12PM +0200, Paolo Bonzini wrote: > > > On 13/09/2016 16:58, Greg KH wrote: > > [adding stable@ as this is a stable issue, not a 'normal' issue] > > > > On Tue, Sep 13, 2016 at 03:51:00PM +0100, Matt Fleming wrote: > >> Folks, > >> > >> While hunting down a

Re: [PATCH v1 0/2] i2c: Stop i2c modules being unloaded while in use.

Hi Peter, > nitpick: Patch subjects for the second patch is wrong. > > "reparented" is a bit dual when dealing with i2c adapter trees. > i2c_mux_add_owned_adapter is perhaps clearer? Agreed, I will update that. > > > Aside from that, I'm not using modules much and need some enlightenment > as

Re: [PATCH v1 0/2] i2c: Stop i2c modules being unloaded while in use.

Hi Peter, > nitpick: Patch subjects for the second patch is wrong. > > "reparented" is a bit dual when dealing with i2c adapter trees. > i2c_mux_add_owned_adapter is perhaps clearer? Agreed, I will update that. > > > Aside from that, I'm not using modules much and need some enlightenment > as

[PATCH] irqchip: mips-gic: Use for_each_set_bit to iterate over local IRQs

The MIPS GIC driver has previously iterated over bits set in a bitmap representing pending local IRQs by calling find_first_bit, clearing that bit then calling find_first_bit again until all bits are clear. If multiple interrupts are pending then this is wasteful, as find_first_bit will have to

[PATCH] irqchip: mips-gic: Use for_each_set_bit to iterate over local IRQs

The MIPS GIC driver has previously iterated over bits set in a bitmap representing pending local IRQs by calling find_first_bit, clearing that bit then calling find_first_bit again until all bits are clear. If multiple interrupts are pending then this is wasteful, as find_first_bit will have to

[PATCH] irqchip: mips-gic: Fix local interrupts

Since the device hierarchy domain was added by commit c98c1822ee13 ("irqchip/mips-gic: Add device hierarchy domain"), GIC local interrupts have been broken. Users attempting to setup a per-cpu local IRQ, for example the GIC timer clock events code in drivers/clocksource/mips-gic-timer.c, the

[PATCH] irqchip: mips-gic: Fix local interrupts

Since the device hierarchy domain was added by commit c98c1822ee13 ("irqchip/mips-gic: Add device hierarchy domain"), GIC local interrupts have been broken. Users attempting to setup a per-cpu local IRQ, for example the GIC timer clock events code in drivers/clocksource/mips-gic-timer.c, the

Re: [PATCH 03/47] block-rbd: Adjust the position of a jump label in rbd_header_from_disk()

On Tue, 13 Sep 2016 17:30:33 +0200, Ilya Dryomov wrote: > On Tue, Sep 13, 2016 at 4:36 PM, Jean Delvare wrote: > > On Tue, 13 Sep 2016 11:16:13 +0200, Ilya Dryomov wrote: > >> Jon, could you please yank 865a1caa4b6b ("CodingStyle: Clarify and > >> complete chapter 7") from your

Re: [PATCH 03/47] block-rbd: Adjust the position of a jump label in rbd_header_from_disk()

On Tue, 13 Sep 2016 17:30:33 +0200, Ilya Dryomov wrote: > On Tue, Sep 13, 2016 at 4:36 PM, Jean Delvare wrote: > > On Tue, 13 Sep 2016 11:16:13 +0200, Ilya Dryomov wrote: > >> Jon, could you please yank 865a1caa4b6b ("CodingStyle: Clarify and > >> complete chapter 7") from your linux-next branch

Re: [PATCH 1/2] PCI: save and restore device state during bus reset

On Thu, Sep 01, 2016 at 07:00:00PM -0400, Sinan Kaya wrote: > A secondary bus reset causes settings to be lost by all downstream > devices on the tree. The code is currently saving and restoring device > states only when called from the VFIO path via pci_probe_reset_bus > and pci_reset_bus

Re: [PATCH 1/2] PCI: save and restore device state during bus reset

On Thu, Sep 01, 2016 at 07:00:00PM -0400, Sinan Kaya wrote: > A secondary bus reset causes settings to be lost by all downstream > devices on the tree. The code is currently saving and restoring device > states only when called from the VFIO path via pci_probe_reset_bus > and pci_reset_bus

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

On Tue, Sep 13, 2016 at 06:14:27PM +0200, Oleg Nesterov wrote: > Me too, and I failed to find something which could be broken... So > perhaps should make it nop and investigate the new bug reports after > that. Works for me :-) > > Hmm. And preempt_enable_no_resched_notrace() under TASK_DEAD

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

On Tue, Sep 13, 2016 at 06:14:27PM +0200, Oleg Nesterov wrote: > Me too, and I failed to find something which could be broken... So > perhaps should make it nop and investigate the new bug reports after > that. Works for me :-) > > Hmm. And preempt_enable_no_resched_notrace() under TASK_DEAD

Re: [PATCH V3] net-next: dsa: add FIB support

Hi John, John Crispin writes: > i sent an email to Jiri earlier today and he asked me to drop this > until his notification series got merged. That makes sense then. So David should ignore this for the moment. Thanks, Vivien

Re: [PATCH V3] net-next: dsa: add FIB support

Hi John, John Crispin writes: > i sent an email to Jiri earlier today and he asked me to drop this > until his notification series got merged. That makes sense then. So David should ignore this for the moment. Thanks, Vivien

Re: [PATCH 3/4] input: Deprecate real timestamps beyond year 2106

> All errors (new ones prefixed by >>): > >drivers/input/input-compat.c: In function 'input_event_from_user': >>> drivers/input/input-compat.c:24:15: error: invalid application of 'sizeof' >>> to incomplete type 'struct input_event_compat' >sizeof(struct input_event_compat))) >

Re: [PATCH 3/4] input: Deprecate real timestamps beyond year 2106

> All errors (new ones prefixed by >>): > >drivers/input/input-compat.c: In function 'input_event_from_user': >>> drivers/input/input-compat.c:24:15: error: invalid application of 'sizeof' >>> to incomplete type 'struct input_event_compat' >sizeof(struct input_event_compat))) >

Re: [PATCH v3] net: ip, diag -- Add diag interface for raw sockets

On Tue, Sep 13, 2016 at 11:57:35AM -0400, David Miller wrote: > > > > Thanks for review, David. I updated against net-next. > > Please do not post new versions of patches as replies to existing > discussions. > > Instead, make fresh patch postings to the list. Oh, will do. Sorry for

Re: [PATCH v3] net: ip, diag -- Add diag interface for raw sockets

On Tue, Sep 13, 2016 at 11:57:35AM -0400, David Miller wrote: > > > > Thanks for review, David. I updated against net-next. > > Please do not post new versions of patches as replies to existing > discussions. > > Instead, make fresh patch postings to the list. Oh, will do. Sorry for

Re: [PATCH v5 2/9] drivers: irqchip: Add STM32 external interrupts support

Hi Thomas, On 09/13/2016 05:21 PM, Thomas Gleixner wrote: On Fri, 9 Sep 2016, Alexandre TORGUE wrote: +static void stm32_exti_free(struct irq_domain *d, unsigned int virq, + unsigned int nr_irqs) +{ + struct irq_data *data = irq_get_irq_data(virq); + +

Re: [PATCH v5 2/9] drivers: irqchip: Add STM32 external interrupts support

Hi Thomas, On 09/13/2016 05:21 PM, Thomas Gleixner wrote: On Fri, 9 Sep 2016, Alexandre TORGUE wrote: +static void stm32_exti_free(struct irq_domain *d, unsigned int virq, + unsigned int nr_irqs) +{ + struct irq_data *data = irq_get_irq_data(virq); + +

[PATCH] perf diff: bug fix, donot overwrite build id in dso__load

From: Kan Liang This patch fixes a perf diff regression issue which was introduced by: commit 5baecbcd9c9a ("perf symbols: we can now read separate debug-info files based on a build ID") The binary name could be same when perf diff different binaries. Build id is used to

[PATCH] usb: atm: cxacru: Clean up if function returned NULL on failure

Some functions return NULL on failure, used !x instead of x==NULL. Signed-off-by: Amit Ghadge --- drivers/usb/atm/cxacru.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/usb/atm/cxacru.c b/drivers/usb/atm/cxacru.c index

[PATCH] perf diff: bug fix, donot overwrite build id in dso__load

From: Kan Liang This patch fixes a perf diff regression issue which was introduced by: commit 5baecbcd9c9a ("perf symbols: we can now read separate debug-info files based on a build ID") The binary name could be same when perf diff different binaries. Build id is used to distinguish between

[PATCH] usb: atm: cxacru: Clean up if function returned NULL on failure

Some functions return NULL on failure, used !x instead of x==NULL. Signed-off-by: Amit Ghadge --- drivers/usb/atm/cxacru.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/usb/atm/cxacru.c b/drivers/usb/atm/cxacru.c index 0a866e9..95a4737 100644 ---

Re: [PATCH v5 07/14] drivers: acpi: iort: add support for ARM SMMU platform devices creation

On Tue, Sep 13, 2016 at 04:25:55PM +0100, Robin Murphy wrote: [...] > > +/** > > + * iort_add_smmu_platform_device() - Allocate a platform device for SMMU > > + * @fwnode: IORT node associated fwnode handle > > + * @node: Pointer to SMMU ACPI IORT node > > + * > > + * Returns: 0 on success, <0

Re: [PATCH v5 07/14] drivers: acpi: iort: add support for ARM SMMU platform devices creation

On Tue, Sep 13, 2016 at 04:25:55PM +0100, Robin Murphy wrote: [...] > > +/** > > + * iort_add_smmu_platform_device() - Allocate a platform device for SMMU > > + * @fwnode: IORT node associated fwnode handle > > + * @node: Pointer to SMMU ACPI IORT node > > + * > > + * Returns: 0 on success, <0

Re: [PATCH V3] net-next: dsa: add FIB support

On 13/09/2016 18:21, Vivien Didelot wrote: > Hi John, > > John Crispin writes: > >> @@ -237,6 +237,7 @@ struct switchdev_obj; >> struct switchdev_obj_port_fdb; >> struct switchdev_obj_port_mdb; >> struct switchdev_obj_port_vlan; >> +struct switchdev_obj_ipv4_fib; > > Can

Re: [PATCH V3] net-next: dsa: add FIB support

On 13/09/2016 18:21, Vivien Didelot wrote: > Hi John, > > John Crispin writes: > >> @@ -237,6 +237,7 @@ struct switchdev_obj; >> struct switchdev_obj_port_fdb; >> struct switchdev_obj_port_mdb; >> struct switchdev_obj_port_vlan; >> +struct switchdev_obj_ipv4_fib; > > Can you keep it

Re: KVM patches applied in weird order in -stable

On 13/09/2016 16:58, Greg KH wrote: > [adding stable@ as this is a stable issue, not a 'normal' issue] > > On Tue, Sep 13, 2016 at 03:51:00PM +0100, Matt Fleming wrote: >> Folks, >> >> While hunting down a performance issue involving KVM I was surprised >> to see "native_set_debugreg()" as the

Re: KVM patches applied in weird order in -stable

On 13/09/2016 16:58, Greg KH wrote: > [adding stable@ as this is a stable issue, not a 'normal' issue] > > On Tue, Sep 13, 2016 at 03:51:00PM +0100, Matt Fleming wrote: >> Folks, >> >> While hunting down a performance issue involving KVM I was surprised >> to see "native_set_debugreg()" as the

Re: [PATCHv3 1/2] pciehp: Let user control LED status

On Tue, Sep 13, 2016 at 09:05:39AM -0600, Keith Busch wrote: > +int pciehp_get_raw_attention_status(struct hotplug_slot *hotplug_slot, > + u8 *value) > +{ > + struct slot *slot = hotplug_slot->private; > + struct pci_dev *pdev =

Re: [PATCHv3 1/2] pciehp: Let user control LED status

On Tue, Sep 13, 2016 at 09:05:39AM -0600, Keith Busch wrote: > +int pciehp_get_raw_attention_status(struct hotplug_slot *hotplug_slot, > + u8 *value) > +{ > + struct slot *slot = hotplug_slot->private; > + struct pci_dev *pdev =

Re: [PATCH v2] mm, proc: Fix region lost in /proc/self/smaps

On 09/13/2016 07:59 AM, Oleg Nesterov wrote: > On 09/12, Michal Hocko wrote: >> > Considering how this all can be tricky and how partial reads can be >> > confusing and even misleading I am really wondering whether we >> > should simply document that only full reads will provide a sensible >> >

Re: [PATCH v2] mm, proc: Fix region lost in /proc/self/smaps

On 09/13/2016 07:59 AM, Oleg Nesterov wrote: > On 09/12, Michal Hocko wrote: >> > Considering how this all can be tricky and how partial reads can be >> > confusing and even misleading I am really wondering whether we >> > should simply document that only full reads will provide a sensible >> >

Re: [PATCH V3] net-next: dsa: add FIB support

Hi John, John Crispin writes: > @@ -237,6 +237,7 @@ struct switchdev_obj; > struct switchdev_obj_port_fdb; > struct switchdev_obj_port_mdb; > struct switchdev_obj_port_vlan; > +struct switchdev_obj_ipv4_fib; Can you keep it ordered please (put obj_ipv4 above port_fdb). >

Re: [PATCH V3] net-next: dsa: add FIB support

Hi John, John Crispin writes: > @@ -237,6 +237,7 @@ struct switchdev_obj; > struct switchdev_obj_port_fdb; > struct switchdev_obj_port_mdb; > struct switchdev_obj_port_vlan; > +struct switchdev_obj_ipv4_fib; Can you keep it ordered please (put obj_ipv4 above port_fdb). > > struct

Re: [PATCH v2 0/8] PCI: pciehp: Rework hotplug interrupt routine

On Mon, Sep 12, 2016 at 04:08:47PM -0500, Bjorn Helgaas wrote: > This is mostly Mayurkumar's work from [1] and [2]. I split [2] into two > patches and reworked it to keep the enclosing loop around the pciehp ISR. > > The patches I added are trivial ones to clarify variable names, make dmesg >

Re: [PATCH v2 0/8] PCI: pciehp: Rework hotplug interrupt routine

On Mon, Sep 12, 2016 at 04:08:47PM -0500, Bjorn Helgaas wrote: > This is mostly Mayurkumar's work from [1] and [2]. I split [2] into two > patches and reworked it to keep the enclosing loop around the pciehp ISR. > > The patches I added are trivial ones to clarify variable names, make dmesg >

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

On 09/12, Peter Zijlstra wrote: > > On Mon, Sep 12, 2016 at 03:05:38PM +0200, Oleg Nesterov wrote: > > > But this leads to the question which I wanted to ask many times. > > > > Why cond_resched() is not NOP if CONFIG_PREEMPT=y ? > > Dunno, nobody bothered to do it? We should keep the

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

On 09/12, Peter Zijlstra wrote: > > On Mon, Sep 12, 2016 at 03:05:38PM +0200, Oleg Nesterov wrote: > > > But this leads to the question which I wanted to ask many times. > > > > Why cond_resched() is not NOP if CONFIG_PREEMPT=y ? > > Dunno, nobody bothered to do it? We should keep the

[PATCH v6] genirq: Machine-parsable version of /proc/interrupts

From: Craig Gallek Export struct irq_desc information through sysfs. The same information is available in /proc/interrupts but the format of that file has changed over kernel versions and differs across architectures. The procfs version also has varying column numbers

[PATCH v6] genirq: Machine-parsable version of /proc/interrupts

From: Craig Gallek Export struct irq_desc information through sysfs. The same information is available in /proc/interrupts but the format of that file has changed over kernel versions and differs across architectures. The procfs version also has varying column numbers depending on hardware.

RE: [PATCH v2 1/8] PCI: pciehp: Rename pcie_isr() locals for clarity

> > On Tue, Sep 13, 2016 at 10:05:31AM +, Patel, Mayurkumar wrote: > > > > > Rename "detected" and "intr_loc" to "status" and "events" for clarity. > > > "status" is the value we read from the Slot Status register; "events" is > > > the set of hot-plug events we need to process. No

RE: [PATCH v2 1/8] PCI: pciehp: Rename pcie_isr() locals for clarity

> > On Tue, Sep 13, 2016 at 10:05:31AM +, Patel, Mayurkumar wrote: > > > > > Rename "detected" and "intr_loc" to "status" and "events" for clarity. > > > "status" is the value we read from the Slot Status register; "events" is > > > the set of hot-plug events we need to process. No

Re: [PATCH 2/2] phy: msm8996-pcie-phy: Add support to msm8996 pcie phy

On 9/7/2016 4:25 PM, Srinivas Kandagatla wrote: This patch adds support to msm8996 pcie phy which supports 3 ports, Port A, Port B and Port C. Each port is independent and connected to a pcie host controller, there is also a common block which is shared across all the 3 ports. Signed-off-by:

Re: [PATCH 2/2] phy: msm8996-pcie-phy: Add support to msm8996 pcie phy

On 9/7/2016 4:25 PM, Srinivas Kandagatla wrote: This patch adds support to msm8996 pcie phy which supports 3 ports, Port A, Port B and Port C. Each port is independent and connected to a pcie host controller, there is also a common block which is shared across all the 3 ports. Signed-off-by:

Re: [PATCH] drivers: net: phy: xgene: Fix 'remove' function

From: Christophe JAILLET Date: Sun, 11 Sep 2016 21:43:34 +0200 > If 'IS_ERR(pdata->clk)' is true, then 'clk_disable_unprepare(pdata->clk)' > will do nothing. > > It is likely that 'if (!IS_ERR(pdata->clk))' was expected here. > In fact, the test can even be

Re: [PATCH] drivers: net: phy: xgene: Fix 'remove' function

From: Christophe JAILLET Date: Sun, 11 Sep 2016 21:43:34 +0200 > If 'IS_ERR(pdata->clk)' is true, then 'clk_disable_unprepare(pdata->clk)' > will do nothing. > > It is likely that 'if (!IS_ERR(pdata->clk))' was expected here. > In fact, the test can even be removed because

Re: [PATCH 3/4] input: Deprecate real timestamps beyond year 2106

Hi Deepa, [auto build test ERROR on input/next] [also build test ERROR on v4.8-rc6 next-20160913] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record w

Re: [PATCH 3/4] input: Deprecate real timestamps beyond year 2106

Hi Deepa, [auto build test ERROR on input/next] [also build test ERROR on v4.8-rc6 next-20160913] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record w

Re: [PATCH] MIPS: rb532: Fix undefined reference to setup_serial_port

On Mon, Sep 05, 2016 at 05:18:40PM +0100, Matt Redfearn wrote: > If the rb532 machine is compiled without CONFIG_SERIAL_8250, the > following linker error occurs > > arch/mips/built-in.o: In function `setup_serial_port': > (.init.text+0x20c): undefined reference to `early_serial_setup' > > Fix

Re: [PATCH] MIPS: rb532: Fix undefined reference to setup_serial_port

On Mon, Sep 05, 2016 at 05:18:40PM +0100, Matt Redfearn wrote: > If the rb532 machine is compiled without CONFIG_SERIAL_8250, the > following linker error occurs > > arch/mips/built-in.o: In function `setup_serial_port': > (.init.text+0x20c): undefined reference to `early_serial_setup' > > Fix

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

On 2016-09-12 08:05 PM, Rafael J. Wysocki wrote: > On Monday, September 12, 2016 11:15:45 PM Rafael J. Wysocki wrote: >> On Monday, September 12, 2016 06:14:44 PM Peter Zijlstra wrote: >>> On Mon, Sep 12, 2016 at 12:01:58PM -0400, Chris Metcalf wrote: On 9/7/2016 5:11 PM, Francis Giraldeau

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

On 2016-09-12 08:05 PM, Rafael J. Wysocki wrote: > On Monday, September 12, 2016 11:15:45 PM Rafael J. Wysocki wrote: >> On Monday, September 12, 2016 06:14:44 PM Peter Zijlstra wrote: >>> On Mon, Sep 12, 2016 at 12:01:58PM -0400, Chris Metcalf wrote: On 9/7/2016 5:11 PM, Francis Giraldeau

Re: [PATCH v5 06/14] drivers: acpi: implement acpi_dma_configure

On Tue, Sep 13, 2016 at 03:41:06PM +0100, Robin Murphy wrote: > On 09/09/16 15:23, Lorenzo Pieralisi wrote: > > On DT based systems, the of_dma_configure() API implements DMA > > configuration for a given device. On ACPI systems an API equivalent to > > of_dma_configure() is missing which implies

Re: [PATCH v5 06/14] drivers: acpi: implement acpi_dma_configure

On Tue, Sep 13, 2016 at 03:41:06PM +0100, Robin Murphy wrote: > On 09/09/16 15:23, Lorenzo Pieralisi wrote: > > On DT based systems, the of_dma_configure() API implements DMA > > configuration for a given device. On ACPI systems an API equivalent to > > of_dma_configure() is missing which implies

[tip:timers/core] tick/nohz: Prevent stopping the tick on an offline CPU

Commit-ID: 57ccdf449f962ab5fc8cbf26479402f13bdb8be7 Gitweb: http://git.kernel.org/tip/57ccdf449f962ab5fc8cbf26479402f13bdb8be7 Author: Wanpeng Li AuthorDate: Wed, 7 Sep 2016 18:51:13 +0800 Committer: Thomas Gleixner CommitDate: Tue, 13 Sep

[tip:timers/core] tick/nohz: Prevent stopping the tick on an offline CPU

Commit-ID: 57ccdf449f962ab5fc8cbf26479402f13bdb8be7 Gitweb: http://git.kernel.org/tip/57ccdf449f962ab5fc8cbf26479402f13bdb8be7 Author: Wanpeng Li AuthorDate: Wed, 7 Sep 2016 18:51:13 +0800 Committer: Thomas Gleixner CommitDate: Tue, 13 Sep 2016 17:53:52 +0200 tick/nohz: Prevent

Re: [PATCH 3/3] net-next: dsa: add new driver for qca8xxx family

> Hi Andrew, > > this function does indeed duplicate the functionality of > phy_ethtool_get_eee() with the small difference, that e->eee_active is > also set which phy_ethtool_get_eee() does not set. > > dsa_slave_get_eee() will call phy_ethtool_get_eee() right after the > get_eee() op has been

Re: [PATCH 3/3] net-next: dsa: add new driver for qca8xxx family

> Hi Andrew, > > this function does indeed duplicate the functionality of > phy_ethtool_get_eee() with the small difference, that e->eee_active is > also set which phy_ethtool_get_eee() does not set. > > dsa_slave_get_eee() will call phy_ethtool_get_eee() right after the > get_eee() op has been

Re: [PATCH v3] net: ip, diag -- Add diag interface for raw sockets

From: Cyrill Gorcunov Date: Sun, 11 Sep 2016 22:17:15 +0300 > On Sat, Sep 10, 2016 at 04:28:40PM -0600, David Ahern wrote: >> On 9/10/16 4:05 PM, Cyrill Gorcunov wrote: >> > On Sat, Sep 10, 2016 at 10:31:35AM -0600, David Ahern wrote: >> >> >> >> Would you mind adding the

Re: [PATCH 2/3] qemu: Implement virtio-pstore device

On Sat, Aug 20, 2016 at 05:07:43PM +0900, Namhyung Kim wrote: > Add virtio pstore device to allow kernel log files saved on the host. > It will save the log files on the directory given by pstore device > option. > > $ qemu-system-x86_64 -device virtio-pstore,directory=dir-xx ... > > (guest)

Re: [PATCH v3] net: ip, diag -- Add diag interface for raw sockets

From: Cyrill Gorcunov Date: Sun, 11 Sep 2016 22:17:15 +0300 > On Sat, Sep 10, 2016 at 04:28:40PM -0600, David Ahern wrote: >> On 9/10/16 4:05 PM, Cyrill Gorcunov wrote: >> > On Sat, Sep 10, 2016 at 10:31:35AM -0600, David Ahern wrote: >> >> >> >> Would you mind adding the destroy capability as

Re: [PATCH 2/3] qemu: Implement virtio-pstore device

On Sat, Aug 20, 2016 at 05:07:43PM +0900, Namhyung Kim wrote: > Add virtio pstore device to allow kernel log files saved on the host. > It will save the log files on the directory given by pstore device > option. > > $ qemu-system-x86_64 -device virtio-pstore,directory=dir-xx ... > > (guest)

Re: [PATCH 1/6] PCI: xilinx: Keep both legacy and MSI interrupt references.

On Thu, Sep 01, 2016 at 03:44:41PM +0530, Bharat Kumar Gogada wrote: > When built with MSI support the legacy domain reference is being > overwritten with MSI. > Instead creating two separate domains for MSI and legacy interrupts. > > Signed-off-by: Bharat Kumar Gogada

Re: [PATCH 1/6] PCI: xilinx: Keep both legacy and MSI interrupt references.

On Thu, Sep 01, 2016 at 03:44:41PM +0530, Bharat Kumar Gogada wrote: > When built with MSI support the legacy domain reference is being > overwritten with MSI. > Instead creating two separate domains for MSI and legacy interrupts. > > Signed-off-by: Bharat Kumar Gogada Applied all these (except

Re: [PATCH 3/3] PCI: Xilinx NWL PCIe: Fix Error for multi function device for legacy interrupts.

Hello, On Tue, 13 Sep 2016 10:34:02 -0500, Bjorn Helgaas wrote: > > After looking at this myself, I'm not happy with this either. It feels > > like there are bugs lurking here and we're just hiding one of them. > > > > Here are the callers of irq_domain_add_linear() for legacy INTx in > >

Re: [PATCH 3/3] PCI: Xilinx NWL PCIe: Fix Error for multi function device for legacy interrupts.

Hello, On Tue, 13 Sep 2016 10:34:02 -0500, Bjorn Helgaas wrote: > > After looking at this myself, I'm not happy with this either. It feels > > like there are bugs lurking here and we're just hiding one of them. > > > > Here are the callers of irq_domain_add_linear() for legacy INTx in > >

RE: [PATCH v7] gpio: add Intel WhiskeyCove PMIC GPIO driver

On Fri, Sep 13, 2016 at 07:46:31AM, Paul Gortmaker wrote: >> On Tue, Sep 13, 2016 at 4:37 PM, Paul Gortmaker >> wrote: >> >> > This looks like an invalid address, and >> >> >> >> >> +MODULE_AUTHOR("Ajay Thomas >> >> >>

RE: [PATCH v7] gpio: add Intel WhiskeyCove PMIC GPIO driver

On Fri, Sep 13, 2016 at 07:46:31AM, Paul Gortmaker wrote: >> On Tue, Sep 13, 2016 at 4:37 PM, Paul Gortmaker >> wrote: >> >> > This looks like an invalid address, and >> >> >> >> >> +MODULE_AUTHOR("Ajay Thomas >> >> >> +"); >> >> > >> >> > ...the same here. In fact it sure looks like two

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