Skip to content
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

Despite claim, no properties are defined in the rscv- namespace #198

Closed
jhauser-us opened this issue Sep 28, 2024 · 6 comments
Closed

Despite claim, no properties are defined in the rscv- namespace #198

jhauser-us opened this issue Sep 28, 2024 · 6 comments
Labels
wontfix This will not be worked on

Comments

@jhauser-us
Copy link

Section 6.3, "RVI-specific ACPI Device Properties", says, "This section defines the _DSD device properties in the rscv- namespace." However, the only properties actually mentioned in this section are for UART devices, and if I'm not mistaken, these are not defined in the rscv- namespace. (Right?)

In short, I believe this section says it defines properties in the rscv- namespace but then doesn't do so.

@vlsunil
Copy link
Collaborator

vlsunil commented Oct 11, 2024

You are right. I think this is a place holder for any property to be defined under rscv- namespace. The DSD guide (https://github.com/UEFI/DSD-Guide/blob/main/src/dsd-guide.adoc#appendix-c-known-device-property-prefixes) allows to use vendor ACPI ID as the prefix for the property but vendor needs to manage those properties. For RISC-V, ACPI ID registered is RSCV. Hence, any one in future wants to define and use a new property under rscv- namespace, should register here first. I think that is the idea to have this section.

@andreiw
Copy link
Collaborator

andreiw commented Nov 6, 2024

We had some properties here initially, then - we didn't. Nevertheless, it makes sense to stake a claim to the rscv- namespace now.

@andreiw andreiw added the wontfix This will not be worked on label Nov 6, 2024
@andreiw
Copy link
Collaborator

andreiw commented Nov 6, 2024

Marking this as won't fix given last two comments. If you're okay with that, please close the ticket @jhauser-us.

@jhauser-us
Copy link
Author

The right response is not to leave the document making an obviously false statement. If you want to stake the claim to the rscv- namespace, then change the text to say that.

vlsunil added a commit to vlsunil/riscv-brs that referenced this issue Nov 8, 2024
The RVI-specific ACPI Device Properties section exists as a place holder
to define standard DSD properties in the "rscv-" namespace. While there
are no properties currently defined, it is the place where one can add
new properties approved by appropriate RVI forum. Try to reword to make
the intention clear.

Fixes: riscv-non-isa#198
Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
vlsunil added a commit to vlsunil/riscv-brs that referenced this issue Nov 11, 2024
The RVI-specific ACPI Device Properties section exists as a place holder
to define standard DSD properties in the "rscv-" namespace. While there
are no properties currently defined, it is the place where one can add
new properties approved by appropriate RVI forum. Try to reword to make
the intention clear.

Fixes: riscv-non-isa#198
Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
vlsunil added a commit to vlsunil/riscv-brs that referenced this issue Nov 11, 2024
The RVI-specific ACPI Device Properties section exists as a place holder
to define standard DSD properties in the "rscv-" namespace. While there
are no properties currently defined, it is the place where one can add
new properties approved by appropriate RVI forum. Try to reword to make
the intention clear.

Fixes: riscv-non-isa#198
Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
@jhauser-us
Copy link
Author

It is the consensus of the Architecture Review Committee that Section 6.3, "RVI-specific ACPI Device Properties", needs a non-normative note clarifying that the table of rscv- names is currently empty. And this paragraph:

Request for new property names in the rscv- namespace should be made as a git pull request to below table in this document.

should be made non-normative, preferably moved into the same non-normative note.

In my opinion, it makes more sense for this non-normative note to follow the table, which would require "below table" be changed appropriately. (Note, by the way, that the words above and below are not adjectives, so it's not gramatically correct to say "above table" or "below table".)

@vlsunil
Copy link
Collaborator

vlsunil commented Dec 3, 2024

Thanks @jhauser-us . Let me update as per your suggestion.

@avpatel avpatel reopened this Dec 3, 2024
vlsunil added a commit to vlsunil/riscv-brs that referenced this issue Dec 5, 2024
ARC suggested to move details about git PR to non-normative text below
the table and to mention that currently the table which defines the DSD
properties under riscv- namespace is empty.

Fixes: riscv-non-isa#198
Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
@avpatel avpatel closed this as completed in b1af1aa Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants