From: Tony Lindgren <tony@atomide.com>
To: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
Rob Herring <robherring2@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
Matt Porter <mporter@konsulko.com>,
Koen Kooi <koen@dominion.thruhere.net>,
Robert Nelson <robertcnelson@gmail.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Guenter Roeck <linux@roeck-us.net>,
Geert Uytterhoeven <geert+renesas@glider.be>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Pantelis Antoniou <panto@antoniou-consulting.com>
Subject: Re: [PATCH] arm: dts: Beaglebone i2c definitions
Date: Wed, 20 May 2015 11:17:08 -0700 [thread overview]
Message-ID: <20150520181708.GL10274@atomide.com> (raw)
In-Reply-To: <20150514153822.GJ15563@atomide.com>
* Tony Lindgren <tony@atomide.com> [150514 08:40]:
> * Pantelis Antoniou <pantelis.antoniou@konsulko.com> [150513 01:05]:
> > The beaglebone family of boards contain two I2C busses enabled.
> > The first one with a baseboard identification EEPROM and a
> > cape I2C bus.
>
> This seems safe to apply as the i2c2 pins are listed in the cape
> specification.
>
> These pins could be used for other devices too.. But in that case
> the cape would not follow the cape standard.
So applying this one into omap-for-v4.2/dt thanks.
Tony
prev parent reply other threads:[~2015-05-20 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 8:04 [PATCH] arm: dts: Beaglebone i2c definitions Pantelis Antoniou
[not found] ` <1431504274-32084-1-git-send-email-pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2015-05-14 15:38 ` Tony Lindgren
2015-05-20 18:17 ` Tony Lindgren [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=20150520181708.GL10274@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=grant.likely@secretlab.ca \
--cc=koen@dominion.thruhere.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mporter@konsulko.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=robertcnelson@gmail.com \
--cc=robherring2@gmail.com \
--cc=srinivas.kandagatla@linaro.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).