RE: [PATCH 1/2] watchdog: uniphier: add UniPhier watchdog driver

Hi Hayashibara-san > a/Documentation/devicetree/bindings/watchdog/uniphier-wdt.txt > b/Documentation/devicetree/bindings/watchdog/uniphier-wdt.txt > new file mode 100644 > index 000..a59d1ba > --- /dev/null > +++ b/Documentation/devicetree/bindings/watchdog/uniphier-wdt.txt > @@ -0,0 +1,20

RE: [PATCH 1/2] watchdog: uniphier: add UniPhier watchdog driver

Hi Hayashibara-san > a/Documentation/devicetree/bindings/watchdog/uniphier-wdt.txt > b/Documentation/devicetree/bindings/watchdog/uniphier-wdt.txt > new file mode 100644 > index 000..a59d1ba > --- /dev/null > +++ b/Documentation/devicetree/bindings/watchdog/uniphier-wdt.txt > @@ -0,0 +1,20

Re: Patch 0727d35de ("Make initramfs honor CONFIG_DEVTMPFS_MOUNT") breaks boot

On 05/23/2017 06:08 PM, Yury Norov wrote: >> It was 2 years ago, but AFAIR I took the Ubuntu image here: >> http://cdimage.ubuntu.com/ubuntu-base/releases/14.04.1/release/ubuntu-base-14.04.1-core-arm64.tar.gz Have you applied updates since then? (Maybe they fixed their init script since 2 years

Re: Patch 0727d35de ("Make initramfs honor CONFIG_DEVTMPFS_MOUNT") breaks boot

On 05/23/2017 06:08 PM, Yury Norov wrote: >> It was 2 years ago, but AFAIR I took the Ubuntu image here: >> http://cdimage.ubuntu.com/ubuntu-base/releases/14.04.1/release/ubuntu-base-14.04.1-core-arm64.tar.gz Have you applied updates since then? (Maybe they fixed their init script since 2 years

Re: [patch] compiler, clang: suppress warning for unused static inline functions

* Matthias Kaehlcke wrote: > El Wed, May 24, 2017 at 02:01:15PM -0700 David Rientjes ha dit: > > > GCC explicitly does not warn for unused static inline functions for > > -Wunused-function. The manual states: > > > > Warn whenever a static function is declared but not

Re: [patch] compiler, clang: suppress warning for unused static inline functions

* Matthias Kaehlcke wrote: > El Wed, May 24, 2017 at 02:01:15PM -0700 David Rientjes ha dit: > > > GCC explicitly does not warn for unused static inline functions for > > -Wunused-function. The manual states: > > > > Warn whenever a static function is declared but not defined or > >

Re: Fwd: Watchdog detected hard lockup.

On (05/25/17 11:14), Sumit Gemini wrote: >Thanks Sergey and i forgot to add other guys in discussion. >  > >[1]lkml.kernel.org/r/20170509082859.854-1-sergey.senozhat...@gmail.com > >Now I'm going for backporting the kernel with RFC, as you suggested me >yesterday. or you can

Re: Fwd: Watchdog detected hard lockup.

On (05/25/17 11:14), Sumit Gemini wrote: >Thanks Sergey and i forgot to add other guys in discussion. >  > >[1]lkml.kernel.org/r/20170509082859.854-1-sergey.senozhat...@gmail.com > >Now I'm going for backporting the kernel with RFC, as you suggested me >yesterday. or you can

Re: [PATCH/RFC] iio: hi8435: do not enable all events by default

24.05.2017 22:27, Jonathan Cameron wrote: > On Tue, 23 May 2017 11:08:30 +0300 > Nikita Yushchenko wrote: > >> Having all events enabled by default is misleading. >> Userspace should explicitly enable events they want to receive. >> >> Signed-off-by: Nikita

Re: [PATCH/RFC] iio: hi8435: do not enable all events by default

24.05.2017 22:27, Jonathan Cameron wrote: > On Tue, 23 May 2017 11:08:30 +0300 > Nikita Yushchenko wrote: > >> Having all events enabled by default is misleading. >> Userspace should explicitly enable events they want to receive. >> >> Signed-off-by: Nikita Yushchenko > I agree in principle,

[PATCH v5 03/10] VAS: Define vas_init() and vas_exit()

Implement vas_init() and vas_exit() functions for a new VAS module. This VAS module is essentially a library for other device drivers and kernel users of the NX coprocessors like NX-842 and NX-GZIP. In the future this will be extended to add support for user space to access the NX coprocessors.

[PATCH v5 03/10] VAS: Define vas_init() and vas_exit()

Implement vas_init() and vas_exit() functions for a new VAS module. This VAS module is essentially a library for other device drivers and kernel users of the NX coprocessors like NX-842 and NX-GZIP. In the future this will be extended to add support for user space to access the NX coprocessors.

[PATCH v5 02/10] Move GET_FIELD/SET_FIELD to vas.h

Move the GET_FIELD and SET_FIELD macros to vas.h as VAS and other users of VAS, including NX-842 can use those macros. There is a lot of related code between the VAS/NX kernel drivers and skiboot. For consistency switch the order of parameters in SET_FIELD to match the order in skiboot.

[PATCH v5 02/10] Move GET_FIELD/SET_FIELD to vas.h

Move the GET_FIELD and SET_FIELD macros to vas.h as VAS and other users of VAS, including NX-842 can use those macros. There is a lot of related code between the VAS/NX kernel drivers and skiboot. For consistency switch the order of parameters in SET_FIELD to match the order in skiboot.

[PATCH v5 06/10] VAS: Define helpers to alloc/free windows

Define helpers to allocate/free VAS window objects. These will be used in follow-on patches when opening/closing windows. Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/platforms/powernv/vas-window.c | 61 + 1 file changed, 61

[PATCH v5 06/10] VAS: Define helpers to alloc/free windows

Define helpers to allocate/free VAS window objects. These will be used in follow-on patches when opening/closing windows. Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/platforms/powernv/vas-window.c | 61 + 1 file changed, 61 insertions(+) diff --git

[PATCH v5 08/10] VAS: Define vas_win_close() interface

Define the vas_win_close() interface which should be used to close a send or receive windows. While the hardware configurations required to open send and receive windows differ, the configuration to close a window is the same for both. So we use a single interface to close the window.

[PATCH v5 08/10] VAS: Define vas_win_close() interface

Define the vas_win_close() interface which should be used to close a send or receive windows. While the hardware configurations required to open send and receive windows differ, the configuration to close a window is the same for both. So we use a single interface to close the window.

[PATCH v5 10/10] VAS: Define copy/paste interfaces

Define interfaces (wrappers) to the 'copy' and 'paste' instructions (which are new in PowerISA 3.0). These are intended to be used to by NX driver(s) to submit Coprocessor Request Blocks (CRBs) to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu ---

[PATCH v5 09/10] VAS: Define vas_tx_win_open()

Define an interface to open a VAS send window. This interface is intended to be used the Nest Accelerator (NX) driver(s) to open a send window and use it to submit compression/encryption requests to a VAS receive window. The receive window, identified by the [vasid, cop] parameters, must already

[PATCH v5 10/10] VAS: Define copy/paste interfaces

Define interfaces (wrappers) to the 'copy' and 'paste' instructions (which are new in PowerISA 3.0). These are intended to be used to by NX driver(s) to submit Coprocessor Request Blocks (CRBs) to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v4] - Export

[PATCH v5 09/10] VAS: Define vas_tx_win_open()

Define an interface to open a VAS send window. This interface is intended to be used the Nest Accelerator (NX) driver(s) to open a send window and use it to submit compression/encryption requests to a VAS receive window. The receive window, identified by the [vasid, cop] parameters, must already

[PATCH v5 05/10] VAS: Define helpers to init window context

Define helpers to initialize window context registers of the VAS hardware. These will be used in follow-on patches when opening/closing VAS windows. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v5] - Fix: Copy the FIFO address into LFIFO_BAR register as is

[PATCH v5 05/10] VAS: Define helpers to init window context

Define helpers to initialize window context registers of the VAS hardware. These will be used in follow-on patches when opening/closing VAS windows. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v5] - Fix: Copy the FIFO address into LFIFO_BAR register as is (don't shift

[PATCH v5 04/10] VAS: Define helpers for access MMIO regions

Define some helper functions to access the MMIO regions. We use these in a follow-on patches to read/write VAS hardware registers. These helpers are also used to later issue 'paste' instructions to submit requests to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu

[PATCH v5 07/10] VAS: Define vas_rx_win_open() interface

Define the vas_rx_win_open() interface. This interface is intended to be used by the Nest Accelerator (NX) driver(s) to setup receive windows for one or more NX engines (which implement compression/encryption algorithms in the hardware). Follow-on patches will provide an interface to close the

[PATCH v5 00/11] Enable VAS

Power9 introduces a hardware subsystem referred to as the Virtual Accelerator Switchboard (VAS). VAS allows kernel subsystems and user space processes to directly access the Nest Accelerator (NX) engines which implement compression and encryption algorithms in the hardware. NX has been in Power

[PATCH v5 01/10] VAS: Define macros, register fields and structures

Define macros for the VAS hardware registers and bit-fields as well as couple of data structures needed by the VAS driver. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v4] - [Michael Neuling] Move VAS code to arch/powerpc; Reorg vas.h and

[PATCH v5 04/10] VAS: Define helpers for access MMIO regions

Define some helper functions to access the MMIO regions. We use these in a follow-on patches to read/write VAS hardware registers. These helpers are also used to later issue 'paste' instructions to submit requests to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu --- Changelog [v5]:

[PATCH v5 07/10] VAS: Define vas_rx_win_open() interface

Define the vas_rx_win_open() interface. This interface is intended to be used by the Nest Accelerator (NX) driver(s) to setup receive windows for one or more NX engines (which implement compression/encryption algorithms in the hardware). Follow-on patches will provide an interface to close the

[PATCH v5 00/11] Enable VAS

Power9 introduces a hardware subsystem referred to as the Virtual Accelerator Switchboard (VAS). VAS allows kernel subsystems and user space processes to directly access the Nest Accelerator (NX) engines which implement compression and encryption algorithms in the hardware. NX has been in Power

[PATCH v5 01/10] VAS: Define macros, register fields and structures

Define macros for the VAS hardware registers and bit-fields as well as couple of data structures needed by the VAS driver. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v4] - [Michael Neuling] Move VAS code to arch/powerpc; Reorg vas.h and vas-internal.h to kernel and uapi

Re: [PATCH] mm/vmalloc: a slight change of compare target in __insert_vmap_area()

On Wed 24-05-17 23:07:30, Wei Yang wrote: > On Wed, May 24, 2017 at 02:11:35PM +0200, Michal Hocko wrote: > >On Wed 24-05-17 18:03:47, Wei Yang wrote: > >> The vmap RB tree store the elements in order and no overlap between any of > >> them. The comparison in __insert_vmap_area() is to decide

Re: [PATCH] mm/vmalloc: a slight change of compare target in __insert_vmap_area()

On Wed 24-05-17 23:07:30, Wei Yang wrote: > On Wed, May 24, 2017 at 02:11:35PM +0200, Michal Hocko wrote: > >On Wed 24-05-17 18:03:47, Wei Yang wrote: > >> The vmap RB tree store the elements in order and no overlap between any of > >> them. The comparison in __insert_vmap_area() is to decide

Re: [PATCH] mm/zsmalloc: fix -Wunneeded-internal-declaration warning

On Tue, May 23, 2017 at 10:38:57PM -0700, Nick Desaulniers wrote: > is_first_page() is only called from the macro VM_BUG_ON_PAGE() which is > only compiled in as a runtime check when CONFIG_DEBUG_VM is set, > otherwise is checked at compile time and not actually compiled in. > > Fixes the

Re: [PATCH] mm/zsmalloc: fix -Wunneeded-internal-declaration warning

On Tue, May 23, 2017 at 10:38:57PM -0700, Nick Desaulniers wrote: > is_first_page() is only called from the macro VM_BUG_ON_PAGE() which is > only compiled in as a runtime check when CONFIG_DEBUG_VM is set, > otherwise is checked at compile time and not actually compiled in. > > Fixes the

[PATCH] tpm, tpmrm: Mark tpmrm_write as static

sparse complains that tpmrm_write can be made static, and since it is right we make it static. Signed-off-by: Peter Huewe --- drivers/char/tpm/tpmrm-dev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/char/tpm/tpmrm-dev.c

[PATCH] tpm, tpmrm: Mark tpmrm_write as static

sparse complains that tpmrm_write can be made static, and since it is right we make it static. Signed-off-by: Peter Huewe --- drivers/char/tpm/tpmrm-dev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/char/tpm/tpmrm-dev.c b/drivers/char/tpm/tpmrm-dev.c index

Aw: Re: [PATCH] tpm: remove struct tpm_pcrextend_in

> Removed struct tpm_pcrextend_in as it is not used for anything anymore. > > Signed-off-by: Jarkko Sakkinen LGTM. Reviewed-by: Peter Huewe > --- > drivers/char/tpm/tpm.h | 6 -- > 1 file changed, 6 deletions(-) > > diff --git

Aw: Re: [PATCH] tpm: remove struct tpm_pcrextend_in

> Removed struct tpm_pcrextend_in as it is not used for anything anymore. > > Signed-off-by: Jarkko Sakkinen LGTM. Reviewed-by: Peter Huewe > --- > drivers/char/tpm/tpm.h | 6 -- > 1 file changed, 6 deletions(-) > > diff --git a/drivers/char/tpm/tpm.h b/drivers/char/tpm/tpm.h > index

Re: [PATCH v4 04/11] VAS: Define vas_init() and vas_exit()

Tyrel Datwyler [tyr...@linux.vnet.ibm.com] wrote: > > + vinst = _instances[0]; > > + for_each_node_by_name(dn, "vas") { > > + rc = init_vas_instance(dn, vinst); > > + if (rc) { > > + pr_err("Error %d initializing VAS instance %ld\n", rc, > > +

Re: [PATCH v4 04/11] VAS: Define vas_init() and vas_exit()

Tyrel Datwyler [tyr...@linux.vnet.ibm.com] wrote: > > + vinst = _instances[0]; > > + for_each_node_by_name(dn, "vas") { > > + rc = init_vas_instance(dn, vinst); > > + if (rc) { > > + pr_err("Error %d initializing VAS instance %ld\n", rc, > > +

Aw: Re: [PATCH] tpm, tpm_infineon: remove useless snprintf() calls

> The memory copy from rodata to stack is useless. > > Signed-off-by: Jarkko Sakkinen After review, yes that should work. Reviewed-by: Peter Huewe > --- > drivers/char/tpm/tpm_infineon.c | 8 > 1 file changed, 4 insertions(+), 4

Aw: Re: [PATCH] tpm, tpm_infineon: remove useless snprintf() calls

> The memory copy from rodata to stack is useless. > > Signed-off-by: Jarkko Sakkinen After review, yes that should work. Reviewed-by: Peter Huewe > --- > drivers/char/tpm/tpm_infineon.c | 8 > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git

[PATCH v2 2/3] rtmutex: update rt-mutex

The rtmutex remove a pending owner bit in in rt_mutex::owner, in commit 8161239a8bcc ("rtmutex: Simplify PI algorithm and make highest prio task get lock") But the document was changed accordingly. Updating it to a meaningful state. BTW, as 'Steven Rostedt' mentioned: There is still technically

[PATCH v2 2/3] rtmutex: update rt-mutex

The rtmutex remove a pending owner bit in in rt_mutex::owner, in commit 8161239a8bcc ("rtmutex: Simplify PI algorithm and make highest prio task get lock") But the document was changed accordingly. Updating it to a meaningful state. BTW, as 'Steven Rostedt' mentioned: There is still technically

[PATCH 3/3] rtmutex: remove unnecessary adjust prio

We don't need to adjust prio before new pi_waiter adding. The prio only need update after pi_waiter change or task priority change. Signed-off-by: Alex Shi Cc: Steven Rostedt Cc: Sebastian Siewior Cc: Mathieu Poirier

[PATCH 3/3] rtmutex: remove unnecessary adjust prio

We don't need to adjust prio before new pi_waiter adding. The prio only need update after pi_waiter change or task priority change. Signed-off-by: Alex Shi Cc: Steven Rostedt Cc: Sebastian Siewior Cc: Mathieu Poirier Cc: Juri Lelli Cc: Thomas Gleixner To: linux-kernel@vger.kernel.org To:

[PATCH v3 1/3] rtmutex: update rt-mutex-design

The rt-mutex-design documents didn't gotten meaningful update from its first version. Even after owner's pending bit was removed in commit 8161239a8bcc ("rtmutex: Simplify PI algorithm and make highest prio task get lock") and priority list 'plist' changed to rbtree. And Peter Zijlstra did some

[PATCH v3 1/3] rtmutex: update rt-mutex-design

The rt-mutex-design documents didn't gotten meaningful update from its first version. Even after owner's pending bit was removed in commit 8161239a8bcc ("rtmutex: Simplify PI algorithm and make highest prio task get lock") and priority list 'plist' changed to rbtree. And Peter Zijlstra did some

Re: [PATCH] Staging: bcm2835-audio: bcm2835-ctl.c: Fixed a comment coding style issue.

On Thu, May 25, 2017 at 4:58 AM, Tobin C. Harding wrote: > On Wed, May 24, 2017 at 08:03:14PM +0530, srishti sharma wrote: > > This driver is not in Greg KH's staging tree. You may like to work off > of that tree when doing staging patches. > >

Re: [PATCH] Staging: bcm2835-audio: bcm2835-ctl.c: Fixed a comment coding style issue.

On Thu, May 25, 2017 at 4:58 AM, Tobin C. Harding wrote: > On Wed, May 24, 2017 at 08:03:14PM +0530, srishti sharma wrote: > > This driver is not in Greg KH's staging tree. You may like to work off > of that tree when doing staging patches. > >

[PATCH] mtd: nand: check ecc->total sanity in nand_scan_tail

Drivers are supposed to set correct ecc->{size,strength,bytes} before calling nand_scan_tail(), but it does not complain about ecc->total bigger than oobsize. In this case, chip->scan_bbt() crashes due to memory corruption, but it is hard to debug. It would be kind to fail it earlier with a

[PATCH] mtd: nand: check ecc->total sanity in nand_scan_tail

Drivers are supposed to set correct ecc->{size,strength,bytes} before calling nand_scan_tail(), but it does not complain about ecc->total bigger than oobsize. In this case, chip->scan_bbt() crashes due to memory corruption, but it is hard to debug. It would be kind to fail it earlier with a

[PATCH v3 1/2] phy: add PCIe PHY driver for Mediatek SoCs

This patch adds a generic PCIe PHY driver for Mediatek SoCs. Signed-off-by: Ryder Lee --- drivers/phy/Kconfig | 8 ++ drivers/phy/Makefile| 1 + drivers/phy/phy-mediatek-pcie.c | 290 3 files changed,

[PATCH v3 1/2] phy: add PCIe PHY driver for Mediatek SoCs

This patch adds a generic PCIe PHY driver for Mediatek SoCs. Signed-off-by: Ryder Lee --- drivers/phy/Kconfig | 8 ++ drivers/phy/Makefile| 1 + drivers/phy/phy-mediatek-pcie.c | 290 3 files changed, 299 insertions(+) create

[PATCH v3 0/2] Add PCIe phy driver for some Mediatek SoCs

Hi, This patch series add PCIe phy driver and related dt-binding file for Mediatek SoCs. The PICe host driver has been applied to pci/host-mediatek for v4.13. Changes since v3: - rename both the driver and the binding document to make it more generic so that we could reuse the driver if

[PATCH v3 0/2] Add PCIe phy driver for some Mediatek SoCs

Hi, This patch series add PCIe phy driver and related dt-binding file for Mediatek SoCs. The PICe host driver has been applied to pci/host-mediatek for v4.13. Changes since v3: - rename both the driver and the binding document to make it more generic so that we could reuse the driver if

[PATCH v3 2/2] dt-bindings: phy: Add documentation for Mediatek PCIe PHY

Add dt-binding information for Mediatek PCIe PHY Signed-off-by: Ryder Lee Acked-by: Rob Herring --- .../devicetree/bindings/phy/phy-mediatek-pcie.txt | 64 ++ 1 file changed, 64 insertions(+) create mode 100644

[PATCH v3 2/2] dt-bindings: phy: Add documentation for Mediatek PCIe PHY

Add dt-binding information for Mediatek PCIe PHY Signed-off-by: Ryder Lee Acked-by: Rob Herring --- .../devicetree/bindings/phy/phy-mediatek-pcie.txt | 64 ++ 1 file changed, 64 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/phy-mediatek-pcie.txt

[RFC PATCH 3/5] ARM: imx: add gpiod_lookup_table for spi chip-selects

This is a preparatory step which will allow the conversion of spi-imx.c to gpiod. Signed-off-by: Chris Packham --- arch/arm/mach-imx/mach-mx27_3ds.c | 21 + arch/arm/mach-imx/mach-pca100.c | 13 + 2 files changed, 34

[RFC PATCH 0/5] spi: moving to struct gpio_desc

This is my attempt to move spi over to using struct gpio_desc. I've stopped at converting struct spi_master to gather some feedback. ep93xx wasn't as hard as I'd expected so I'm pretty happy with those changes. imx on the other hand has an annoying habit of conflating the GPIO and native

[RFC PATCH 3/5] ARM: imx: add gpiod_lookup_table for spi chip-selects

This is a preparatory step which will allow the conversion of spi-imx.c to gpiod. Signed-off-by: Chris Packham --- arch/arm/mach-imx/mach-mx27_3ds.c | 21 + arch/arm/mach-imx/mach-pca100.c | 13 + 2 files changed, 34 insertions(+) diff --git

[RFC PATCH 0/5] spi: moving to struct gpio_desc

This is my attempt to move spi over to using struct gpio_desc. I've stopped at converting struct spi_master to gather some feedback. ep93xx wasn't as hard as I'd expected so I'm pretty happy with those changes. imx on the other hand has an annoying habit of conflating the GPIO and native

[RFC PATCH 5/5] ARM: ep93xx: remove chipselect from ep93xx_spi_info

Now that the driver has been updated to use gpiod there is no need to have platform data to define the SPI chipselects. We still need to define the number of chipselects used. Signed-off-by: Chris Packham --- arch/arm/mach-ep93xx/edb93xx.c | 7

[RFC PATCH 5/5] ARM: ep93xx: remove chipselect from ep93xx_spi_info

Now that the driver has been updated to use gpiod there is no need to have platform data to define the SPI chipselects. We still need to define the number of chipselects used. Signed-off-by: Chris Packham --- arch/arm/mach-ep93xx/edb93xx.c | 7 +-- arch/arm/mach-ep93xx/simone.c

[RFC PATCH 4/5] spi: core: convert spi_master to use gpio_desc

Instead of numeric gpios make struct spi_master hold an array of struct gpio_desc. For now struct spi_device still maintains a numeric gpio which will be updated in a subsequent change. Signed-off-by: Chris Packham --- drivers/spi/spi-ep93xx.c | 18

[RFC PATCH 1/5] spi: use gpio_desc instead of numeric gpio

By using a gpio_desc and gpiod_set_value() instead of a numeric gpio and gpio_set_value() the gpio flags are taken into account. This is useful when using a gpio chip-select to supplement a controllers native chip-select. Signed-off-by: Chris Packham --- (I've

[RFC PATCH 4/5] spi: core: convert spi_master to use gpio_desc

Instead of numeric gpios make struct spi_master hold an array of struct gpio_desc. For now struct spi_device still maintains a numeric gpio which will be updated in a subsequent change. Signed-off-by: Chris Packham --- drivers/spi/spi-ep93xx.c | 18 -- drivers/spi/spi-imx.c|

[RFC PATCH 1/5] spi: use gpio_desc instead of numeric gpio

By using a gpio_desc and gpiod_set_value() instead of a numeric gpio and gpio_set_value() the gpio flags are taken into account. This is useful when using a gpio chip-select to supplement a controllers native chip-select. Signed-off-by: Chris Packham --- (I've included this in this series for

[RFC PATCH 2/5] ARM: ep93xx: add gpiod_lookup_table for spi chip-selects

This is a preparatory step which will allow the conversion of spi-ep93xx.c to gpiod. Signed-off-by: Chris Packham --- arch/arm/mach-ep93xx/edb93xx.c | 12 arch/arm/mach-ep93xx/simone.c| 11 +++

[RFC PATCH 2/5] ARM: ep93xx: add gpiod_lookup_table for spi chip-selects

This is a preparatory step which will allow the conversion of spi-ep93xx.c to gpiod. Signed-off-by: Chris Packham --- arch/arm/mach-ep93xx/edb93xx.c | 12 arch/arm/mach-ep93xx/simone.c| 11 +++ arch/arm/mach-ep93xx/vision_ep9307.c | 15 +++ 3 files

Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback

On Wed, May 24, 2017 at 3:38 PM, Luis R. Rodriguez wrote: > On Wed, May 24, 2017 at 3:00 PM, Andy Lutomirski wrote: >> On Wed, May 24, 2017 at 2:40 PM, Luis R. Rodriguez wrote: >>> From: Martin Fuzzey >>> >>> Commit

Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback

On Wed, May 24, 2017 at 3:38 PM, Luis R. Rodriguez wrote: > On Wed, May 24, 2017 at 3:00 PM, Andy Lutomirski wrote: >> On Wed, May 24, 2017 at 2:40 PM, Luis R. Rodriguez wrote: >>> From: Martin Fuzzey >>> >>> Commit 0cb64249ca500 ("firmware_loader: abort request if wait_for_completion >>> is

Re: [PATCH] sparc64: Add 16GB hugepage support

On 5/24/17 8:45 PM, David Miller wrote: > From: Paul Gortmaker > Date: Wed, 24 May 2017 23:34:42 -0400 > >> [[PATCH] sparc64: Add 16GB hugepage support] On 24/05/2017 (Wed 17:29) Nitin >> Gupta wrote: >> >>> Orabug: 25362942 >>> >>> Signed-off-by: Nitin Gupta

Re: [PATCH] sparc64: Add 16GB hugepage support

On 5/24/17 8:45 PM, David Miller wrote: > From: Paul Gortmaker > Date: Wed, 24 May 2017 23:34:42 -0400 > >> [[PATCH] sparc64: Add 16GB hugepage support] On 24/05/2017 (Wed 17:29) Nitin >> Gupta wrote: >> >>> Orabug: 25362942 >>> >>> Signed-off-by: Nitin Gupta >> >> If this wasn't an accidental

[PATCH v4 2/9] dt-bindings: arm: mediatek: add bindings for mediatek MT7623a SoC Platform

From: Sean Wang This adds DT binding documentation for Mediatek MT7623a Signed-off-by: Sean Wang Acked-by: Rob Herring --- Documentation/devicetree/bindings/arm/mediatek.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v4 2/9] dt-bindings: arm: mediatek: add bindings for mediatek MT7623a SoC Platform

From: Sean Wang This adds DT binding documentation for Mediatek MT7623a Signed-off-by: Sean Wang Acked-by: Rob Herring --- Documentation/devicetree/bindings/arm/mediatek.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt

[PATCH v4 0/9] arm: dts: extend mt7623 support

From: Sean Wang Changes since v3: - explain in the commit message why this binding is changed - patches for dt-binding is reordered at the beginning of patch list - be concise wigh using SPDX-License-Identifier in new dts file Changes since v2: - exclude those patch are

[PATCH v4 1/9] dt-bindings: arm: mediatek: update for MT7623n SoC and relevant boards

From: Sean Wang Because there are two versions of MT7623 SoC that is MT7623a and MT7623n respectively. So update the part of MT7623n bindings to allow that people tend to differentiate which MT7623 SoC the boards applies. And "mediatek,mt7623-evb" can be safely changed

[PATCH v4 1/9] dt-bindings: arm: mediatek: update for MT7623n SoC and relevant boards

From: Sean Wang Because there are two versions of MT7623 SoC that is MT7623a and MT7623n respectively. So update the part of MT7623n bindings to allow that people tend to differentiate which MT7623 SoC the boards applies. And "mediatek,mt7623-evb" can be safely changed to

[PATCH v4 0/9] arm: dts: extend mt7623 support

From: Sean Wang Changes since v3: - explain in the commit message why this binding is changed - patches for dt-binding is reordered at the beginning of patch list - be concise wigh using SPDX-License-Identifier in new dts file Changes since v2: - exclude those patch are already queued into

[PATCH] spi: st-ssc4: whitespace cleanup

Remove stray single spaces after a leading hard-tab. Signed-off-by: Chris Packham --- drivers/spi/spi-st-ssc4.c | 38 +++--- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/drivers/spi/spi-st-ssc4.c

[PATCH] spi: st-ssc4: whitespace cleanup

Remove stray single spaces after a leading hard-tab. Signed-off-by: Chris Packham --- drivers/spi/spi-st-ssc4.c | 38 +++--- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/drivers/spi/spi-st-ssc4.c b/drivers/spi/spi-st-ssc4.c index

[PATCH v4 9/9] arm: dts: mt7623: add dts file for Bananapi R2 (BPI-R2) board

From: Sean Wang Add support for the Bananapi R2 (BPI-R2) development board from BIPAI KEJI. Detailed hardware information for BPI-R2 which could be found on http://www.banana-pi.org/r2.html The patch currently only adds Mediatek GMAC, MT7530 Switch, the crypto engine,

[PATCH v4 7/9] arm: dts: mt7623: enable the usb device on the mt7623n rfb

From: John Crispin All versions of the mt7623n RFB have an USB port so enable the device. There is a gpio that gets used to power up the port supply. Add support for this gpio using the fixed-regulator driver. Signed-off-by: John Crispin Signed-off-by: Sean

[PATCH v4 9/9] arm: dts: mt7623: add dts file for Bananapi R2 (BPI-R2) board

From: Sean Wang Add support for the Bananapi R2 (BPI-R2) development board from BIPAI KEJI. Detailed hardware information for BPI-R2 which could be found on http://www.banana-pi.org/r2.html The patch currently only adds Mediatek GMAC, MT7530 Switch, the crypto engine, USB, IR, I2S, I2C, UART,

[PATCH v4 7/9] arm: dts: mt7623: enable the usb device on the mt7623n rfb

From: John Crispin All versions of the mt7623n RFB have an USB port so enable the device. There is a gpio that gets used to power up the port supply. Add support for this gpio using the fixed-regulator driver. Signed-off-by: John Crispin Signed-off-by: Sean Wang ---

[PATCH v4 5/9] ARM: mediatek: add MT7623a smp bringup code

From: Sean Wang Add support for booting secondary CPUs on MT7623a. Signed-off-by: Sean Wang --- arch/arm/mach-mediatek/mediatek.c | 2 ++ arch/arm/mach-mediatek/platsmp.c | 1 + 2 files changed, 3 insertions(+) diff --git

[PATCH v4 8/9] arm: dts: mt7623: enable the nand device on the mt7623n nand rfb

From: John Crispin Enable the nand device and setup pinmux on the mt7632m rfb with nand support. Signed-off-by: John Crispin Signed-off-by: Sean Wang --- arch/arm/boot/dts/mt7623n-rfb-nand.dts | 88 ++

[PATCH v4 6/9] arm: dts: mt7623: cleanup the mt7623n rfb uart nodes

From: John Crispin This patch does a cleanup of the uart nodes in the dts file of the RFB. It adds aliases, enables 2 more uarts and explicitly sets the uart mode of the console. Signed-off-by: John Crispin Signed-off-by: Sean Wang

[PATCH v4 5/9] ARM: mediatek: add MT7623a smp bringup code

From: Sean Wang Add support for booting secondary CPUs on MT7623a. Signed-off-by: Sean Wang --- arch/arm/mach-mediatek/mediatek.c | 2 ++ arch/arm/mach-mediatek/platsmp.c | 1 + 2 files changed, 3 insertions(+) diff --git a/arch/arm/mach-mediatek/mediatek.c

[PATCH v4 8/9] arm: dts: mt7623: enable the nand device on the mt7623n nand rfb

From: John Crispin Enable the nand device and setup pinmux on the mt7632m rfb with nand support. Signed-off-by: John Crispin Signed-off-by: Sean Wang --- arch/arm/boot/dts/mt7623n-rfb-nand.dts | 88 ++ 1 file changed, 88 insertions(+) diff --git

[PATCH v4 6/9] arm: dts: mt7623: cleanup the mt7623n rfb uart nodes

From: John Crispin This patch does a cleanup of the uart nodes in the dts file of the RFB. It adds aliases, enables 2 more uarts and explicitly sets the uart mode of the console. Signed-off-by: John Crispin Signed-off-by: Sean Wang --- arch/arm/boot/dts/mt7623n-rfb.dtsi | 16 +++-

Re: [linux-sunxi] [PATCH v3 3/9] ASoC: sun8i-codec-analog: add support for V3s SoC

On Wed, May 24, 2017 at 6:06 PM, Icenowy Zheng wrote: > From: Icenowy Zheng > > The V3s SoC features an analog codec with headphone support but without > mic2 and linein. > > Add support for it. > > Signed-off-by: Icenowy Zheng Reviewed-by:

[PATCH v4 3/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file

From: John Crispin MediaTek produces various PMICs. Which one is used depends on the actual circuit design. Instead of adding the correct PMIC node to every dts file we instead add a new intermediate dtsi file which adds the PMIC node. Additionally we also add the phandles for

[PATCH v4 4/9] arm: dts: mt7623: rename mt7623-evb.dts to arch/arm/boot/dts/mt7623n-rfb.dtsi

From: Sean Wang There are 2 versions of the MT7623 SoC, the one is MT7623n and the other is MT7623a. MT7623n is almost identical to MT7623a but has some additional multimedia features. The reference boards are available as NAND or MMC and might have a different ethernet

Re: [linux-sunxi] [PATCH v3 3/9] ASoC: sun8i-codec-analog: add support for V3s SoC

On Wed, May 24, 2017 at 6:06 PM, Icenowy Zheng wrote: > From: Icenowy Zheng > > The V3s SoC features an analog codec with headphone support but without > mic2 and linein. > > Add support for it. > > Signed-off-by: Icenowy Zheng Reviewed-by: Chen-Yu Tsai Mark, please hold off on applying this

[PATCH v4 3/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file

From: John Crispin MediaTek produces various PMICs. Which one is used depends on the actual circuit design. Instead of adding the correct PMIC node to every dts file we instead add a new intermediate dtsi file which adds the PMIC node. Additionally we also add the phandles for the regulators to

[PATCH v4 4/9] arm: dts: mt7623: rename mt7623-evb.dts to arch/arm/boot/dts/mt7623n-rfb.dtsi

From: Sean Wang There are 2 versions of the MT7623 SoC, the one is MT7623n and the other is MT7623a. MT7623n is almost identical to MT7623a but has some additional multimedia features. The reference boards are available as NAND or MMC and might have a different ethernet setup. In order to

  1   2   3   4   5   6   7   8   9   10   >