Re: [RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Alban
On Mon, 27 Feb 2017 21:42:30 +0100 Boris Brezillon wrote: > +Moritz > > Hi Alban, > > On Mon, 27 Feb 2017 21:28:09 +0100 > Alban wrote: > > > Hi all, > > > > while looking at adding OF support for the ath9k driver I had the problem of > >

Re: [RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Alban
On Mon, 27 Feb 2017 21:42:30 +0100 Boris Brezillon wrote: > +Moritz > > Hi Alban, > > On Mon, 27 Feb 2017 21:28:09 +0100 > Alban wrote: > > > Hi all, > > > > while looking at adding OF support for the ath9k driver I had the problem of > > reading the EEPROM data. On the SoC platforms this

Re: [RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Moritz Fischer
Hi all, On Mon, Feb 27, 2017 at 12:42 PM, Boris Brezillon wrote: > +Moritz > > Hi Alban, > > On Mon, 27 Feb 2017 21:28:09 +0100 > Alban wrote: > >> Hi all, >> >> while looking at adding OF support for the ath9k driver I had the problem of >>

Re: [RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Moritz Fischer
Hi all, On Mon, Feb 27, 2017 at 12:42 PM, Boris Brezillon wrote: > +Moritz > > Hi Alban, > > On Mon, 27 Feb 2017 21:28:09 +0100 > Alban wrote: > >> Hi all, >> >> while looking at adding OF support for the ath9k driver I had the problem of >> reading the EEPROM data. On the SoC platforms this

Re: [RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Boris Brezillon
+Moritz Hi Alban, On Mon, 27 Feb 2017 21:28:09 +0100 Alban wrote: > Hi all, > > while looking at adding OF support for the ath9k driver I had the problem of > reading the EEPROM data. On the SoC platforms this data is stored in an SPI > flash along with a few other things. In

Re: [RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Boris Brezillon
+Moritz Hi Alban, On Mon, 27 Feb 2017 21:28:09 +0100 Alban wrote: > Hi all, > > while looking at adding OF support for the ath9k driver I had the problem of > reading the EEPROM data. On the SoC platforms this data is stored in an SPI > flash along with a few other things. In OpenWRT/LEDE

Re: [RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Marek Vasut
On 02/27/2017 09:28 PM, Alban wrote: > Hi all, > > while looking at adding OF support for the ath9k driver I had the problem of > reading the EEPROM data. On the SoC platforms this data is stored in an SPI > flash along with a few other things. In OpenWRT/LEDE this data is read from > the board

Re: [RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Marek Vasut
On 02/27/2017 09:28 PM, Alban wrote: > Hi all, > > while looking at adding OF support for the ath9k driver I had the problem of > reading the EEPROM data. On the SoC platforms this data is stored in an SPI > flash along with a few other things. In OpenWRT/LEDE this data is read from > the board

[RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Alban
Hi all, while looking at adding OF support for the ath9k driver I had the problem of reading the EEPROM data. On the SoC platforms this data is stored in an SPI flash along with a few other things. In OpenWRT/LEDE this data is read from the board init code using the fact that the flash is

[RFC 0/3] drivers: Add an API to read device specific config data

2017-02-27 Thread Alban
Hi all, while looking at adding OF support for the ath9k driver I had the problem of reading the EEPROM data. On the SoC platforms this data is stored in an SPI flash along with a few other things. In OpenWRT/LEDE this data is read from the board init code using the fact that the flash is