devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Kryger <tim.kryger@linaro.org>
To: Christian Daudt <bcm@fixthebug.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>
Cc: Tim Kryger <tim.kryger@linaro.org>,
	Broadcom Kernel Feedback List
	<bcm-kernel-feedback-list@broadcom.com>,
	Device Tree List <devicetree@vger.kernel.org>,
	Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linaro Patches List <patches@linaro.org>
Subject: [PATCH 0/2] Enable I2C on bcm28155-ap
Date: Fri, 6 Dec 2013 15:45:26 -0800	[thread overview]
Message-ID: <1386373528-13045-1-git-send-email-tim.kryger@linaro.org> (raw)

This series enables all the I2C busses on the bcm28155-ap board.

These patches appeared in another series that was partially accepted.
  https://lkml.org/lkml/2013/11/14/517

It depends on:  https://lkml.org/lkml/2013/12/5/508

Tim Kryger (2):
  ARM: dts: bcm281xx: Add i2c busses
  ARM: dts: bcm28155-ap: Enable all the i2c busses

 arch/arm/boot/dts/bcm11351.dtsi   | 40 +++++++++++++++++++++++++++++++++++++++
 arch/arm/boot/dts/bcm28155-ap.dts | 20 ++++++++++++++++++++
 2 files changed, 60 insertions(+)

-- 
1.8.0.1

             reply	other threads:[~2013-12-06 23:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 23:45 Tim Kryger [this message]
2013-12-06 23:45 ` [PATCH 1/2] ARM: dts: bcm281xx: Add i2c busses Tim Kryger
2013-12-10  7:28   ` Christian Daudt
2013-12-06 23:45 ` [PATCH 2/2] ARM: dts: bcm28155-ap: Enable all the " Tim Kryger
     [not found]   ` <1386373528-13045-3-git-send-email-tim.kryger-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-12-10  7:07     ` Christian Daudt

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=1386373528-13045-1-git-send-email-tim.kryger@linaro.org \
    --to=tim.kryger@linaro.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bcm@fixthebug.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=patches@linaro.org \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.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).