On Fri, Oct 10, 2014 at 08:48:53AM -0700, bruce bushby wrote: > So I'm guessing it's those sort of addresses that should now come > from DTS variables? ...are their specific "structures" that pass > "DTS variables" to a driver?
For the generic resources (clocks, addresses, interrupts, dma channels, etc.), there is generic structures that are _not_ specific to the DT. > The most excellent: > http://free-electrons.com/pub/conferences/2013/elce/petazzoni-device-tree-dummies/petazzoni-device-tree-dummies.pdf > > Mentions the following on page 15: > > described by the clocks property > I s->clk = clk_get(&pdev->dev, NULL); > > described by the interrupts property > I s->irq = platform_get_irq(pdev, 0); > > Where are these functions defined? http://lxr.free-electrons.com/ident?i=clk_get http://lxr.free-electrons.com/ident?i=platform_get_irq > Assuming there are some magic includes that all DTS enabled drivers > must use? No. > Are there other functions to get spi or i2c addresses? The SPI and I2C addresses will be filled and passed to the drivers through the spi_master / i2c_client structures. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
signature.asc
Description: Digital signature
