[PATCH 2/5] usb: dwc2: fix dwc2_get_device_property for u8 and u16

t;) Signed-off-by: Stefan Wahren --- drivers/usb/dwc2/params.c | 12 1 file changed, 12 deletions(-) diff --git a/drivers/usb/dwc2/params.c b/drivers/usb/dwc2/params.c index fd5f7f8..2c7b624 100644 --- a/drivers/usb/dwc2/params.c +++ b/drivers/usb/dwc2/params.c @@ -247,8 +247,6 @@ s

[PATCH 5/5] usb: dwc2: fix kernel-doc for dwc2_set_param

Since there is no parameter @value replace it with @legacy. Fixes: 05ee799f202 ("usb: dwc2: Move gadget settings into core_params") Signed-off-by: Stefan Wahren --- drivers/usb/dwc2/params.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/dwc2/

[PATCH 0/5] usb: dwc2: fix parameter handling

This patch series fixes several parameter handling issues found on bcm2835 in gadget mode. It's based on Felipe's USB next. Stefan Wahren (5): usb: dwc2: Do not set host parameter in peripheral mode usb: dwc2: fix dwc2_get_device_property for u8 and u16 usb: dwc2: fix default value for DMA

[PATCH 0/5] usb: dwc2: fix parameter handling

This patch series fixes several parameter handling issues found on bcm2835 in gadget mode. It's based on Felipe's USB next. Stefan Wahren (5): usb: dwc2: Do not set host parameter in peripheral mode usb: dwc2: fix dwc2_get_device_property for u8 and u16 usb: dwc2: fix default value for DMA

[PATCH 3/5] usb: dwc2: fix default value for DMA support

The current defaults for DMA results on a non-DMA platform in a unnecessary error message: Invalid value 0 for param gadget-dma So fix this by using dma_capable as default value. Fixes: 9962b62f1be ("usb: dwc2: Deprecate g-use-dma binding") Signed-off-by: Stefan Wahren <stefan.wa

[PATCH 3/5] usb: dwc2: fix default value for DMA support

The current defaults for DMA results on a non-DMA platform in a unnecessary error message: Invalid value 0 for param gadget-dma So fix this by using dma_capable as default value. Fixes: 9962b62f1be ("usb: dwc2: Deprecate g-use-dma binding") Signed-off-by: Stefan Wahren --- driver

[PATCH 1/5] usb: dwc2: Do not set host parameter in peripheral mode

56 invalid for host_nperio_tx_fifo_size. Check HW configuration. 512 invalid for host_perio_tx_fifo_size. Check HW configuration. Fixes: 55e1040e424b ("usb: dwc2: Improve handling of host and device hwparams") Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- driver

[PATCH 4/5] usb: dwc2: gadget: fix default value for gadget-dma-desc

The current default for gadget DMA descriptor results on bcm2835 in a unnecessary error message: Invalid value 1 for param gadget-dma-desc So fix this by using hw->dma_desc_enable as default value. Fixes: dec4b55677e ("usb: dwc2: gadget: Add descriptor DMA parameter") Signed-o

[PATCH 1/5] usb: dwc2: Do not set host parameter in peripheral mode

56 invalid for host_nperio_tx_fifo_size. Check HW configuration. 512 invalid for host_perio_tx_fifo_size. Check HW configuration. Fixes: 55e1040e424b ("usb: dwc2: Improve handling of host and device hwparams") Signed-off-by: Stefan Wahren --- drivers/usb/dwc2/params.c | 12 ++-

[PATCH 4/5] usb: dwc2: gadget: fix default value for gadget-dma-desc

The current default for gadget DMA descriptor results on bcm2835 in a unnecessary error message: Invalid value 1 for param gadget-dma-desc So fix this by using hw->dma_desc_enable as default value. Fixes: dec4b55677e ("usb: dwc2: gadget: Add descriptor DMA parameter") Signed-o

[PATCH V2 2/2] ARM: bcm2835: Add names for the RPi Zero GPIO lines

This adds the GPIO names for the Raspberry Pi Zero. The GPIO lines of the RPi Zero are almost identical to the Model A+ except: * GPIO 35, 38, 40 and 45 are not connected * Status LED is active low Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- arch/arm/boot/dts/bcm2835-rpi-ze

[PATCH V2 2/2] ARM: bcm2835: Add names for the RPi Zero GPIO lines

This adds the GPIO names for the Raspberry Pi Zero. The GPIO lines of the RPi Zero are almost identical to the Model A+ except: * GPIO 35, 38, 40 and 45 are not connected * Status LED is active low Signed-off-by: Stefan Wahren --- arch/arm/boot/dts/bcm2835-rpi-zero.dts | 65

[PATCH V2 0/2] ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines

This patch series should fix and extend the patch V4 "ARM: bcm2835: Add names for the Raspberry Pi GPIO lines" from Linus Walleij and Eric Anholt. Changes in V2: - fix URL to firmware DT blob - drop dtsi file since Model A+ and Zero aren't identical Stefan Wahren (2): ARM: bc

[PATCH V2 0/2] ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines

This patch series should fix and extend the patch V4 "ARM: bcm2835: Add names for the Raspberry Pi GPIO lines" from Linus Walleij and Eric Anholt. Changes in V2: - fix URL to firmware DT blob - drop dtsi file since Model A+ and Zero aren't identical Stefan Wahren (2): ARM: bc

[PATCH V2 1/2] ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines

quot; for USB current limit (0=600mA, 1=1200mA) [1] - https://github.com/raspberrypi/firmware/blob/master/extra/dt-blob.dts Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- arch/arm/boot/dts/bcm2835-rpi-a-plus.dts |4 ++-- arch/arm/boot/dts/bcm2835-rpi-a.dts |4 ++-- arch

[PATCH V2 1/2] ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines

quot; for USB current limit (0=600mA, 1=1200mA) [1] - https://github.com/raspberrypi/firmware/blob/master/extra/dt-blob.dts Signed-off-by: Stefan Wahren --- arch/arm/boot/dts/bcm2835-rpi-a-plus.dts |4 ++-- arch/arm/boot/dts/bcm2835-rpi-a.dts |4 ++-- arch/arm/boot/dts/bcm2835-rpi-b-plu

Re: [PATCH 2/2] ARM: bcm2835: Add names for the Raspberry Pi Zero GPIO lines

> Eric Anholt <e...@anholt.net> hat am 15. November 2016 um 18:23 geschrieben: > > > Stefan Wahren <stefan.wah...@i2se.com> writes: > > > This adds the GPIO names for the Raspberry Pi Zero. Since there are no > > schematics for the RPi Zero use the sam

Re: [PATCH 2/2] ARM: bcm2835: Add names for the Raspberry Pi Zero GPIO lines

> Eric Anholt hat am 15. November 2016 um 18:23 geschrieben: > > > Stefan Wahren writes: > > > This adds the GPIO names for the Raspberry Pi Zero. Since there are no > > schematics for the RPi Zero use the same as the Model A+. > > These look good to me. I d

Re: [PATCH v9 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD

Hi Ksenija, > Ksenija Stanojevic hat am 2. November 2016 um > 08:38 geschrieben: > > > Add core files for low resolution analog-to-digital converter (mxs-lradc) > MFD driver. > > Signed-off-by: Ksenija Stanojevic > --- > Changes in

Re: [PATCH v9 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD

Hi Ksenija, > Ksenija Stanojevic hat am 2. November 2016 um > 08:38 geschrieben: > > > Add core files for low resolution analog-to-digital converter (mxs-lradc) > MFD driver. > > Signed-off-by: Ksenija Stanojevic > --- > Changes in v9: > - improve commit message. > > Changes in v8: > -

Re: [PATCH 1/2] pinctrl: bcm2835: Fix ints for GPIOs 28-31 & 46-53

nterrupt groups don't correspond > directly with the GPIO control banks. Instead, GPIOs 0-27 generate IRQ > GPIO0, 28-45 IRQ GPIO1 and 46-53 IRQ GPIO2. > > Awkwardly, the GPIOs for IRQ GPIO1 straddle two 32-entry GPIO banks, > so split out a function to process the interrupts for

Re: [PATCH 1/2] pinctrl: bcm2835: Fix ints for GPIOs 28-31 & 46-53

pond > directly with the GPIO control banks. Instead, GPIOs 0-27 generate IRQ > GPIO0, 28-45 IRQ GPIO1 and 46-53 IRQ GPIO2. > > Awkwardly, the GPIOs for IRQ GPIO1 straddle two 32-entry GPIO banks, > so split out a function to process the interrupts for a single GPIO > bank. > &g

[PATCH 2/2] ARM: bcm2835: Add names for the Raspberry Pi Zero GPIO lines

This adds the GPIO names for the Raspberry Pi Zero. Since there are no schematics for the RPi Zero use the same as the Model A+. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- arch/arm/boot/dts/bcm2835-rpi-a-plus-gpio.dtsi | 75 +++ arch/arm/boot/dts/bcm28

[PATCH 2/2] ARM: bcm2835: Add names for the Raspberry Pi Zero GPIO lines

This adds the GPIO names for the Raspberry Pi Zero. Since there are no schematics for the RPi Zero use the same as the Model A+. Signed-off-by: Stefan Wahren --- arch/arm/boot/dts/bcm2835-rpi-a-plus-gpio.dtsi | 75 +++ arch/arm/boot/dts/bcm2835-rpi-a-plus.dts | 76

[PATCH 0/2] ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines

This patch series should fix and extend the patch V4 "ARM: bcm2835: Add names for the Raspberry Pi GPIO lines" from Linus Walleij and Eric Anholt. Stefan Wahren (2): ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines ARM: bcm2835: Add names for the Raspberry Pi Zero GPIO lines

[PATCH 1/2] ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines

quot; for USB current limit (0=600mA, 1=1200mA) [1] - https://github.com/raspberrypi/documentation/blob/master/configuration/images/dt-blob.dts Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- arch/arm/boot/dts/bcm2835-rpi-a-plus.dts |4 ++-- arch/arm/boot/dts/bcm2835-rpi-a.dts

[PATCH 0/2] ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines

This patch series should fix and extend the patch V4 "ARM: bcm2835: Add names for the Raspberry Pi GPIO lines" from Linus Walleij and Eric Anholt. Stefan Wahren (2): ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines ARM: bcm2835: Add names for the Raspberry Pi Zero GPIO lines

[PATCH 1/2] ARM: bcm2835: Fix names for the Raspberry Pi GPIO lines

quot; for USB current limit (0=600mA, 1=1200mA) [1] - https://github.com/raspberrypi/documentation/blob/master/configuration/images/dt-blob.dts Signed-off-by: Stefan Wahren --- arch/arm/boot/dts/bcm2835-rpi-a-plus.dts |4 ++-- arch/arm/boot/dts/bcm2835-rpi-a.dts |4 ++-- arch/arm/b

Re: [PATCH] ARM64: dts: bcm2837-rpi-3-b: remove incorrect pwr LED

Hi Eric, [add Gerd to CC] > Eric Anholt hat am 11. November 2016 um 18:38 geschrieben: > > > From: Andrea Merello > > We are incorrectly defining the pwr LED, attaching it to a gpio line > that is wired to the Wi-Fi SDIO module (which fails due to

Re: [PATCH] ARM64: dts: bcm2837-rpi-3-b: remove incorrect pwr LED

Hi Eric, [add Gerd to CC] > Eric Anholt hat am 11. November 2016 um 18:38 geschrieben: > > > From: Andrea Merello > > We are incorrectly defining the pwr LED, attaching it to a gpio line > that is wired to the Wi-Fi SDIO module (which fails due to this). i agree with the intention of this

Re: [PATCH v9 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD

> Ksenija Stanojevic <ksenija.stanoje...@gmail.com> hat am 2. November 2016 um > 08:38 geschrieben: > > > Add core files for low resolution analog-to-digital converter (mxs-lradc) > MFD driver. > > Signed-off-by: Ksenija Stanojevic <ksenija.stanoje...@gma

Re: [PATCH v9 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD

> Ksenija Stanojevic hat am 2. November 2016 um > 08:38 geschrieben: > > > Add core files for low resolution analog-to-digital converter (mxs-lradc) > MFD driver. > > Signed-off-by: Ksenija Stanojevic Tested-by: Stefan Wahren for Patch 1 + 2 > --- > ... >

Re: [PATCH v3] ARM: bcm2835: Add names for the Raspberry Pi GPIO lines

> Eric Anholt <e...@anholt.net> hat am 31. Oktober 2016 um 18:53 geschrieben: > > > Stefan Wahren <stefan.wah...@i2se.com> writes: > > > Hi Eric, > > > >> Eric Anholt <e...@anholt.net> hat am 27. Oktober 2016 um 18:52 geschrieben: > >

Re: [PATCH v3] ARM: bcm2835: Add names for the Raspberry Pi GPIO lines

> Eric Anholt hat am 31. Oktober 2016 um 18:53 geschrieben: > > > Stefan Wahren writes: > > > Hi Eric, > > > >> Eric Anholt hat am 27. Oktober 2016 um 18:52 geschrieben: > >> > >> > >> From: Linus Walleij > >>

Re: [PATCH v3] ARM: bcm2835: Add names for the Raspberry Pi GPIO lines

Hi Eric, > Eric Anholt hat am 27. Oktober 2016 um 18:52 geschrieben: > > > From: Linus Walleij > > The idea is to give useful names to GPIO lines that an implementer > will be using from userspace, e.g. for maker type projects. These are >

Re: [PATCH v3] ARM: bcm2835: Add names for the Raspberry Pi GPIO lines

Hi Eric, > Eric Anholt hat am 27. Oktober 2016 um 18:52 geschrieben: > > > From: Linus Walleij > > The idea is to give useful names to GPIO lines that an implementer > will be using from userspace, e.g. for maker type projects. These are > user-visible using tools/gpio/lsgpio.c sorry for

Re: [PATCH v3 net-next 8/8] net: qualcomm: add QCA7000 UART driver

Am 18.10.2016 um 20:30 schrieb David Miller: > From: Stefan Wahren <stefan.wah...@i2se.com> > Date: Tue, 18 Oct 2016 13:27:34 +0200 > >> +void >> +qca_tty_receive(struct tty_struct *tty, const unsigned char *cp, char *fp, >> +int count) >&g

Re: [PATCH v3 net-next 8/8] net: qualcomm: add QCA7000 UART driver

Am 18.10.2016 um 20:30 schrieb David Miller: > From: Stefan Wahren > Date: Tue, 18 Oct 2016 13:27:34 +0200 > >> +void >> +qca_tty_receive(struct tty_struct *tty, const unsigned char *cp, char *fp, >> +int count) >> +{ >> +struct qcauar

[PATCH v3 net-next 1/8] net: qualcomm: remove unnecessary includes

Most of the includes in qca_7k.c are unnecessary so we better remove them. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/qca_7k.c | 4 1 file changed, 4 deletions(-) diff --git a/drivers/net/ethernet/qualcomm/qca_7k.c b/drivers/net/et

[PATCH v3 net-next 1/8] net: qualcomm: remove unnecessary includes

Most of the includes in qca_7k.c are unnecessary so we better remove them. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.c | 4 1 file changed, 4 deletions(-) diff --git a/drivers/net/ethernet/qualcomm/qca_7k.c b/drivers/net/ethernet/qualcomm/qca_7k.c index

[PATCH v3 net-next 2/8] net: qca_debug: use net_device_ops instead of direct call

There is no need to export qcaspi_netdev_open and qcaspi_netdev_close because they are also accessible via the net_device_ops. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/qca_debug.c | 5 +++-- drivers/net/ethernet/qualcomm/qca_spi.h | 3 --- 2

[PATCH v3 net-next 0/8] net: qualcomm: add QCA7000 UART driver

netif_trans_update() and dev_trans_start() [1] - https://github.com/IoE/qca7000 [2] - https://github.com/lategoodbye/busybox/commits/qca7k_support_1_24 Stefan Wahren (8): net: qualcomm: remove unnecessary includes net: qca_debug: use net_device_ops instead of direct call net: qualcomm: move

[PATCH v3 net-next 7/8] net: qualcomm: make qca_common a separate kernel module

In order to share common functions between QCA7000 SPI and UART protocol driver the qca_common needs to be a separate kernel module. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/Kconfig | 8 +++- drivers/net/ethernet/qualcomm/Makefile

[PATCH v3 net-next 2/8] net: qca_debug: use net_device_ops instead of direct call

There is no need to export qcaspi_netdev_open and qcaspi_netdev_close because they are also accessible via the net_device_ops. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_debug.c | 5 +++-- drivers/net/ethernet/qualcomm/qca_spi.h | 3 --- 2 files changed, 3 insertions

[PATCH v3 net-next 0/8] net: qualcomm: add QCA7000 UART driver

netif_trans_update() and dev_trans_start() [1] - https://github.com/IoE/qca7000 [2] - https://github.com/lategoodbye/busybox/commits/qca7k_support_1_24 Stefan Wahren (8): net: qualcomm: remove unnecessary includes net: qca_debug: use net_device_ops instead of direct call net: qualcomm: move

[PATCH v3 net-next 7/8] net: qualcomm: make qca_common a separate kernel module

In order to share common functions between QCA7000 SPI and UART protocol driver the qca_common needs to be a separate kernel module. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/Kconfig | 8 +++- drivers/net/ethernet/qualcomm/Makefile | 5 +++-- drivers/net

[PATCH v3 net-next 8/8] net: qualcomm: add QCA7000 UART driver

This patch adds the Ethernet over UART driver for the Qualcomm QCA7000 HomePlug GreenPHY. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/Kconfig | 12 + drivers/net/ethernet/qualcomm/Makefile | 2 + drivers/net/ethernet/qualcomm/qca_co

[PATCH v3 net-next 8/8] net: qualcomm: add QCA7000 UART driver

This patch adds the Ethernet over UART driver for the Qualcomm QCA7000 HomePlug GreenPHY. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/Kconfig | 12 + drivers/net/ethernet/qualcomm/Makefile | 2 + drivers/net/ethernet/qualcomm/qca_common.h | 6 + drivers/net

[PATCH v3 net-next 6/8] net: qualcomm: prepare frame decoding for UART driver

Unfortunately the frame format is not exactly identical between SPI and UART. In case of SPI there is an additional HW length at the beginning. So store the initial state to make the decoding state machine more flexible and easy to extend for UART support. Signed-off-by: Stefan Wahren <stefan.

[PATCH v3 net-next 3/8] net: qualcomm: move qcaspi_tx_cmd to qca_spi.c

The function qcaspi_tx_cmd() is only called from qca_spi.c. So we better move it there. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/qca_7k.c | 24 drivers/net/ethernet/qualcomm/qca_7k.h | 1 - drivers/net/ethernet/qu

[PATCH v3 net-next 5/8] net: qualcomm: move MTU handling to qca_common

The MTU of the QCA7000 is independent from it's host interface (UART,SPI). So move the change_mtu function to qca_common. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/qca_common.c | 11 +++ drivers/net/ethernet/qualcomm/qca_common.

[PATCH v3 net-next 3/8] net: qualcomm: move qcaspi_tx_cmd to qca_spi.c

The function qcaspi_tx_cmd() is only called from qca_spi.c. So we better move it there. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.c | 24 drivers/net/ethernet/qualcomm/qca_7k.h | 1 - drivers/net/ethernet/qualcomm/qca_spi.c | 24

[PATCH v3 net-next 5/8] net: qualcomm: move MTU handling to qca_common

The MTU of the QCA7000 is independent from it's host interface (UART,SPI). So move the change_mtu function to qca_common. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_common.c | 11 +++ drivers/net/ethernet/qualcomm/qca_common.h | 3 +++ drivers/net/ethernet

[PATCH v3 net-next 6/8] net: qualcomm: prepare frame decoding for UART driver

Unfortunately the frame format is not exactly identical between SPI and UART. In case of SPI there is an additional HW length at the beginning. So store the initial state to make the decoding state machine more flexible and easy to extend for UART support. Signed-off-by: Stefan Wahren

[PATCH v3 net-next 4/8] net: qualcomm: rename qca_framing.c to qca_common.c

As preparation for the upcoming UART driver we need a module which contains common functions for both interfaces. The module qca_framing is a good candidate but renaming to qca_common would make it clear. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qu

[PATCH v3 net-next 4/8] net: qualcomm: rename qca_framing.c to qca_common.c

As preparation for the upcoming UART driver we need a module which contains common functions for both interfaces. The module qca_framing is a good candidate but renaming to qca_common would make it clear. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/Makefile | 2

Re: [PATCH v7 0/5] mxs-lradc: Split driver into MFD

Hi Ksenija, > Ksenija Stanojevic hat am 2. Oktober 2016 um > 16:15 geschrieben: > > > Split existing driver mxs-lradc into MFD with touchscreen and > IIO part. i'm back from holidays and wanted to test your patch series. Unfortunately patch 1-3 looks broken to

Re: [PATCH v7 0/5] mxs-lradc: Split driver into MFD

Hi Ksenija, > Ksenija Stanojevic hat am 2. Oktober 2016 um > 16:15 geschrieben: > > > Split existing driver mxs-lradc into MFD with touchscreen and > IIO part. i'm back from holidays and wanted to test your patch series. Unfortunately patch 1-3 looks broken to me. Maybe you should wait for

Re: [PATCH 4/4] staging/vchi: Remove dependency on CONFIG_BROKEN.

Hi Greg, > Greg Kroah-Hartman <gre...@linuxfoundation.org> hat am 15. Oktober 2016 um > 13:27 geschrieben: > > > On Sat, Oct 15, 2016 at 10:35:25AM +0200, Stefan Wahren wrote: > > > > > Greg Kroah-Hartman <gre...@linuxfoundation.org> hat am 1

Re: [PATCH 4/4] staging/vchi: Remove dependency on CONFIG_BROKEN.

Hi Greg, > Greg Kroah-Hartman hat am 15. Oktober 2016 um > 13:27 geschrieben: > > > On Sat, Oct 15, 2016 at 10:35:25AM +0200, Stefan Wahren wrote: > > > > > Greg Kroah-Hartman hat am 13. Oktober 2016 um > > > 09:05 geschrieben: > > > >

Re: [PATCH 4/4] staging/vchi: Remove dependency on CONFIG_BROKEN.

> Greg Kroah-Hartman hat am 13. Oktober 2016 um > 09:05 geschrieben: > > > On Mon, Oct 03, 2016 at 11:52:09AM -0700, Eric Anholt wrote: > > The driver builds now. > > > > Signed-off-by: Eric Anholt > > --- > >

Re: [PATCH 4/4] staging/vchi: Remove dependency on CONFIG_BROKEN.

> Greg Kroah-Hartman hat am 13. Oktober 2016 um > 09:05 geschrieben: > > > On Mon, Oct 03, 2016 at 11:52:09AM -0700, Eric Anholt wrote: > > The driver builds now. > > > > Signed-off-by: Eric Anholt > > --- > > drivers/staging/vc04_services/Kconfig | 2 +- > > 1 file changed, 1 insertion(+),

Re: [PATCH 3/4] ARM: bcm2835: Add #define for VCHIQ property message.

> Stefan Wahren <stefan.wah...@i2se.com> hat am 15. Oktober 2016 um 09:53 > geschrieben: > > > Hi Greg, > > > Eric Anholt <e...@anholt.net> hat am 3. Oktober 2016 um 20:52 geschrieben: > > > > > > This comes from the downstream tree

Re: [PATCH 3/4] ARM: bcm2835: Add #define for VCHIQ property message.

> Stefan Wahren hat am 15. Oktober 2016 um 09:53 > geschrieben: > > > Hi Greg, > > > Eric Anholt hat am 3. Oktober 2016 um 20:52 geschrieben: > > > > > > This comes from the downstream tree and is needed for the new VCHIQ > > driver in st

Re: [PATCH 3/4] ARM: bcm2835: Add #define for VCHIQ property message.

Hi Greg, > Eric Anholt hat am 3. Oktober 2016 um 20:52 geschrieben: > > > This comes from the downstream tree and is needed for the new VCHIQ > driver in staging. maybe it's not clear from the commit message, but RPI_FIRMWARE_VCHIQ_INIT is already used in

Re: [PATCH 3/4] ARM: bcm2835: Add #define for VCHIQ property message.

Hi Greg, > Eric Anholt hat am 3. Oktober 2016 um 20:52 geschrieben: > > > This comes from the downstream tree and is needed for the new VCHIQ > driver in staging. maybe it's not clear from the commit message, but RPI_FIRMWARE_VCHIQ_INIT is already used in

Re: [PATCH RFC v2 net-next 0/8] net: qualcomm: add QCA7000 UART driver

> Stefan Wahren <stefan.wah...@i2se.com> hat am 26. September 2016 um 13:07 > geschrieben: > > > The Qualcomm QCA7000 HomePlug GreenPHY supports two interfaces: > UART and SPI. This patch series adds the missing support for UART. > > This driver based on the Q

Re: [PATCH RFC v2 net-next 0/8] net: qualcomm: add QCA7000 UART driver

> Stefan Wahren hat am 26. September 2016 um 13:07 > geschrieben: > > > The Qualcomm QCA7000 HomePlug GreenPHY supports two interfaces: > UART and SPI. This patch series adds the missing support for UART. > > This driver based on the Qualcomm code [1], but contai

Re: [PATCH v6 1/4] mfd: mxs-lradc: Add support for mxs-lradc MFD

Hi Lee, [add Rob and Mark] > Lee Jones <lee.jo...@linaro.org> hat am 29. September 2016 um 19:15 > geschrieben: > > > On Thu, 29 Sep 2016, Stefan Wahren wrote: > > > Lee Jones <lee.jo...@linaro.org> hat am 28. September 2016 um 03:05 > > > geschri

Re: [PATCH v6 1/4] mfd: mxs-lradc: Add support for mxs-lradc MFD

Hi Lee, [add Rob and Mark] > Lee Jones hat am 29. September 2016 um 19:15 > geschrieben: > > > On Thu, 29 Sep 2016, Stefan Wahren wrote: > > > Lee Jones hat am 28. September 2016 um 03:05 > > > geschrieben: > > > > > >

Re: [PATCH v3 2/7] i2c: bcm2835: Protect against unexpected TXW/RXR interrupts

> Noralf Trønnes hat am 29. September 2016 um 00:22 > geschrieben: > > > > Den 29.09.2016 00:00, skrev Eric Anholt: > > Noralf Trønnes writes: > > > >> If an unexpected TXW or RXR interrupt occurs (msg_buf_remaining == 0), > >> the driver has no way to

Re: [PATCH v3 2/7] i2c: bcm2835: Protect against unexpected TXW/RXR interrupts

> Noralf Trønnes hat am 29. September 2016 um 00:22 > geschrieben: > > > > Den 29.09.2016 00:00, skrev Eric Anholt: > > Noralf Trønnes writes: > > > >> If an unexpected TXW or RXR interrupt occurs (msg_buf_remaining == 0), > >> the driver has no way to fill/drain the FIFO to stop the

Re: [PATCH v6 1/4] mfd: mxs-lradc: Add support for mxs-lradc MFD

Hi Lee, > Lee Jones hat am 28. September 2016 um 03:05 > geschrieben: > > > On Sat, 17 Sep 2016, Ksenija Stanojevic wrote: > > > + > > +static int mxs_lradc_probe(struct platform_device *pdev) > > +{ > > + const struct of_device_id *of_id; > > + struct device *dev =

Re: [PATCH v6 1/4] mfd: mxs-lradc: Add support for mxs-lradc MFD

Hi Lee, > Lee Jones hat am 28. September 2016 um 03:05 > geschrieben: > > > On Sat, 17 Sep 2016, Ksenija Stanojevic wrote: > > > + > > +static int mxs_lradc_probe(struct platform_device *pdev) > > +{ > > + const struct of_device_id *of_id; > > + struct device *dev = >dev; > > + struct

Re: [PATCH v2 8/8] ARM: bcm2835: Disable i2c2 in the Device Tree

> Noralf Trønnes hat am 27. September 2016 um 13:57 > geschrieben: > > > i2c2 is connected to the HDMI connector and is controlled by the > firmware. Disable it to stay out of harms way. Until this point the commit message is okay, the rest is more confusing. Btw this

Re: [PATCH v2 8/8] ARM: bcm2835: Disable i2c2 in the Device Tree

> Noralf Trønnes hat am 27. September 2016 um 13:57 > geschrieben: > > > i2c2 is connected to the HDMI connector and is controlled by the > firmware. Disable it to stay out of harms way. Until this point the commit message is okay, the rest is more confusing. Btw this should avoid a warning

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

> Stephen Warren <swar...@wwwdotorg.org> hat am 26. September 2016 um 18:38 > geschrieben: > > > On 09/23/2016 12:39 PM, Stefan Wahren wrote: > > Hi Eric, > > > >> Eric Anholt <e...@anholt.net> hat am 19. September 2016 um 18:13 > >>

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

> Stephen Warren hat am 26. September 2016 um 18:38 > geschrieben: > > > On 09/23/2016 12:39 PM, Stefan Wahren wrote: > > Hi Eric, > > > >> Eric Anholt hat am 19. September 2016 um 18:13 > >> geschrieben: > >> > >> >

[PATCH RFC v2 net-next 4/8] net: qualcomm: rename qca_framing.c to qca_common.c

As preparation for the upcoming UART driver we need a module which contains common functions for both interfaces. The module qca_framing is a good candidate but renaming to qca_common would make it clear. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qu

[PATCH RFC v2 net-next 2/8] net: qca_debug: use net_device_ops instead of direct call

There is no need to export qcaspi_netdev_open and qcaspi_netdev_close because they are also accessible via the net_device_ops. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/qca_debug.c | 5 +++-- drivers/net/ethernet/qualcomm/qca_spi.h | 3 --- 2

[PATCH RFC v2 net-next 2/8] net: qca_debug: use net_device_ops instead of direct call

There is no need to export qcaspi_netdev_open and qcaspi_netdev_close because they are also accessible via the net_device_ops. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_debug.c | 5 +++-- drivers/net/ethernet/qualcomm/qca_spi.h | 3 --- 2 files changed, 3 insertions

[PATCH RFC v2 net-next 4/8] net: qualcomm: rename qca_framing.c to qca_common.c

As preparation for the upcoming UART driver we need a module which contains common functions for both interfaces. The module qca_framing is a good candidate but renaming to qca_common would make it clear. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/Makefile | 2

[PATCH RFC v2 net-next 5/8] net: qualcomm: move MTU handling to qca_common

The MTU of the QCA7000 is independent from it's host interface (UART,SPI). So move the change_mtu function to qca_common. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/qca_common.c | 11 +++ drivers/net/ethernet/qualcomm/qca_common.

[PATCH RFC v2 net-next 5/8] net: qualcomm: move MTU handling to qca_common

The MTU of the QCA7000 is independent from it's host interface (UART,SPI). So move the change_mtu function to qca_common. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_common.c | 11 +++ drivers/net/ethernet/qualcomm/qca_common.h | 3 +++ drivers/net/ethernet

[PATCH RFC v2 net-next 6/8] net: qualcomm: prepare frame decoding for UART driver

Unfortunately the frame format is not exactly identical between SPI and UART. In case of SPI there is an additional HW length at the beginning. So store the initial state to make the decoding state machine more flexible and easy to extend for UART support. Signed-off-by: Stefan Wahren <stefan.

[PATCH RFC v2 net-next 6/8] net: qualcomm: prepare frame decoding for UART driver

Unfortunately the frame format is not exactly identical between SPI and UART. In case of SPI there is an additional HW length at the beginning. So store the initial state to make the decoding state machine more flexible and easy to extend for UART support. Signed-off-by: Stefan Wahren

[PATCH RFC v2 net-next 7/8] net: qualcomm: make qca_common a separate kernel module

In order to share common functions between QCA7000 SPI and UART protocol driver the qca_common needs to be a separate kernel module. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/Kconfig | 8 +++- drivers/net/ethernet/qualcomm/Makefile

[PATCH RFC v2 net-next 7/8] net: qualcomm: make qca_common a separate kernel module

In order to share common functions between QCA7000 SPI and UART protocol driver the qca_common needs to be a separate kernel module. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/Kconfig | 8 +++- drivers/net/ethernet/qualcomm/Makefile | 5 +++-- drivers/net

[PATCH RFC v2 net-next 8/8] net: qualcomm: add QCA7000 UART driver

This patch adds the Ethernet over UART driver for the Qualcomm QCA7000 HomePlug GreenPHY. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/Kconfig | 12 + drivers/net/ethernet/qualcomm/Makefile | 2 + drivers/net/ethernet/qualcomm/qca_co

[PATCH RFC v2 net-next 1/8] net: qualcomm: remove unnecessary includes

Most of the includes in qca_7k.c are unnecessary so we better remove them. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/qca_7k.c | 4 1 file changed, 4 deletions(-) diff --git a/drivers/net/ethernet/qualcomm/qca_7k.c b/drivers/net/et

[PATCH RFC v2 net-next 8/8] net: qualcomm: add QCA7000 UART driver

This patch adds the Ethernet over UART driver for the Qualcomm QCA7000 HomePlug GreenPHY. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/Kconfig | 12 + drivers/net/ethernet/qualcomm/Makefile | 2 + drivers/net/ethernet/qualcomm/qca_common.h | 6 + drivers/net

[PATCH RFC v2 net-next 1/8] net: qualcomm: remove unnecessary includes

Most of the includes in qca_7k.c are unnecessary so we better remove them. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.c | 4 1 file changed, 4 deletions(-) diff --git a/drivers/net/ethernet/qualcomm/qca_7k.c b/drivers/net/ethernet/qualcomm/qca_7k.c index

[PATCH RFC v2 net-next 3/8] net: qualcomm: move qcaspi_tx_cmd to qca_spi.c

The function qcaspi_tx_cmd() is only called from qca_spi.c. So we better move it there. Signed-off-by: Stefan Wahren <stefan.wah...@i2se.com> --- drivers/net/ethernet/qualcomm/qca_7k.c | 24 drivers/net/ethernet/qualcomm/qca_7k.h | 1 - drivers/net/ethernet/qu

[PATCH RFC v2 net-next 0/8] net: qualcomm: add QCA7000 UART driver

] - https://github.com/IoE/qca7000 [2] - https://github.com/lategoodbye/busybox/commits/qca7k_support_1_24 Stefan Wahren (8): net: qualcomm: remove unnecessary includes net: qca_debug: use net_device_ops instead of direct call net: qualcomm: move qcaspi_tx_cmd to qca_spi.c net: qualcomm: rename

[PATCH RFC v2 net-next 3/8] net: qualcomm: move qcaspi_tx_cmd to qca_spi.c

The function qcaspi_tx_cmd() is only called from qca_spi.c. So we better move it there. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.c | 24 drivers/net/ethernet/qualcomm/qca_7k.h | 1 - drivers/net/ethernet/qualcomm/qca_spi.c | 24

[PATCH RFC v2 net-next 0/8] net: qualcomm: add QCA7000 UART driver

] - https://github.com/IoE/qca7000 [2] - https://github.com/lategoodbye/busybox/commits/qca7k_support_1_24 Stefan Wahren (8): net: qualcomm: remove unnecessary includes net: qca_debug: use net_device_ops instead of direct call net: qualcomm: move qcaspi_tx_cmd to qca_spi.c net: qualcomm: rename

Re: [PATCH 2/3] gpio: Add a driver for the Raspberry Pi's firmware GPIO calls.

Hi Eric, > Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: > > > This driver will be used for accessing the FXL6408 GPIO exander on the > Pi3. We can't drive it directly from Linux because the firmware is > continuously polling one of the expander's lines to do

Re: [PATCH 2/3] gpio: Add a driver for the Raspberry Pi's firmware GPIO calls.

Hi Eric, > Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: > > > This driver will be used for accessing the FXL6408 GPIO exander on the > Pi3. We can't drive it directly from Linux because the firmware is > continuously polling one of the expander's lines to do its > undervoltage

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

Hi Eric, > Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: > > > The RPi firmware exposes all of the board's GPIO lines through > property calls. Linux chooses to control most lines directly through > the pinctrl driver, but for the FXL6408 GPIO expander on the

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

Hi Eric, > Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: > > > The RPi firmware exposes all of the board's GPIO lines through > property calls. Linux chooses to control most lines directly through > the pinctrl driver, but for the FXL6408 GPIO expander on the Pi3, we > need to

<    4   5   6   7   8   9   10   11   12   13   >