Re: [PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure

2012-07-25 Thread Daniel Mack
On 25.07.2012 22:12, Mark Brown wrote: > On Wed, Jul 25, 2012 at 10:00:18PM +0200, Daniel Mack wrote: > >> I don't know what's wrong here, but clearly, the message in my inbox has > >> To: spi-devel-general@lists.sourceforge.net >> Cc: grant.lik...@secretlab.ca, >> rob.herr...@calxeda.com, >

Re: [PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure

2012-07-25 Thread Mark Brown
On Wed, Jul 25, 2012 at 10:00:18PM +0200, Daniel Mack wrote: > I don't know what's wrong here, but clearly, the message in my inbox has > To: spi-devel-general@lists.sourceforge.net > Cc: grant.lik...@secretlab.ca, > rob.herr...@calxeda.com, > devicetree-disc...@lists.ozlabs.org, >

Re: [PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure

2012-07-25 Thread Daniel Mack
On 25.07.2012 21:52, Mark Brown wrote: > On Wed, Jul 25, 2012 at 09:38:58PM +0200, Daniel Mack wrote: >> On 25.07.2012 21:33, Mark Brown wrote: > >>> Always CC maintainers on things... you've not CCed Grant or Linus W, >>> and for now I'm handling SPI patches (though I'm not in MAINTAINERS so >>>

Re: [PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure

2012-07-25 Thread Mark Brown
On Wed, Jul 25, 2012 at 09:38:58PM +0200, Daniel Mack wrote: > On 25.07.2012 21:33, Mark Brown wrote: > > Always CC maintainers on things... you've not CCed Grant or Linus W, > > and for now I'm handling SPI patches (though I'm not in MAINTAINERS so > > missing me is less surprising). > I *did*

Re: [PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure

2012-07-25 Thread Daniel Mack
On 25.07.2012 21:33, Mark Brown wrote: > On Wed, Jul 25, 2012 at 01:44:11PM +0200, Daniel Mack wrote: >> The spi-gpio driver currently assumes the chipselect gpio number is >> stored in ->controller_data of the device's static board information. > > Always CC maintainers on things... you've not C

Re: [PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure

2012-07-25 Thread Mark Brown
On Wed, Jul 25, 2012 at 01:44:11PM +0200, Daniel Mack wrote: > The spi-gpio driver currently assumes the chipselect gpio number is > stored in ->controller_data of the device's static board information. Always CC maintainers on things... you've not CCed Grant or Linus W, and for now I'm handling

Re: [PATCH 2/2] SPI: spi-gpio: Add DT bindings

2012-07-25 Thread Daniel Mack
On 25.07.2012 14:32, Wolfram Sang wrote: > +Example: + + spi { + compatible = "spi-gpio"; + #address-cells = <0x1>; + ranges; + + gpio-sck = <&gpio 95 0>; + gpio-miso = <&gpio 98 0>; + gpio-mos

Re: [PATCH 2/2] SPI: spi-gpio: Add DT bindings

2012-07-25 Thread Daniel Mack
On 25.07.2012 14:11, Wolfram Sang wrote: > On Wed, Jul 25, 2012 at 01:44:12PM +0200, Daniel Mack wrote: >> This patch adds DT bindings to the spi-gpio driver and some >> documentation about how to use it. >> >> Signed-off-by: Daniel Mack >> --- >> Documentation/devicetree/bindings/spi/spi-gpio.tx

[PATCH 2/2] SPI: spi-gpio: Add DT bindings

2012-07-25 Thread Daniel Mack
This patch adds DT bindings to the spi-gpio driver and some documentation about how to use it. Signed-off-by: Daniel Mack --- Documentation/devicetree/bindings/spi/spi-gpio.txt | 29 ++ drivers/spi/spi-gpio.c | 99 +++- 2 files changed, 125 ins

[PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure

2012-07-25 Thread Daniel Mack
The spi-gpio driver currently assumes the chipselect gpio number is stored in ->controller_data of the device's static board information. In devicetree environments, this information is unavailable and has to be derived from the DT node. This patch moves the gpio storage to the controller's priva

Promo exceptionnelle : 50 pourcent de reduction pour ce week-end

2012-07-25 Thread Accorhotels.com par Duano
Pour voir le message, veuillez utiliser un lecteur de mail compatible HTML Lien miroir : http://m10-fr.com/mc10_m/YT0xMyZiPTE2NzgyJmM9NDgzNjEyJmQ9MjAxMi0wNy0yNSAwOToxMDowMSZlPTEmaD0xNjc4MSZmPTE2NzgyJmc9MTY3ODI= Lien de désinscription : http://m10-fr.com/mc10_unsub/YT0xMyZiPTE2NzgyJmM9NDgzNjEyJm