linux-kernel - Re: [PATCH] ARM: dts: zynq: Add OCM node

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150212143138.GB27577@jcartwri.amer.corp.natinst.com>
Date:	Thu, 12 Feb 2015 08:31:38 -0600
From:	Josh Cartwright <joshc@...com>
To:	Mark Rutland <mark.rutland@....com>
Cc:	Michal Simek <michal.simek@...inx.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"monstr@...str.eu" <monstr@...str.eu>,
	Andreas F?rber <afaerber@...e.de>,
	S?ren Brinkmann <soren.brinkmann@...inx.com>,
	Russell King <linux@....linux.org.uk>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Steffen Trumtrar <s.trumtrar@...gutronix.de>,
	Kumar Gala <galak@...eaurora.org>,
	Peter Crosthwaite <peter.crosthwaite@...inx.com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <Pawel.Moll@....com>,
	Rob Herring <robherring2@...il.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] ARM: dts: zynq: Add OCM node

On Thu, Feb 12, 2015 at 10:26:16AM +0000, Mark Rutland wrote:
> On Thu, Feb 12, 2015 at 10:22:07AM +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@...inx.com>
> > ---
> > 
> > This patch is done based on discussion here.
> > https://lkml.org/lkml/2014/12/1/396
> > 
> > There are some ways how to do it.
> > OCM location can be changed but board DTS files
> > can easily rewrite it.
> > The problem which there is that node has address
> > in it but maybe someone can suggest better solution.
> 
> Given that the node is so simple, can't this be pushed down into the
> board files? So long as the label is consistent anything else that's
> referring to it should still work.

Not that I have a strong opinion, but I've found that sometimes it's
nice to be able to just glance at the SoC dtsi file to get an
understanding of all of the hardware currently being modeled.

  Josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/