On Fri, Sep 25, 2020 at 04:43:12PM -0700, Trent Piepho wrote:
> When dynamically assigning device names, an aiodev's name will be
> "aiodev" and an index, not part of the name string itself, will be
> allocated dynamically. These are combined to register a device with a
> name like "aiodev0" or "aiodev1".
>
> The shell environment variables use the device name, so one might use
> "${aiodev0.in_value0_mV}" and "${aiodev1.in_value0_mV}".
>
> However, the channel names that are used with aiochannel_get_by_name()
> just use the aiodev's name and channel name. So channel 0 of the 1st
> aiodev would be "aiodev.in_value0_mV" and the 2nd aiodev would use the
> same name.
>
> Change the channel naming to use the device instance name, e.g.
> "aiodev0", rather than the aiodev's base name. This makes the names
> used aiochannel_get_by_name() match the environment variable names and
> also avoids duplicate names with more than one dynamically allocated
> aiodev.
>
> Rename aiochannel_get_by_name() to aiochannel_by_name() so that any out
> of tree boards that use it will fail to compile, since they now need to
> pass in a different name.
>
> Signed-off-by: Trent Piepho <trent.piepho@xxxxxxxxxxx>
> ---
> Changes in v2:
> * Rename aiochannel_get_by_name()
Applied all, thanks
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
