linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] versatile: sic: add device tree bindings
Date: Fri, 13 Jan 2012 19:04:56 +0000	[thread overview]
Message-ID: <20120113190456.GC1068@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120113184151.GC22767@ponder.secretlab.ca>

On Fri, Jan 13, 2012 at 11:41:51AM -0700, Grant Likely wrote:
> On Fri, Jan 13, 2012 at 10:58:34AM +0000, Jamie Iles wrote:
> > On Fri, Jan 13, 2012 at 10:48:42AM +0000, Russell King - ARM Linux wrote:
> > > On Fri, Jan 13, 2012 at 12:44:00AM +0000, Jamie Iles wrote:
> > > > +#ifdef CONFIG_OF
> > > > +int __init sic_of_init(struct device_node *np, struct device_node *parent)
> > > > +{
> > > > +	struct fpga_irq_data *sic_data = kzalloc(sizeof(*sic_data), GFP_KERNEL);
> > > > +	int err = -ENOMEM, irq;
> > > > +
> > > > +	if (WARN_ON(!sic_data))
> > > > +		return err;
> > > > +
> > > > +	sic_data->base = of_iomap(np, 0);
> > > > +	if (WARN_ON(!sic_data->base))
> > > > +		goto out_free_data;
> > > > +
> > > > +	irq = irq_of_parse_and_map(np, 0);
> > > > +	if (irq < 0)
> > > > +		goto out_free_data;
> > > > +
> > > > +	sic_data->irq_start = irq_alloc_descs(-1, 0, 32, numa_node_id());
> > > > +	if (WARN_ON(sic_data->irq_start < 0)) {
> > > > +		err = sic_data->irq_start;
> > > > +		goto out_unmap;
> > > > +	}
> > > > +	sic_data->domain.of_node = of_node_get(np);
> > > > +
> > > > +	fpga_irq_init(irq, ~0, sic_data);
> > > 
> > > I notice that you completely ignore the validity mask, and initialize all
> > > 32 interrupts.  This is wrong.  You don't think I put the validity mask
> > > there just to obfuscate the code?
> > 
> > OK, that is wrong.  The validity mask is used for the non-DT platforms, 
> > for the DT one I'll add a property stating the valid mask:
> > 
> > 	arm,valid-irq-mask = <0x001fffff>;
> > 
> > to the node in the trees.
> 
> Shouldn't be necessary when the driver is converted to using the
> linear mapping.  When that happens, only the requested irqs will get
> mapped.

What I'm saying is that they shouldn't even be _published_ as
potentially valid IRQs.

  reply	other threads:[~2012-01-13 19:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13  0:43 [PATCH 0/2] Full DT IRQ support for versatile Jamie Iles
2012-01-13  0:44 ` [PATCH 1/2] versatile: sic: add device tree bindings Jamie Iles
2012-01-13  2:29   ` Grant Likely
2012-01-13 10:35     ` Jamie Iles
2012-01-13 21:00       ` Grant Likely
2012-01-13 21:19         ` Russell King - ARM Linux
2012-01-13 10:48   ` Russell King - ARM Linux
2012-01-13 10:58     ` Jamie Iles
2012-01-13 18:41       ` Grant Likely
2012-01-13 19:04         ` Russell King - ARM Linux [this message]
2012-01-13  0:44 ` [PATCH 2/2] versatile: dt: register interrupt controllers from dt Jamie Iles
2012-01-13  1:20 ` [PATCH 0/2] Full DT IRQ support for versatile Grant Likely
2012-01-13  1:42   ` Jamie Iles
2012-01-13  2:31     ` Grant Likely

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=20120113190456.GC1068@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 NNTP newsgroup(s).