From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 for 3.10] Introduce a Marvell EBU MBus driver
Date: Mon, 18 Mar 2013 16:24:11 +0100 [thread overview]
Message-ID: <20130318162411.11c9e3ab@skate> (raw)
In-Reply-To: <201303181459.10954.arnd@arndb.de>
Dear Arnd Bergmann,
On Mon, 18 Mar 2013 14:59:10 +0000, Arnd Bergmann wrote:
> I would prefer not to merge the DT binding, but I'm fine with the
> current implementation, as in the pull request that Jason sent
> me. How about this:
>
> * You remove the Documentation/devicetree/bindings/arm/mvebu-mbus.txt file
> that is the main source of disagreement, along with the mvebu_mbus_dt_init
> function.
> * All conversion patches get changed to not add properties to the soc
> node but instead call mvebu_mbus_init directly. That code is there
> already.
>
> I can take those patches, and we can work on a better DT binding for
> a later release without having to hold up other conversions.
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?
Anyway, whatever your decision is, I can submit an updated patch set
that implements this, and also fix the mv78xx0 patch (my colleague
Gregory Clement found a problem with the mv78xx0 when testing on real
hardware).
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-18 15:24 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 [this message]
2013-03-18 15:58 ` Arnd Bergmann
2013-03-18 16:26 ` Jason Cooper
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=20130318162411.11c9e3ab@skate \
--to=thomas.petazzoni@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 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).