mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Måns Rullgård" <mans@mansr.com>
To: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>,
	Marc Zyngier <marc.zyngier@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Sebastian Frias <sf84@laposte.net>
Subject: Re: [RFC PATCH v2] irqchip: Add support for Tango interrupt controller
Date: Mon, 18 Jan 2016 13:04:08 +0000	[thread overview]
Message-ID: <yw1xwpr7rqd3.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <569CE0F2.1060507@sigmadesigns.com> (Marc Gonzalez's message of "Mon, 18 Jan 2016 13:56:18 +0100")

Marc Gonzalez <marc_gonzalez@sigmadesigns.com> writes:

> +	if (of_property_read_u32(node, "reg", &ctl))
> +		panic("%s: failed to get reg base", node->name);
> +
> +	chip = kzalloc(sizeof(*chip), GFP_KERNEL);
> +	chip->ctl = ctl;
> +	chip->base = base;

I think it might be better to let the OF core convert the "reg" property
to a struct resource, then get the offset by subtracting from the base
(physical) address.  Otherwise it will break badly if someone thinks
it's safe to drop "ranges" from the outer node and use absolute
addresses in the child nodes (that's how the "reg" property typically
behaves).

Anyway, thanks for revisiting this.  I never got a straight answer (or
any answer for that matter) when I asked which approach would be
preferred, and then I had better things to do than keep trying patches
until people got happy.

-- 
Måns Rullgård

  reply	other threads:[~2016-01-18 13:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 12:56 Marc Gonzalez
2016-01-18 13:04 ` Måns Rullgård [this message]
2016-01-18 15:57 ` Marc Gonzalez
2016-01-18 16:44   ` [RFC PATCH v3] " Marc Gonzalez
2016-01-20 16:04     ` Marc Zyngier
2016-01-20 16:10       ` Måns Rullgård
2016-01-20 16:23         ` Marc Zyngier
2016-01-20 16:25           ` Måns Rullgård
2016-01-20 16:36             ` Marc Gonzalez
2016-01-20 16:38               ` Måns Rullgård
2016-01-20 16:43                 ` Marc Gonzalez
2016-01-20 18:09                   ` Måns Rullgård
2016-01-22 15:58                     ` Marc Gonzalez
2016-01-22 16:35                       ` Måns Rullgård
2016-01-22 16:37                         ` Marc Gonzalez
2016-01-22 16:39                           ` Måns Rullgård
2016-01-22 16:45                             ` Marc Gonzalez
2016-01-22 16:49                               ` Måns Rullgård
2016-01-20 16:24         ` Marc Gonzalez
2016-01-20 16:26           ` Måns Rullgård
2016-01-20 17:02           ` Mark Rutland
2016-01-20 17:05             ` Måns Rullgård
2016-01-20 17:05             ` Marc Gonzalez
2016-01-20 17:06               ` Måns Rullgård

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=yw1xwpr7rqd3.fsf@unicorn.mansr.com \
    --to=mans@mansr.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=marc_gonzalez@sigmadesigns.com \
    --cc=sf84@laposte.net \
    --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®