From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 for 3.10] Introduce a Marvell EBU MBus driver
Date: Mon, 18 Mar 2013 12:26:16 -0400 [thread overview]
Message-ID: <20130318162616.GJ13280@titan.lakedaemon.net> (raw)
In-Reply-To: <201303181558.59608.arnd@arndb.de>
Arnd,
On Mon, Mar 18, 2013 at 03:58:59PM +0000, Arnd Bergmann wrote:
> On Monday 18 March 2013, Thomas Petazzoni wrote:
> > So even the DT-only sub-architecture (such as mvebu) should hard-code
> > the register base addresses?
> >
> > The proposed DT binding in the current patch is very minimal, and I
> > don't see why the more elaborate DT binding that you proposed could not
> > be implemented as an improvement of it: the DT binding you proposed
> > seems backward compatible with the one currently implemented, no?
>
> It's quite possible that it could be done in a backward compatible
> way, I just like to be on the safe side in case it's not.
We do have a bit more latitude here. There isn't a single shipping
mvebu device with a fdt enabled bootloader. So, as long as we aren't
impacting other SoCs/drivers, I'm comfortable with taking a release or
two to shake it out. I understand we prefer not to do that, but in this
case, I don't want to hold up everything else in the pipeline.
thx,
Jason.
next prev parent reply other threads:[~2013-03-18 16:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 16:59 [PATCH v2 for 3.10] Introduce a Marvell EBU MBus driver Thomas Petazzoni
2013-03-06 16:59 ` [PATCH 01/10] arm: plat-orion: only build addr-map.c when needed Thomas Petazzoni
2013-03-06 16:59 ` [PATCH 02/10] arm: plat-orion: use mv_mbus_dram_info() in PCIe code Thomas Petazzoni
2013-03-06 16:59 ` [PATCH 03/10] arm: mach-orion5x: use mv_mbus_dram_info() in PCI code Thomas Petazzoni
2013-03-06 16:59 ` [PATCH 04/10] bus: introduce an Marvell EBU MBus driver Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 05/10] arm: mach-mvebu: convert to use mvebu-mbus driver Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 06/10] arm: mach-kirkwood: " Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 07/10] arm: mach-dove: " Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 08/10] arm: mach-orion5x: " Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 09/10] arm: mach-mv78xx0: convert to use the " Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 10/10] arm: plat-orion: remove addr-map code Thomas Petazzoni
2013-03-14 19:53 ` [PATCH v2 for 3.10] Introduce a Marvell EBU MBus driver Gregory CLEMENT
2013-03-18 14:59 ` Arnd Bergmann
2013-03-18 15:24 ` Thomas Petazzoni
2013-03-18 15:58 ` Arnd Bergmann
2013-03-18 16:26 ` Jason Cooper [this message]
2013-03-17 18:59 ` Jason Cooper
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=20130318162616.GJ13280@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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;
as well as URLs for NNTP newsgroup(s).