From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver
Date: Sat, 6 Apr 2013 15:32:06 +0200 [thread overview]
Message-ID: <201304061532.06280.arnd@arndb.de> (raw)
In-Reply-To: <20130405214510.GB16221@obsidianresearch.com>
On Friday 05 April 2013, Jason Gunthorpe wrote:
> I look at this and sort of go 'hmm'. These are basically register
> offsets into the block starting at 0xd0010400. I don't see any
> registers that are shared between targets. It would be simpler to keep
> each target as a seperate node and seperate driver instance.
>
> Combining that idea with the suggestion for target-id centric mbus DT
> binding:
>
> bootcs at d0010400 {
> compatible = "marvell,armada370-devbus";
> ranges = <0 MAPDEF_BOOTCS 0x1000>
> reg = <MAPDEF_INTERNAL + 0x10400 0x8>; // boot cs register set
> devbus,dev-width = <1>;
> [..] etc
>
> rom at 0 {
> reg = <0 0x1000>
> }
> }
+1
Good idea
Arnd
next prev parent reply other threads:[~2013-04-06 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 21:11 [PATCH v2 0/5] Device Bus support for Marvell EBU SoC Ezequiel Garcia
2013-04-05 21:11 ` [PATCH v2 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver Ezequiel Garcia
2013-04-05 21:45 ` Jason Gunthorpe
2013-04-05 22:09 ` Ezequiel Garcia
2013-04-06 13:32 ` Arnd Bergmann [this message]
2013-04-05 21:11 ` [PATCH v2 2/5] ARM: mvebu: Add Device Bus support for Armada 370/XP SoC Ezequiel Garcia
2013-04-05 21:11 ` [PATCH v2 3/5] ARM: mvebu: Add support for NOR flash device on Armada XP-GP board Ezequiel Garcia
2013-04-05 21:11 ` [PATCH v2 4/5] ARM: mvebu: Add support for NOR flash device on Openblocks AX3 board Ezequiel Garcia
2013-04-05 21:12 ` [PATCH v2 5/5] ARM: mvebu: Add Device Bus and CFI flash memory support to defconfig 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=201304061532.06280.arnd@arndb.de \
--to=arnd@arndb.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox