From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Armada 375/38x MBus support
Date: Tue, 11 Feb 2014 12:55:13 -0300 [thread overview]
Message-ID: <20140211155512.GA24205@localhost> (raw)
In-Reply-To: <1392060298-27094-1-git-send-email-ezequiel.garcia@free-electrons.com>
On Mon, Feb 10, 2014 at 04:24:56PM -0300, Ezequiel Garcia wrote:
> As part of the submission of the Armada 375/38x initial support, these
> two small patches add MBus support.
>
> You will find that despite the MBus support being identical for the whole
> SoC family: Armada 370/XP/375 and 38x, we have per-SoC compatible for each
> of them.
>
> Such decision is being currently discussed; see:
>
> http://www.spinics.net/lists/arm-kernel/msg306480.html
>
These patches are not required, so please omit them entirely.
The new agreement [1] is to add SoC-specific compatible strings and also
declare the nodes as compatibles with the already supported SoC,
whenever appropriate.
For instance, the devicetrees for Armada 375 would have this mbus node:
mbus {
compatible = "marvell,armada375-mbus", "marvell,armada370-mbus"
}
And therefore, we don't need any changes in the driver for now.
[1] http://www.spinics.net/lists/arm-kernel/msg306727.html
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
prev parent reply other threads:[~2014-02-11 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 19:24 [PATCH 0/2] Armada 375/38x MBus support Ezequiel Garcia
2014-02-10 19:24 ` [PATCH 1/2] bus: mvebu-mbus: Add support for the Armada 375 SoCs Ezequiel Garcia
2014-02-10 19:24 ` [PATCH 2/2] bus: mvebu: Add support for the Armada 38x SoCs Ezequiel Garcia
2014-02-11 15:55 ` Ezequiel Garcia [this message]
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=20140211155512.GA24205@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.