public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Atish Patra <Atish.Patra@wdc.com>
Cc: paul.walmsley@sifive.com, linux-riscv@lists.infradead.org,
	palmer@dabbelt.com, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, jason@lakedaemon.net
Subject: Re: [v2 PATCH] irqchip/sifive-plic: Add support for multiple PLICs
Date: Fri, 28 Feb 2020 19:55:52 +0000	[thread overview]
Message-ID: <4211bc32ef9a2de376f96d9e4d6c05df@kernel.org> (raw)
In-Reply-To: <39c1cd2c80d67b8b39fe6e2f867e65fd2d42f6d6.camel@wdc.com>

On 2020-02-28 19:03, Atish Patra wrote:
> On Fri, 2020-02-28 at 18:53 +0000, Marc Zyngier wrote:
>> On 2020-02-21 23:22, Atish Patra wrote:
>> > Current, PLIC driver can support only 1 PLIC on the board. However,
>> > there can be multiple PLICs present on a two socket systems in
>> > RISC-V.
>> >
>> > Modify the driver so that each PLIC handler can have a information
>> > about individual PLIC registers and an irqdomain associated with
>> > it.
>> >
>> > Tested on two socket RISC-V system based on VCU118 FPGA connected
>> > via
>> > OmniXtend protocol.
>> >
>> > Signed-off-by: Atish Patra <atish.patra@wdc.com>
>> > ---
>> > This patch is rebased on top of 5.6-rc2 and following plic fix from
>> > hotplug series.
>> >
>> > https://lkml.org/lkml/2020/2/20/1220
>> 
>> How do you want this to be merged? I haven't really followed the
>> hotplug
>> series, but given that this is a pretty simple patch, I'd rather
>> have
>> things
>> based the other way around so that it can be merged independently.
>> 
> I am fine with that or
> 
> I can remove the PLIC patch from the hotplug series and include this
> series as that patch is not really dependant on hotplug code.
> 
> https://patchwork.kernel.org/patch/11407379/
> 
> Let me know what do you prefer.

I'd rather have an independent PLIC series that I can take into 5.7
independently of the rest of the hotplug series. This will make things
simpler for everyone.

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

      reply	other threads:[~2020-02-28 19:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 23:22 [v2 PATCH] irqchip/sifive-plic: Add support for multiple PLICs Atish Patra
2020-02-28  4:06 ` Anup Patel
2020-02-28 18:25   ` Atish Patra
2020-02-28 18:53 ` Marc Zyngier
2020-02-28 19:03   ` Atish Patra
2020-02-28 19:55     ` Marc Zyngier [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=4211bc32ef9a2de376f96d9e4d6c05df@kernel.org \
    --to=maz@kernel.org \
    --cc=Atish.Patra@wdc.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=tglx@linutronix.de \
    /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