From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Kirkwood - Remove kirkwood_setup_wins and rely on the DT binding
Date: Tue, 17 Sep 2013 20:48:31 +0200 [thread overview]
Message-ID: <5238A3FF.4030305@gmail.com> (raw)
In-Reply-To: <20130917181742.GA4182@obsidianresearch.com>
On 09/17/2013 08:17 PM, Jason Gunthorpe wrote:
> On Tue, Sep 17, 2013 at 08:03:01PM +0200, Thomas Petazzoni wrote:
>> but until that exists, we thought that pushing the ranges property down
>> to the .dts file was the least horrible solution.
>
> I think we can get away with doing it the other way for kirkwood,
> here are my reasons:
> - Kirkwood is mature now, the DT is basically complete, we shouldn't
> need to churn the ranges in the dtsi much, if at all.
> - There are 31 kirkwood dts files, and none of them need a ranges
> different from the default
> - Kirkwood has more than enough mbus windows, we don't need to be
> stingy with them
> - The board files were already sort of like this, but a big chunk
> of the 31 boards were missing ranges entirely.
>
> Basically, no board file has a ranges, only the kirkwood.dtsi has a
> ranges.
Dove will also have its mbus ranges located in the SoC dtsi for the
same above reasons. The patch is already queued in mvebu/for-next.
Sebastian
next prev parent reply other threads:[~2013-09-17 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 22:47 [PATCH] arm: Kirkwood - Remove kirkwood_setup_wins and rely on the DT binding Jason Gunthorpe
2013-09-17 13:32 ` Ezequiel Garcia
2013-09-17 15:36 ` Jason Gunthorpe
2013-09-17 18:03 ` Thomas Petazzoni
2013-09-17 18:17 ` Jason Gunthorpe
2013-09-17 18:25 ` Ezequiel Garcia
2013-09-17 18:48 ` Sebastian Hesselbarth [this message]
2013-09-17 18:58 ` Thomas Petazzoni
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=5238A3FF.4030305@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.