Is there RISC-V privilege specification version detection SBI call?

Hi @avpatel
In my understanding, we use system register to check the privilege specification version.

        /* Detect if hart supports Priv v1.10 */
        val = csr_read_allowed(CSR_MCOUNTEREN, (unsigned long)&trap);
        if (!trap.cause)
                hfeatures->priv_version = SBI_HART_PRIV_VER_1_10;

        /* Detect if hart supports Priv v1.11 */
        val = csr_read_allowed(CSR_MCOUNTINHIBIT, (unsigned long)&trap);
        if (!trap.cause &&
            (hfeatures->priv_version >= SBI_HART_PRIV_VER_1_10))
                hfeatures->priv_version = SBI_HART_PRIV_VER_1_11;

        /* Detect if hart supports Priv v1.12 */
        csr_read_allowed(CSR_MENVCFG, (unsigned long)&trap);
        if (!trap.cause &&
            (hfeatures->priv_version >= SBI_HART_PRIV_VER_1_11))
                hfeatures->priv_version = SBI_HART_PRIV_VER_1_12;

But for riscv-state-enable feature, If we want to check in S-mode if it supports it, we haven't any function for this.

so maybe we need to add a new SBI call for privilege specification version detection?

Start with the shown csr_read_allowed privilege-version detection and the linked riscv-state-enable requirement. Review how OpenSBI exposes SBI calls and whether S-mode can determine support from the existing CSR checks. Done means a decided interface or documented conclusion about whether a new privilege-version detection call is needed.