devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Mason <jonmason@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Russell King <linux@arm.linux.org.uk>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com
Subject: [PATCH v4 0/2] ARM: dts: bcm5301x: Add SVK DT files and docs
Date: Wed, 21 Oct 2015 18:46:02 -0400	[thread overview]
Message-ID: <1445467564-30024-1-git-send-email-jonmason@broadcom.com> (raw)

Changes in v4:
* Changed bootargs to stdout-path, per Sudeep Holla

Changes in v3:
* Updated the DT documentation compat strings
* Modified the include files and compat strings for the SVK DT files,
  per Hauke Mehrtens

Changes in v2: 
* Reorder the patches to add the DT binding documentation prior to the
  new DT files 
* Removed the DT documentation compat strings to only the SoCs, not the
  individual boards 
* Fixed the compat strings in the individual device tree files 
* Added the memory node and removed the "mem=" from the bootargs 


Add device tree files and update the documentation for Broadcom
Northstar based SVKs.  Since the bcm5301x.dtsi already exists, all that
is necessary is the dts files to enable the UARTs.  With these files,
the SVKs are able to boot to shell

Jon Mason (2):
  dt-bindings: Add new SoCs to bcm4708 DT bindings
  ARM: dts: bcm5301x: Add BCM SVK DT files

 .../devicetree/bindings/arm/bcm/brcm,bcm4708.txt   |  7 +++
 arch/arm/boot/dts/Makefile                         |  5 +-
 arch/arm/boot/dts/bcm94708.dts                     | 56 +++++++++++++++++++
 arch/arm/boot/dts/bcm94709.dts                     | 56 +++++++++++++++++++
 arch/arm/boot/dts/bcm953012k.dts                   | 63 ++++++++++++++++++++++
 5 files changed, 186 insertions(+), 1 deletion(-)
 create mode 100644 arch/arm/boot/dts/bcm94708.dts
 create mode 100644 arch/arm/boot/dts/bcm94709.dts
 create mode 100644 arch/arm/boot/dts/bcm953012k.dts

-- 
1.9.1

             reply	other threads:[~2015-10-21 22:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 22:46 Jon Mason [this message]
2015-10-21 22:46 ` [PATCH v4 1/2] dt-bindings: Add new SoCs to bcm4708 DT bindings Jon Mason
     [not found] ` <1445467564-30024-1-git-send-email-jonmason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-10-21 22:46   ` [PATCH v4 2/2] ARM: dts: bcm5301x: Add BCM SVK DT files Jon Mason

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=1445467564-30024-1-git-send-email-jonmason@broadcom.com \
    --to=jonmason@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=hauke@hauke-m.de \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.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).