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

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.

> Thanks,
> 
>          M.

-- 
Regards,
Atish

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 23:22 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 [this message]
2020-02-28 19:55     ` Marc Zyngier

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=39c1cd2c80d67b8b39fe6e2f867e65fd2d42f6d6.camel@wdc.com \
    --to=atish.patra@wdc.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=maz@kernel.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

all inboxes | Powered by JetHome®