From: Robert Nelson <robertcnelson@gmail.com>
To: "Li, Yong B" <yong.b.li@intel.com>
Cc: Tony Lindgren <tony@atomide.com>,
Benoit Cousson <bcousson@baylibre.com>,
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>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux kernel <linux-kernel@vger.kernel.org>,
"sdliyong@gmail.com" <sdliyong@gmail.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Subject: Re: [PATCH] ARM: dts: am335x-boneblack: add i2c1 DT entry
Date: Tue, 7 Jun 2016 12:14:57 -0500 [thread overview]
Message-ID: <CAOCHtYhBSS+D-BQH28FO+RxyzvDg-yeX+6nvLu11G3TNkF7ELg@mail.gmail.com> (raw)
In-Reply-To: <BCE6BEBCDDF4B84E891D2320CBF96F1D3F9FD673@SHSMSX101.ccr.corp.intel.com>
On Tue, Jun 7, 2016 at 1:14 AM, Li, Yong B <yong.b.li@intel.com> wrote:
> Thanks Tony.
>
> I checked the DTS/overlays using linux-yocto-4.1 kernel(Ostro OS). It seems to me that the kernel/u-boot do not include the latest overlay support patch. And I also tested the latest Debian 8.4 using BBB boards, the I2C1 does not work too. This patch is the simplest solution for I2C1/I2C2 in linux-yocto-4.1.
ps, your patch is also broken, you didn't even mux the pins, so i2c1
doesn't work for you anyways. ;)
pinctrl-0 = <&i2c2_pins>; -> pinctrl-0 = <&i2c1_pins>;
Option 1:
With the latest BBB image's, we utilize "cape_universal", thus you can
enable I2C1 via:
root@beaglebone:~# config-pin -l P9.17
default gpio gpio_pu gpio_pd spi i2c pwm
root@beaglebone:~# config-pin -l P9.18
default gpio gpio_pu gpio_pd spi i2c pwm
root@beaglebone:~# config-pin P9.17 i2c
root@beaglebone:~# config-pin P9.18 i2c
Option 2, for the BB-I2C1 overlay:
add
cape_enable=bone_capemgr.enable_partno=BB-I2C1
Option 3, wait for Pantelis's solution... ;)
http://comments.gmane.org/gmane.linux.kernel/2234662
Regards,
--
Robert Nelson
https://rcn-ee.com/
next prev parent reply other threads:[~2016-06-07 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 7:41 [PATCH] ARM: dts: am335x-boneblack: add i2c1 DT entry Yong Li
[not found] ` <CAOCHtYib9YxckneM-j0Gk1YE=MnvAwAhvDjEDEuFJbH6W3EcWA@mail.gmail.com>
2016-06-02 17:39 ` Tony Lindgren
2016-06-02 17:45 ` Robert Nelson
2016-06-02 17:56 ` Tony Lindgren
2016-06-03 5:46 ` Li, Yong B
2016-06-07 6:00 ` Tony Lindgren
2016-06-07 6:14 ` Li, Yong B
2016-06-07 17:14 ` Robert Nelson [this message]
2016-06-08 7:11 ` Li, Yong B
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=CAOCHtYhBSS+D-BQH28FO+RxyzvDg-yeX+6nvLu11G3TNkF7ELg@mail.gmail.com \
--to=robertcnelson@gmail.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sdliyong@gmail.com \
--cc=tony@atomide.com \
--cc=yong.b.li@intel.com \
/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).