On 7/5/21 9:45 AM, Xueming Li wrote: > Auxiliary bus [1] provides a way to split function into child-devices > representing sub-domains of functionality. Each auxiliary device > represents a part of its parent functionality. > > Auxiliary device is identified by unique device name, sysfs path: > /sys/bus/auxiliary/devices/<name> > > Devargs legacy syntax of auxiliary device: > -a auxiliary:<name>[,args...] > Devargs generic syntax of auxiliary device: > -a bus=auxiliary,name=<name>/class=<class>/driver=<driver>[,args...] > > [1] kernel auxiliary bus document: > https://www.kernel.org/doc/html/latest/driver-api/auxiliary_bus.html > > Signed-off-by: Xueming Li <xuemi...@nvidia.com> > Cc: Wang Haiyue <haiyue.w...@intel.com> > Cc: Thomas Monjalon <tho...@monjalon.net> > Cc: Kinsella Ray <m...@ashroe.eu> > Acked-by: Andrew Rybchenko <andrew.rybche...@oktetlabs.ru>
I still don't understand if we really need to make the API a part of stable API/ABI in the future. Can it be internal?
