public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@foss.arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
	"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	dl-linux-imx <linux-imx@nxp.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"van.freenix@gmail.com" <van.freenix@gmail.com>
Subject: Re: [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox
Date: Mon, 10 Jun 2019 11:00:33 +0100	[thread overview]
Message-ID: <20190610110033.28d21d21@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <AM0PR04MB448168C72F1D40C1B9BEB1F788130@AM0PR04MB4481.eurprd04.prod.outlook.com>

On Mon, 10 Jun 2019 01:32:49 +0000
Peng Fan <peng.fan@nxp.com> wrote:

Hi Peng,

[ ... ]

> > > > +
> > > > +	irq_count = platform_irq_count(pdev);
> > > > +	if (irq_count == -EPROBE_DEFER)
> > > > +		return irq_count;
> > > > +
> > > > +	if (irq_count && irq_count != val) {
> > > > +		dev_err(dev, "Interrupts not match num-chans\n");  
> > >
> > > Interrupts property does not match \"arm,num-chans\" would be more  
> > correct.
> > 
> > Given that interrupts are optional, do we have to rely on this?   
> 
> If there is interrupt property, the interrupts should match channel counts.
> 
> Do we actually
> > need one interrupt per channel?  
> 
> I thought about this, provide one interrupt for all channels.
> But there is no good way to let interrupt handlers know which
> channel triggers the interrupt. So I use one interrupt per channel.

Yeah, I was wondering about this as well. Seems like we need this indeed.
Just sounds wasteful, but I guess we don't expect many channels anyway,
normally.

Cheers,
Andre.

  reply	other threads:[~2019-06-10 10:00 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  8:30 [PATCH V2 0/2] mailbox: arm: introduce smc triggered mailbox peng.fan
2019-06-03  8:30 ` [PATCH V2 1/2] DT: mailbox: add binding doc for the ARM SMC mailbox peng.fan
2019-06-03 16:22   ` Florian Fainelli
2019-06-03 16:56     ` Sudeep Holla
2019-06-03 17:18       ` Andre Przywara
2019-06-06  2:51         ` Florian Fainelli
2019-06-06  3:24         ` Peng Fan
2019-06-20  9:22   ` Sudeep Holla
2019-06-20 16:13     ` Andre Przywara
2019-06-20 16:27       ` Jassi Brar
2019-07-08 22:19   ` Rob Herring
2019-07-09  1:40     ` Peng Fan
2019-07-09 13:31       ` Rob Herring
2019-06-03  8:30 ` [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox peng.fan
2019-06-03 16:32   ` Florian Fainelli
2019-06-06  3:35     ` Peng Fan
2019-06-06 13:20     ` Andre Przywara
2019-06-10  1:32       ` Peng Fan
2019-06-10 10:00         ` Andre Przywara [this message]
2019-06-12 12:59         ` Peng Fan
2019-06-12 17:18           ` Andre Przywara
2019-06-20  9:23   ` Sudeep Holla
2019-06-20 10:21     ` Peng Fan
2019-06-20 11:15       ` Sudeep Holla
2019-06-25  7:28         ` Peng Fan
2019-06-20 16:50   ` Jassi Brar
2019-06-25  7:20     ` Peng Fan
2019-06-26 17:05       ` André Przywara
2019-06-26 17:07         ` Florian Fainelli
2019-06-25  7:30     ` Peng Fan
2019-06-25 14:36       ` Jassi Brar
2019-06-26 13:31         ` Peng Fan
2019-06-26 16:31           ` Jassi Brar
2019-06-26 16:44           ` Florian Fainelli
2019-06-26 17:09             ` Sudeep Holla
2019-06-27 18:10               ` Florian Fainelli
2019-06-26 18:27             ` Jassi Brar
2019-06-27  9:09               ` Sudeep Holla
2019-06-27 15:32                 ` Jassi Brar
2019-06-27 17:07                   ` Sudeep Holla
2019-06-26 17:02           ` Sudeep Holla

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=20190610110033.28d21d21@donnerap.cambridge.arm.com \
    --to=andre.przywara@foss.arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=festevam@gmail.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=van.freenix@gmail.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