All of lore.kernel.org
 help / color / mirror / Atom feed
From: Drew Fustini <fustini@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Alexandre Ghiti" <alex@ghiti.fr>,
	"Kornel Dulęba" <mindal@semihalf.com>,
	"Adrien Ricciardi" <aricciardi@baylibre.com>,
	"James Morse" <james.morse@arm.com>,
	"Atish Kumar Patra" <atishp@rivosinc.com>,
	"Atish Patra" <atish.patra@linux.dev>,
	"Vasudevan Srinivasan" <vasu@rivosinc.com>,
	guo.wenjia23@zte.com.cn, liu.qingtao2@zte.com.cn,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] RISC-V: Detect Ssqosid extension and handle srmcfg CSR
Date: Thu, 11 Sep 2025 12:53:32 -0700	[thread overview]
Message-ID: <aMMovMevjriDs/Ac@x1> (raw)
In-Reply-To: <20250911-chaste-rare-fbc3b48a341a@spud>


[-- Attachment #1.1: Type: text/plain, Size: 339 bytes --]

On Thu, Sep 11, 2025 at 05:23:30PM +0100, Conor Dooley wrote:
> Why is there no binding change here? Is it not possible to use the
> extension on DT systems, or is this an oversight?

Thanks for pointing this out. My intention is to support QoS on both DT
and ACPI systems. I will add an entry after sstc in extensions.yaml.

Thanks,
Drew

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Drew Fustini <fustini@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Alexandre Ghiti" <alex@ghiti.fr>,
	"Kornel Dulęba" <mindal@semihalf.com>,
	"Adrien Ricciardi" <aricciardi@baylibre.com>,
	"James Morse" <james.morse@arm.com>,
	"Atish Kumar Patra" <atishp@rivosinc.com>,
	"Atish Patra" <atish.patra@linux.dev>,
	"Vasudevan Srinivasan" <vasu@rivosinc.com>,
	guo.wenjia23@zte.com.cn, liu.qingtao2@zte.com.cn,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] RISC-V: Detect Ssqosid extension and handle srmcfg CSR
Date: Thu, 11 Sep 2025 12:53:32 -0700	[thread overview]
Message-ID: <aMMovMevjriDs/Ac@x1> (raw)
In-Reply-To: <20250911-chaste-rare-fbc3b48a341a@spud>

[-- Attachment #1: Type: text/plain, Size: 339 bytes --]

On Thu, Sep 11, 2025 at 05:23:30PM +0100, Conor Dooley wrote:
> Why is there no binding change here? Is it not possible to use the
> extension on DT systems, or is this an oversight?

Thanks for pointing this out. My intention is to support QoS on both DT
and ACPI systems. I will add an entry after sstc in extensions.yaml.

Thanks,
Drew

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-09-11 19:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  6:15 [PATCH 0/2] RISC-V: Detect Ssqosid extension and handle srmcfg CSR Drew Fustini
2025-09-11  6:15 ` Drew Fustini
2025-09-11  6:15 ` [PATCH 1/2] RISC-V: Detect the Ssqosid extension Drew Fustini
2025-09-11  6:15   ` Drew Fustini
2025-09-11  6:15 ` [PATCH 2/2] RISC-V: Add support for srmcfg CSR from Ssqosid ext Drew Fustini
2025-09-11  6:15   ` Drew Fustini
2025-09-11 16:23 ` [PATCH 0/2] RISC-V: Detect Ssqosid extension and handle srmcfg CSR Conor Dooley
2025-09-11 16:23   ` Conor Dooley
2025-09-11 19:53   ` Drew Fustini [this message]
2025-09-11 19:53     ` Drew Fustini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aMMovMevjriDs/Ac@x1 \
    --to=fustini@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=aricciardi@baylibre.com \
    --cc=atish.patra@linux.dev \
    --cc=atishp@rivosinc.com \
    --cc=conor@kernel.org \
    --cc=guo.wenjia23@zte.com.cn \
    --cc=james.morse@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=liu.qingtao2@zte.com.cn \
    --cc=mindal@semihalf.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=vasu@rivosinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.