We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reg
As of 4fc81d4, the spec seems to leave the semantics here undefined:
/ { bus { compatible = "indirect-bus"; clock { #clock-cells = <0>; compatible = "fixed-clock"; clock-frequency = <32768>; }; }; };
If we map in bus, do we always map in clock?
bus
clock
The current semantics for how nodes under an indirect-bus are included or excluded rely on each node's reg property, which doesn't cover this case.
The text was updated successfully, but these errors were encountered:
You have a good point, we should clarify this. I think if bus is mapped, then also clock is mapped.
Sorry, something went wrong.
@sstabellini I thought about this more and I have another clarifying question: is this recursive?
For example, if clock has a child node without a reg property, is that also mapped?
Yes, also the child of clock should be mapped
No branches or pull requests
As of 4fc81d4, the spec seems to
leave the semantics here undefined:
If we map in
bus
, do we always map inclock
?The current semantics for how nodes under an indirect-bus are included
or excluded rely on each node's
reg
property, which doesn't coverthis case.
The text was updated successfully, but these errors were encountered: