From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"monstr@monstr.eu" <monstr@monstr.eu>,
"Andreas Färber" <afaerber@suse.de>,
"Russell King" <linux@arm.linux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Steffen Trumtrar" <s.trumtrar@pengutronix.de>,
"Kumar Gala" <galak@codeaurora.org>,
"Peter Crosthwaite" <peter.crosthwaite@xilinx.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <Pawel.Moll@arm.com>,
"Rob Herring" <robherring2@gmail.com>,
"Josh Cartwright" <josh.cartwright@ni.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] ARM: dts: zynq: Add OCM node
Date: Thu, 12 Feb 2015 06:58:36 -0800 [thread overview]
Message-ID: <5c1602f83c594a72aac78c245f1830fa@BL2FFO11FD052.protection.gbl> (raw)
In-Reply-To: <c64e7b4bf78649049cea3dceecea453c@BN1AFFO11FD014.protection.gbl>
On Thu, 2015-02-12 at 12:01PM +0100, Michal Simek wrote:
> On 02/12/2015 11:54 AM, Mark Rutland wrote:
> > On Thu, Feb 12, 2015 at 10:42:47AM +0000, Michal Simek wrote:
> >> Add OCM node for all zynq boards. OCM location
> >> can changed but for all current boards this
> >> is the location where OCM is.`
> >>
> >> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> >> ---
> >>
> >> Changes in v2:
> >> - Move node to board file suggested by Mark
> >>
> >> This patch is done based on discussion here.
> >> https://lkml.org/lkml/2014/12/1/396
> >>
> >> Mark: I expect you won't like amba bus reference or
> >> am I wrong?
> >
> > I'm fine with dropping things onto a bus in this way. If we're happy to
> > do it for other nodes I don't see why busses should be special.
>
> Wonderful. I will give people some time to comment this style.
Given that the location is discoverable, wouldn't it make sense to let
'reg' point to the ctrl/cfg registers in the SLCR and let the driver
handle the whereabouts of the OCM location? (but I guess this is going
in circles now, such a proposal was on the table at some point, IIRC).
But I'd prefer:
memory-controller@0xfffc0000 { /* the address here would of course not match all configurations */
interrupts = ...;
syscon = &slcr;
};
Soren
next prev parent reply other threads:[~2015-02-12 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 10:42 Michal Simek
2015-02-12 10:54 ` Mark Rutland
2015-02-12 11:01 ` Michal Simek
2015-02-12 14:58 ` Sören Brinkmann [this message]
2015-02-12 15:07 ` Mark Rutland
2015-02-12 15:09 ` Sören Brinkmann
2015-02-12 15:15 ` Michal Simek
[not found] ` <20150212145836.GZ18532@xsjandreislx>
2015-02-12 15:00 ` Michal Simek
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=5c1602f83c594a72aac78c245f1830fa@BL2FFO11FD052.protection.gbl \
--to=soren.brinkmann@xilinx.com \
--cc=Pawel.Moll@arm.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=josh.cartwright@ni.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=peter.crosthwaite@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
--cc=s.trumtrar@pengutronix.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®