From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: Fix the internal register ranges translation
Date: Thu, 18 Jul 2013 10:55:06 -0300 [thread overview]
Message-ID: <20130718135505.GA3264@localhost> (raw)
In-Reply-To: <51E63B3A.2010807@keymile.com>
Hi Gerlando,
On Wed, Jul 17, 2013 at 08:35:38AM +0200, Gerlando Falauto wrote:
> On 07/16/2013 02:56 PM, Ezequiel Garcia wrote:
> [...]
> > Also, speaking of "device bus" this nand node should be behind a devicebus node.
> >
> > ranges = <MBUS_ID(0xf0, 0x01) 0 0 0xf1000000 0x100000 /* internal-regs */
> > MBUS_ID(0x01, 0x2f) 0 0 0xf4000000 0x400>;
> >
> > devbus {
> > status = "okay";
> > ranges = <0 MBUS_ID(0x01, 0x2f) 0 0x400>;
> >
> > /* nand */
> > nand {
> > compatible = "marvell,orion-nand";
> > reg = <0 0x400>;
> > };
> > };
> >
> > (notice this will allow you to relocate the base address of the NAND windows
> > easily if it conflicts with your PCIe needs).
>
> I am MAYBE slowly starting to understand this whole mbus rework.
> Just one remark though: don't you think it would make sense to add
> something like:
>
> #define MBUS_ID_INTERNAL_REGS MBUS_ID(0xf0, 0x01)
> #define MBUS_ID_NAND MBUS_ID(0x01, 0x2f)
>
Yeah, maybe it would make sense. This has been discussed in the past
and others were against, so that's the reason it's not included in
the series I submitted.
But feel free to send a patch proposing it once the MBus is merged!
Thanks,
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Ezequiel Garcia <ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Gerlando Falauto
<gerlando.falauto-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Cc: Lior Amsalem <alior-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
"Longchamp,
Valentin"
<Valentin.Longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>,
"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] ARM: Kirkwood: Fix the internal register ranges translation
Date: Thu, 18 Jul 2013 10:55:06 -0300 [thread overview]
Message-ID: <20130718135505.GA3264@localhost> (raw)
In-Reply-To: <51E63B3A.2010807-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Hi Gerlando,
On Wed, Jul 17, 2013 at 08:35:38AM +0200, Gerlando Falauto wrote:
> On 07/16/2013 02:56 PM, Ezequiel Garcia wrote:
> [...]
> > Also, speaking of "device bus" this nand node should be behind a devicebus node.
> >
> > ranges = <MBUS_ID(0xf0, 0x01) 0 0 0xf1000000 0x100000 /* internal-regs */
> > MBUS_ID(0x01, 0x2f) 0 0 0xf4000000 0x400>;
> >
> > devbus {
> > status = "okay";
> > ranges = <0 MBUS_ID(0x01, 0x2f) 0 0x400>;
> >
> > /* nand */
> > nand {
> > compatible = "marvell,orion-nand";
> > reg = <0 0x400>;
> > };
> > };
> >
> > (notice this will allow you to relocate the base address of the NAND windows
> > easily if it conflicts with your PCIe needs).
>
> I am MAYBE slowly starting to understand this whole mbus rework.
> Just one remark though: don't you think it would make sense to add
> something like:
>
> #define MBUS_ID_INTERNAL_REGS MBUS_ID(0xf0, 0x01)
> #define MBUS_ID_NAND MBUS_ID(0x01, 0x2f)
>
Yeah, maybe it would make sense. This has been discussed in the past
and others were against, so that's the reason it's not included in
the series I submitted.
But feel free to send a patch proposing it once the MBus is merged!
Thanks,
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
next prev parent reply other threads:[~2013-07-18 13:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 15:31 [PATCH] ARM: Kirkwood: Fix the internal register ranges translation Ezequiel Garcia
2013-06-18 15:31 ` Ezequiel Garcia
2013-06-18 19:42 ` Sebastian Hesselbarth
2013-06-18 19:42 ` Sebastian Hesselbarth
2013-06-18 19:47 ` Ezequiel Garcia
2013-06-18 19:47 ` Ezequiel Garcia
2013-06-19 18:36 ` Jason Cooper
2013-06-19 18:36 ` Jason Cooper
2013-06-19 18:42 ` Ezequiel Garcia
2013-06-19 18:42 ` Ezequiel Garcia
2013-06-19 18:43 ` Jason Cooper
2013-06-19 18:43 ` Jason Cooper
2013-06-21 15:41 ` Jason Cooper
2013-06-21 15:41 ` Jason Cooper
2013-07-16 9:37 ` Gerlando Falauto
2013-07-16 9:37 ` Gerlando Falauto
2013-07-16 12:56 ` Ezequiel Garcia
2013-07-16 12:56 ` Ezequiel Garcia
2013-07-16 18:51 ` Gerlando Falauto
2013-07-16 18:51 ` Gerlando Falauto
2013-07-18 14:05 ` Ezequiel Garcia
2013-07-18 14:05 ` Ezequiel Garcia
2013-07-17 6:35 ` Gerlando Falauto
2013-07-17 6:35 ` Gerlando Falauto
2013-07-18 13:55 ` Ezequiel Garcia [this message]
2013-07-18 13:55 ` Ezequiel Garcia
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=20130718135505.GA3264@localhost \
--to=ezequiel.garcia@free-electrons.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.