All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] ARM: bcm476x: Add platform infrastructure
Date: Thu, 18 Oct 2012 13:48:01 +0000	[thread overview]
Message-ID: <201210181348.02110.arnd@arndb.de> (raw)
In-Reply-To: <20121014223023.611069832@gmail.com>

On Sunday 14 October 2012, Domenico Andreoli wrote:
> From: Domenico Andreoli <domenico.andreoli@linux.com>
> 
> Platform infrastructure for the Broadcom BCM476x ARMv6 SoCs.

Hi Domenico,

All your patches look good to me now, except for one thing throughout
the bindings:

> Index: b/Documentation/devicetree/bindings/arm/bcm476x.txt
> ===================================================================
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/bcm476x.txt
> @@ -0,0 +1,15 @@
> +Broadcom BCM4760 and BCM4761 SoCs device tree bindings
> +------------------------------------------------------
> +
> +Boards with the BCM4760 SoC shall have the following properties:
> +
> +Required root node property:
> +
> +compatible = "brcm,bcm4760";
> +
> +
> +Boards with the BCM4761 SoC shall have the following properties:
> +
> +Required root node property:
> +
> +compatible = "brcm,bcm4761";

I probably wasn't clear enough with my request to have specific
chip identifiers in the device tree "compatible" nodes. The idea
generally is that for completely identical hardware blocks, you
just need to put the first known variant into the driver, e.g.
"brcm,bcm4760-system-timer", and in case of a later chip that
is compatible with it, you list both "brcm,bcm4760-system-timer"
and "brcm,bcm4761-system-timer" in the compatible property of the
device tree. The way you did it is also correct and works, but
is a bit less common.

How do you want to merge your patches? The preferred way from
our side is to get a pull request from you sent to arm at kernel.org
with Cc to the linux-arm-kernel mailing list, but we can also
pick up the patches separately if necessary.

For the patches that go into different directories like the clk
and the clocksource drivers, please Cc the respective subsystem
maintainers and ask them for an Ack. It certainly makes sense
for a new platform port to get merged through the arm-soc tree,
but any future improvements should normally just go through the
subsystem trees.

	Arnd

  reply	other threads:[~2012-10-18 13:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-14 22:14 [PATCH v2 0/5] ARM: Add support for Broadcom BCM476x SoCs Domenico Andreoli
2012-10-14 22:14 ` [PATCH v2 1/5] ARM: bcm476x: Add platform infrastructure Domenico Andreoli
2012-10-18 13:48   ` Arnd Bergmann [this message]
2012-10-18 15:47     ` Domenico Andreoli
2012-10-19  9:03       ` Arnd Bergmann
2012-10-14 22:14 ` [PATCH v2 2/5] ARM: bcm476x: Add system timer Domenico Andreoli
2012-10-14 22:14 ` [PATCH v2 3/5] ARM: bcm476x: Add ripple counter Domenico Andreoli
2012-10-14 22:14 ` [PATCH v2 4/5] ARM: bcm476x: Add stub clock driver Domenico Andreoli
2012-10-14 22:14 ` [PATCH v2 5/5] ARM: bcm476x: Add restart hook Domenico Andreoli

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=201210181348.02110.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 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.