Hi Rob
> > node {
> > => ports@0 {
> > port@0 { ... };
> > port@1 { ... };
> > ...
> > };
> > => ports@1 {
> > ...
> > };
> > };
>
> There is no schema that supports this structure. The closest thing we
> have is in-ports and out-ports in Coresight bindings.
>
> In any case, it should be a separate patch, not buried in here.
Oops, my driver is using multi ports already.
it is handling like below
+-- Board -------------+
|+--------+ +------+|
||SoC (A)|<--->|Codec1|| Sound Card0
|| | +------+|
|| (B)|<-+ |
|+--------+ | |
+------------|----------+
+-- Expansion board ----+
| | +------+|
| +->|Codec2|| Sound Card1
| +------+|
+-----------------------+
Here (A) is handled by ports0, and (B) is handled by ports1,
and each ports has many port nodes.
Thank you for your help !!
Best regards
---
Kuninori Morimoto
[Index of Archives]
[Pulseaudio]
[Linux Audio Users]
[ALSA Devel]
[Fedora Desktop]
[Fedora SELinux]
[Big List of Linux Books]
[Yosemite News]
[KDE Users]