Messages in this thread |  | | | From | Grant Likely <> | | Subject | Re: Device tree conversion of spi device vs. controller_data | | Date | Thu, 12 Apr 2012 21:29:44 -0600 |
| |
On Sun, 08 Apr 2012 12:24:50 +0200, Roland Stigge <stigge@antcom.de> wrote: > Hi, > > upon DT conversion of LPC32xx, I came across the at25 spi eeprom which > needs .controller_data in struct spi_board_info for slave registration > via spi_register_board_info() (non-DT-case). > > In the DT case, we need to eliminate this explicit registering call. > Therefore, I need to somehow replace the .controller_data passing in the > DT case to pass this data to the spi core. But I can't find such a > mechanism (v3.4-rc2). Is there already a concept or API that I > overlooked (please just point me to it) or what can I do to solve this? > (Looks like a general issue for spi slave registration via DT).
Can you point me at specific code?
.controller_data is owned by the spi_master driver. The eeprom driver shouldn't be accessing it directly at all; but I'll need to look at specific code to really understand what is going on.
g.
-- Grant Likely, B.Sc, P.Eng. Secret Lab Technologies,Ltd.
|  |