-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
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
Dependency: ACPI - Define AML device for SPCR type 0x12 devices #24
Comments
'DSD DT' - what do you mean by this? device specific data and have that under a specific ACPIxxxx device name? |
He's probably referring to the practice of embedding DT properties into the _DSD entries, i.e., https://docs.kernel.org/6.2/firmware-guide/acpi/dsd/graph.html |
Yes, that was my question confirming if DSD DT meant that. I assumed so, but I wanted to be sure. |
Yes, Paul is correct. |
This would be nice to have but ideally is code-first and fueled by someone who needs it |
reg-offset is not necessary (there's nothing matching that in SPCR) |
riscv-non-isa#24 Signed-off-by: Andrei Warkentin <[email protected]>
riscv-non-isa#24 Signed-off-by: Andrei Warkentin <[email protected]>
riscv-non-isa#24 Signed-off-by: Andrei Warkentin <[email protected]>
Also need to add the rscv- Known Device Property Prefixex |
#24 Signed-off-by: Andrei Warkentin <[email protected]>
Type 0x12 can describe NS16550-like UARTs that cannot be described by PNP0501 - the e.g. register stride, clock frequency. And there are other "tunables" which may be interesting to the OS driver. This should have it's own ACPIxxxx _CID.
Can model this on https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/serial/8250.yaml.
These seem like a good set. Should these use DSD DT?
The text was updated successfully, but these errors were encountered: