Linux-RISC-V Archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: Samuel Holland <samuel.holland@sifive.com>,
	linux-riscv@lists.infradead.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] cache: sifive_ccache: Auxiliary device support
Date: Wed, 24 Apr 2024 22:20:00 +0100	[thread overview]
Message-ID: <20240424-recolor-deviation-29a5dd4e9499@spud> (raw)
In-Reply-To: <d738dfc0-66af-4dad-bd60-a68c900bf807@ghiti.fr>


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

On Wed, Apr 24, 2024 at 10:19:18PM +0200, Alexandre Ghiti wrote:
> Hi Samuel,
> 
> On 11/04/2024 01:22, Samuel Holland wrote:
> > As of commit c90847bcbfb6 ("cache: sifive_ccache: Partially convert to a
> > platform driver"), the cache subsystem binds a platform driver to the
> > Composable Cache's DT node. This prevents the perf subsystem from doing
> > the same for the new PMU driver[1]. To allow using both drivers at the
> > same time without conflicts or module linkage dependencies, attach the
> > PMU driver to the auxiliary device bus. While at it, prepare to use the
> > auxiliary device bus for the EDAC driver as well, which significantly
> > simplifies that driver. The actual EDAC driver conversion has to wait
> > another development cycle to avoid dependencies between git trees.
> > 
> > [1]: https://lore.kernel.org/linux-riscv/20240216000837.1868917-3-samuel.holland@sifive.com/
> > 
> > 
> > Samuel Holland (4):
> >    cache: sifive_ccache: Silence unused variable warning
> >    cache: sifive_ccache: Use of_iomap() helper
> >    cache: sifive_ccache: Export base address for child drivers
> >    cache: sifive_ccache: Add EDAC and PMU as auxiliary devices
> > 
> >   drivers/cache/Kconfig              |  1 +
> >   drivers/cache/sifive_ccache.c      | 94 +++++++++++++++++++++---------
> >   include/soc/sifive/sifive_ccache.h |  8 +++
> >   3 files changed, 74 insertions(+), 29 deletions(-)
> > 
> 
> I took a quick look and I'm not sure if the whole patchset is a fix for 6.9
> or if only patch 1 is?

Only the first patch is IMO, but it is a fix for a patch I applied so
it'll go this week via the soc tree with those auto-update fixes.

[-- 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

      reply	other threads:[~2024-04-24 21:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 23:22 [PATCH 0/4] cache: sifive_ccache: Auxiliary device support Samuel Holland
2024-04-10 23:22 ` [PATCH 1/4] cache: sifive_ccache: Silence unused variable warning Samuel Holland
2024-04-10 23:22 ` [PATCH 2/4] cache: sifive_ccache: Use of_iomap() helper Samuel Holland
2024-04-10 23:22 ` [PATCH 3/4] cache: sifive_ccache: Export base address for child drivers Samuel Holland
2024-04-10 23:22 ` [PATCH 4/4] cache: sifive_ccache: Add EDAC and PMU as auxiliary devices Samuel Holland
2024-04-12 12:51 ` [PATCH 0/4] cache: sifive_ccache: Auxiliary device support Conor Dooley
2024-04-24 20:19 ` Alexandre Ghiti
2024-04-24 21:20   ` Conor Dooley [this message]

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=20240424-recolor-deviation-29a5dd4e9499@spud \
    --to=conor@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).