Re: [PATCH 1/3] ath6kl: Only use match sets when firmware supports it

Hi Kalle, Have you had a chance to check out these patches yet? -- Kyle Roeschley Software Engineer National Instruments

Re: [PATCH 1/3] ath6kl: Only use match sets when firmware supports it

Hi Kalle, Have you had a chance to check out these patches yet? -- Kyle Roeschley Software Engineer National Instruments

[PATCH] USB: serial: cp210x: Add ID for NI USB serial console

Added the USB VID and PID for the USB serial console on some National Instruments devices. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> --- drivers/usb/serial/cp210x.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c

[PATCH] USB: serial: cp210x: Add ID for NI USB serial console

Added the USB VID and PID for the USB serial console on some National Instruments devices. Signed-off-by: Kyle Roeschley --- drivers/usb/serial/cp210x.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c index 06d502b3e913..cc5b2d0d340d

Re: [PATCH] spi: Add a sysfs interface to instantiate devices

On Fri, Dec 22, 2017 at 03:56:03PM +, Mark Brown wrote: > On Thu, Dec 21, 2017 at 09:05:43PM +, Trent Piepho wrote: > > On Thu, 2017-12-21 at 14:03 -0600, Kyle Roeschley wrote: > > > Add a sysfs interface to instantiate and delete SPI devices using the > > > spid

Re: [PATCH] spi: Add a sysfs interface to instantiate devices

On Fri, Dec 22, 2017 at 03:56:03PM +, Mark Brown wrote: > On Thu, Dec 21, 2017 at 09:05:43PM +, Trent Piepho wrote: > > On Thu, 2017-12-21 at 14:03 -0600, Kyle Roeschley wrote: > > > Add a sysfs interface to instantiate and delete SPI devices using the > > > spid

[PATCH] spi: Add a sysfs interface to instantiate devices

by 99cd8e25875a ("i2c: Add a sysfs interface to instantiate devices"). Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> --- Documentation/spi/spi-summary | 14 drivers/spi/spi.c | 78 +++ include/linux/spi/spi.h | 3 ++

[PATCH] spi: Add a sysfs interface to instantiate devices

by 99cd8e25875a ("i2c: Add a sysfs interface to instantiate devices"). Signed-off-by: Kyle Roeschley --- Documentation/spi/spi-summary | 14 drivers/spi/spi.c | 78 +++ include/linux/spi/spi.h | 3 ++ 3 files changed, 95 insertion

Re: [PATCH] mmc: core: Wait for Vdd to settle on card power off

On Fri, Sep 22, 2017 at 11:38:40AM +0200, Ulf Hansson wrote: > On 21 September 2017 at 19:47, Kyle Roeschley <kyle.roesch...@ni.com> wrote: > > The SD spec version 6.0 section 6.4.1.5 requires that Vdd must be > > lowered to less than 0.5V for a minimum of 1 ms when po

Re: [PATCH] mmc: core: Wait for Vdd to settle on card power off

On Fri, Sep 22, 2017 at 11:38:40AM +0200, Ulf Hansson wrote: > On 21 September 2017 at 19:47, Kyle Roeschley wrote: > > The SD spec version 6.0 section 6.4.1.5 requires that Vdd must be > > lowered to less than 0.5V for a minimum of 1 ms when powering off a > > card. Increase

Re: [PATCH] pinctrl: intel: Mask interrupts on driver probe

On Fri, Sep 22, 2017 at 08:47:12AM +0300, Mika Westerberg wrote: > On Thu, Sep 21, 2017 at 02:20:03PM -0500, Kyle Roeschley wrote: > > Powering off the system on Apollo Lake does not clear the interrupt > > enable registers for the GPIOs. To avoid an interrupt storm on driver >

Re: [PATCH] pinctrl: intel: Mask interrupts on driver probe

On Fri, Sep 22, 2017 at 08:47:12AM +0300, Mika Westerberg wrote: > On Thu, Sep 21, 2017 at 02:20:03PM -0500, Kyle Roeschley wrote: > > Powering off the system on Apollo Lake does not clear the interrupt > > enable registers for the GPIOs. To avoid an interrupt storm on driver >

[PATCH] pinctrl: intel: Mask interrupts on driver probe

Powering off the system on Apollo Lake does not clear the interrupt enable registers for the GPIOs. To avoid an interrupt storm on driver probe, clear all interrupt enables before enabling our interrupt line. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> --- drivers/pinctrl/intel/p

[PATCH] pinctrl: intel: Mask interrupts on driver probe

Powering off the system on Apollo Lake does not clear the interrupt enable registers for the GPIOs. To avoid an interrupt storm on driver probe, clear all interrupt enables before enabling our interrupt line. Signed-off-by: Kyle Roeschley --- drivers/pinctrl/intel/pinctrl-intel.c | 43

[PATCH] mmc: core: Wait for Vdd to settle on card power off

The SD spec version 6.0 section 6.4.1.5 requires that Vdd must be lowered to less than 0.5V for a minimum of 1 ms when powering off a card. Increase our wait to 10 ms so that voltage has time to drain down to 0.5V and cards can power off correctly. Signed-off-by: Kyle Roeschley <kyle.roe

[PATCH] mmc: core: Wait for Vdd to settle on card power off

The SD spec version 6.0 section 6.4.1.5 requires that Vdd must be lowered to less than 0.5V for a minimum of 1 ms when powering off a card. Increase our wait to 10 ms so that voltage has time to drain down to 0.5V and cards can power off correctly. Signed-off-by: Kyle Roeschley --- drivers/mmc

[PATCH] ARM: zynq: Reserve correct amount of non-DMA RAM

than relying on swapper_pg_dir, which is an address and not a size anyway. Fixes: 46f5b96 ("ARM: zynq: Reserve not DMAable space in front of the kernel") Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> --- Found when migrating from 4.1 to 4.6. arch/arm/mach-zynq/common.

[PATCH] ARM: zynq: Reserve correct amount of non-DMA RAM

than relying on swapper_pg_dir, which is an address and not a size anyway. Fixes: 46f5b96 ("ARM: zynq: Reserve not DMAable space in front of the kernel") Signed-off-by: Kyle Roeschley --- Found when migrating from 4.1 to 4.6. arch/arm/mach-zynq/common.c | 2 +- 1 file changed, 1

Re: [RFC] net: phy: smsc: Disable auto-negotiation on startup

On Tue, Oct 11, 2016 at 09:32:30AM -0500, Jeremy Linton wrote: > On 10/10/2016 12:41 PM, Kyle Roeschley wrote: > > Because the SMSC PHY completes auto-negotiation before the driver is > > ready to handle interrupts, the PHY state machine never realizes that we > > have a lin

Re: [RFC] net: phy: smsc: Disable auto-negotiation on startup

On Tue, Oct 11, 2016 at 09:32:30AM -0500, Jeremy Linton wrote: > On 10/10/2016 12:41 PM, Kyle Roeschley wrote: > > Because the SMSC PHY completes auto-negotiation before the driver is > > ready to handle interrupts, the PHY state machine never realizes that we > > have a lin

Re: [RFC] net: phy: smsc: Disable auto-negotiation on startup

On Wed, Oct 12, 2016 at 02:13:06AM -0700, Florian Fainelli wrote: > On 10/10/2016 10:41 AM, Kyle Roeschley wrote: > > Because the SMSC PHY completes auto-negotiation before the driver is > > ready to handle interrupts, the PHY state machine never realizes that we > &g

Re: [RFC] net: phy: smsc: Disable auto-negotiation on startup

On Wed, Oct 12, 2016 at 02:13:06AM -0700, Florian Fainelli wrote: > On 10/10/2016 10:41 AM, Kyle Roeschley wrote: > > Because the SMSC PHY completes auto-negotiation before the driver is > > ready to handle interrupts, the PHY state machine never realizes that we > &g

[RFC] net: phy: smsc: Disable auto-negotiation on startup

commit 99f81afc139c ("phy: micrel: Disable auto negotiation on startup"). Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> --- drivers/net/phy/smsc.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/net/phy/smsc.c b/drivers/net/phy/smsc.c index b62c4aa

[RFC] net: phy: smsc: Disable auto-negotiation on startup

commit 99f81afc139c ("phy: micrel: Disable auto negotiation on startup"). Signed-off-by: Kyle Roeschley --- drivers/net/phy/smsc.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/net/phy/smsc.c b/drivers/net/phy/smsc.c index b62c4aa..8de8011 100644 --- a/drive

[PATCH v8 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

From: Boris Brezillon <boris.brezil...@free-electrons.com> This clarifies the write_bbt() by removing the write label and clarifying the error/exit path. Signed-off-by: Boris Brezillon <boris.brezil...@free-electrons.com> Tested-by: Kyle Roeschley <kyle.roesch...@ni.com> ---

[PATCH v8 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

From: Boris Brezillon This clarifies the write_bbt() by removing the write label and clarifying the error/exit path. Signed-off-by: Boris Brezillon Tested-by: Kyle Roeschley --- v8: Move the chip indexing change back into patch 2 v7: Move all code cleanup into first patch Correct

[PATCH v8 2/2] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> Sign

[PATCH v8 2/2] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Signed-off-by: Kyle Roeschley Signed-off-by: Boris Brezillon

Re: [PATCH v7 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

On Sat, Aug 13, 2016 at 12:37:03AM +0200, Boris Brezillon wrote: > On Fri, 12 Aug 2016 16:58:22 -0500 > Kyle Roeschley <kyle.roesch...@ni.com> wrote: > [...] > > + while (chip < nrchips) { > > I'm probably missing something, but why are you turning th

Re: [PATCH v7 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

On Sat, Aug 13, 2016 at 12:37:03AM +0200, Boris Brezillon wrote: > On Fri, 12 Aug 2016 16:58:22 -0500 > Kyle Roeschley wrote: > [...] > > + while (chip < nrchips) { > > I'm probably missing something, but why are you turning the for loop > into a while loop in thi

Re: [PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

Hi Boris, On Fri, Aug 12, 2016 at 09:15:03PM +0200, Boris Brezillon wrote: > Hi Kyle, > > On Fri, 12 Aug 2016 12:54:49 -0500 > Kyle Roeschley <kyle.roesch...@ni.com> wrote: > > > From: Boris Brezillon <boris.brezil...@free-electrons.com> > > > &g

Re: [PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

Hi Boris, On Fri, Aug 12, 2016 at 09:15:03PM +0200, Boris Brezillon wrote: > Hi Kyle, > > On Fri, 12 Aug 2016 12:54:49 -0500 > Kyle Roeschley wrote: > > > From: Boris Brezillon > > > > This clarifies the write_bbt() by removing the write label and c

[PATCH v7 2/2] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> Sign

[PATCH v7 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

From: Boris Brezillon <boris.brezil...@free-electrons.com> This clarifies the write_bbt() by removing the write label and clarifying the error/exit path. Signed-off-by: Boris Brezillon <boris.brezil...@free-electrons.com> Tested-by: Kyle Roeschley <kyle.roesch...@ni.com> ---

[PATCH v7 2/2] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Signed-off-by: Kyle Roeschley Signed-off-by: Boris Brezillon

[PATCH v7 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

From: Boris Brezillon This clarifies the write_bbt() by removing the write label and clarifying the error/exit path. Signed-off-by: Boris Brezillon Tested-by: Kyle Roeschley --- v7: Move all code cleanup into first patch Correct documentation of mark_bbt_block_bad Make pr_warn

[PATCH v6 2/2] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> Sign

[PATCH v6 2/2] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Signed-off-by: Kyle Roeschley Signed-off-by: Boris Brezillon

[PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

From: Boris Brezillon This clarifies the write_bbt() by removing the write label and clarifying the error/exit path. Signed-off-by: Boris Brezillon --- v6: Split functionality of write_bbt out into new functions v5:

[PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

From: Boris Brezillon This clarifies the write_bbt() by removing the write label and clarifying the error/exit path. Signed-off-by: Boris Brezillon --- v6: Split functionality of write_bbt out into new functions v5: De-duplicate bad block handling v4: Don't ignore write protection while

[RESEND v5] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

stf...@ni.com>. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> Suggested-by: Jeff Westfahl <jeff.westf...@ni.com> --- v5: De-duplicate bad block handling v4: Don't ignore write protection while marking bad BBT blocks Correctly call block_markbad Minor cleanups v3: Don't

[RESEND v5] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

-by: Kyle Roeschley Suggested-by: Jeff Westfahl --- v5: De-duplicate bad block handling v4: Don't ignore write protection while marking bad BBT blocks Correctly call block_markbad Minor cleanups v3: Don't overload mtd->priv Keep nand_erase_nand from erroring on protected BBT blocks

[PATCH v5] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

stf...@ni.com>. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> Suggested-by: Jeff Westfahl <jeff.westf...@ni.com> --- v5: De-duplicate bad block handling v4: Don't ignore write protection while marking bad BBT blocks Correctly call block_markbad Minor cleanups v3: Don't

[PATCH v5] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

-by: Kyle Roeschley Suggested-by: Jeff Westfahl --- v5: De-duplicate bad block handling v4: Don't ignore write protection while marking bad BBT blocks Correctly call block_markbad Minor cleanups v3: Don't overload mtd->priv Keep nand_erase_nand from erroring on protected BBT blocks

[RESEND PATCH v4] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

stf...@ni.com>. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> Suggested-by: Jeff Westfahl <jeff.westf...@ni.com> --- v4: Don't ignore write protection while marking bad BBT blocks Correctly call block_markbad Minor cleanups v3: Don't overload mtd->priv Keep nand_era

[RESEND PATCH v4] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

-by: Kyle Roeschley Suggested-by: Jeff Westfahl --- v4: Don't ignore write protection while marking bad BBT blocks Correctly call block_markbad Minor cleanups v3: Don't overload mtd->priv Keep nand_erase_nand from erroring on protected BBT blocks v2: Mark OOB area in each block as w

[PATCH v4] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

stf...@ni.com>. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> Suggested-by: Jeff Westfahl <jeff.westf...@ni.com> --- v4: Don't ignore write protection while marking bad BBT blocks Correctly call block_markbad Minor cleanups v3: Don't overload mtd->priv Keep nand_era

[PATCH v4] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

-by: Kyle Roeschley Suggested-by: Jeff Westfahl --- v4: Don't ignore write protection while marking bad BBT blocks Correctly call block_markbad Minor cleanups v3: Don't overload mtd->priv Keep nand_erase_nand from erroring on protected BBT blocks v2: Mark OOB area in each block as w

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

On Fri, Apr 29, 2016 at 09:16:31PM +0200, Boris Brezillon wrote: > On Fri, 29 Apr 2016 12:34:18 -0500 > Kyle Roeschley <kyle.roesch...@ni.com> wrote: > > > Hi Boris, > > > > On Wed, Mar 30, 2016 at 03:16:23PM +0200, Boris Brezillon wrote: > > > +Peter, w

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

On Fri, Apr 29, 2016 at 09:16:31PM +0200, Boris Brezillon wrote: > On Fri, 29 Apr 2016 12:34:18 -0500 > Kyle Roeschley wrote: > > > Hi Boris, > > > > On Wed, Mar 30, 2016 at 03:16:23PM +0200, Boris Brezillon wrote: > > > +Peter, who's currently reworking th

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

> On Fri, 25 Mar 2016 17:31:16 -0500 > > Kyle Roeschley <kyle.roesch...@ni.com> wrote: > > > > > If erasing or writing the BBT fails, we should mark the current BBT > > > block as bad and use the BBT descriptor to scan for the next available > > > unused b

Re: [PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

Hi Boris, On Wed, Mar 30, 2016 at 03:16:23PM +0200, Boris Brezillon wrote: > +Peter, who's currently reworking the NAND BBT code. > > On Wed, 30 Mar 2016 15:13:51 +0200 > Boris Brezillon wrote: > > > Hi Kyle, > > > > On Fri, 25 Mar 2016 17:31:1

[PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

stf...@ni.com>. Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> Suggested-by: Jeff Westfahl <jeff.westf...@ni.com> --- This v3 is in response to comments from Brian Norris and Bean Ho on 8/26/15: http://lists.infradead.org/pipermail/linux-mtd/2015-August/061411.html v3: Don't

[PATCH v3] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

-by: Kyle Roeschley Suggested-by: Jeff Westfahl --- This v3 is in response to comments from Brian Norris and Bean Ho on 8/26/15: http://lists.infradead.org/pipermail/linux-mtd/2015-August/061411.html v3: Don't overload mtd->priv Keep nand_erase_nand from erroring on protected BBT blocks v2: M

Re: [PATCH 1/2] misc: add nirtfeatures driver

edded controllers so I think it might be more appropriate to put it in drivers/platform. CC-ing Darren Hart, x86 platform driver maintainer, for input and because I forgot to copy him earlier in this chain. Kyle Roeschley National Instruments

Re: [PATCH 1/2] misc: add nirtfeatures driver

edded controllers so I think it might be more appropriate to put it in drivers/platform. CC-ing Darren Hart, x86 platform driver maintainer, for input and because I forgot to copy him earlier in this chain. Kyle Roeschley National Instruments

Re: [PATCH 2/2] misc: nirtfeatures: physical interface elements

On Tue, Mar 15, 2016 at 09:53:27AM -0500, Josh Cartwright wrote: > Hey Kyle- > > On Mon, Mar 14, 2016 at 04:55:08PM -0500, Kyle Roeschley wrote: > > From: Gratian Crisan <gratian.cri...@ni.com> > > From what I understand, this was mostly Aaron's work, so he should

Re: [PATCH 2/2] misc: nirtfeatures: physical interface elements

On Tue, Mar 15, 2016 at 09:53:27AM -0500, Josh Cartwright wrote: > Hey Kyle- > > On Mon, Mar 14, 2016 at 04:55:08PM -0500, Kyle Roeschley wrote: > > From: Gratian Crisan > > From what I understand, this was mostly Aaron's work, so he should get > authorship.

Re: [PATCH 1/2] misc: add nirtfeatures driver

On Mon, Mar 14, 2016 at 05:30:22PM -0500, Josh Cartwright wrote: > On Mon, Mar 14, 2016 at 03:05:59PM -0700, Greg KH wrote: > > On Mon, Mar 14, 2016 at 04:54:32PM -0500, Kyle Roeschley wrote: > > > From: Jeff Westfahl <jeff.westf...@ni.com> > > > > > > T

Re: [PATCH 1/2] misc: add nirtfeatures driver

On Mon, Mar 14, 2016 at 05:30:22PM -0500, Josh Cartwright wrote: > On Mon, Mar 14, 2016 at 03:05:59PM -0700, Greg KH wrote: > > On Mon, Mar 14, 2016 at 04:54:32PM -0500, Kyle Roeschley wrote: > > > From: Jeff Westfahl > > > > > > This driver introduces suppo

[PATCH 2/2] misc: nirtfeatures: physical interface elements

ssetto <aaron.rosse...@ni.com> Signed-off-by: Josh Cartwright <jo...@ni.com> Signed-off-by: Gratian Crisan <gratian.cri...@ni.com> Signed-off-by: Kyle Roeschley <kyle.roesch...@ni.com> --- drivers/misc/nirtfeatures.c | 753 1 file

[PATCH 2/2] misc: nirtfeatures: physical interface elements

Cartwright Signed-off-by: Gratian Crisan Signed-off-by: Kyle Roeschley --- drivers/misc/nirtfeatures.c | 753 1 file changed, 694 insertions(+), 59 deletions(-) diff --git a/drivers/misc/nirtfeatures.c b/drivers/misc/nirtfeatures.c index 37298f2..2feedb5

[PATCH 1/2] misc: add nirtfeatures driver

From: Jeff Westfahl <jeff.westf...@ni.com> This driver introduces support for hardware features of National Instruments real-time controllers. This is an ACPI device that exposes LEDs, switches, and watchdogs. Signed-off-by: Jeff Westfahl <jeff.westf...@ni.com> Signed-off-by: Ky

[PATCH 1/2] misc: add nirtfeatures driver

From: Jeff Westfahl This driver introduces support for hardware features of National Instruments real-time controllers. This is an ACPI device that exposes LEDs, switches, and watchdogs. Signed-off-by: Jeff Westfahl Signed-off-by: Kyle Roeschley --- drivers/misc/Kconfig| 9