On Thu, Nov 13, 2014 at 02:39:55PM +0100, Wolfram Sang wrote:
> The current implementation creates muxed i2c-<n> busses as immediate
> children of their i2c-<n> parent bus. In case of multiple muxes on one
> bus, it is impossible to determine which muxed bus comes from which mux.
> 
> It could be argued that the parent device should be changed from the
> parent adapter to the mux device. This has pros and cons. To improve the
> topology, simply add a "muxed_device" symlink pointing to the actual
> muxing device, so we can distinguish muxed busses. Doing it this way, we
> don't break the ABI.
> 
> Signed-off-by: Wolfram Sang <[email protected]>
> Cc: Jean Delvare <[email protected]>
> Cc: Guenter Roeck <[email protected]>
> Cc: Martin Belanger <[email protected]>
> Cc: Rodolfo Giometti <[email protected]>
> Cc: Michael Lawnick <[email protected]>
> Cc: Jeroen De Wachter <[email protected]>
> Cc: Gerlando Falauto <[email protected]>

Applied to for-next, thanks!

Attachment: signature.asc
Description: Digital signature

Reply via email to