From: Tony Lindgren <tony@atomide.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: Tom Rini <trini@ti.com>, Matt Ranostay <mranostay@gmail.com>,
robh+dt@kernel.org, mark.rutland@arm.com,
Russell King <linux@arm.linux.org.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux kernel <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@gmail.com>,
Matt Porter <matt.porter@linaro.org>
Subject: Re: [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition
Date: Mon, 12 May 2014 14:07:48 -0700 [thread overview]
Message-ID: <20140512210747.GE5668@atomide.com> (raw)
In-Reply-To: <CAOCHtYgg7jwxswH+mqF3RA7-0RP-nGuft+Ze-GRwu1fbA6+0Bw@mail.gmail.com>
* Robert Nelson <robertcnelson@gmail.com> [140512 13:58]:
> >> Either case if fine with me. As who knows when the dtc "overlay" will
> >> every truly make it mainline, as the capemgr was the only real kernel
> >> user of the i2c/at24 eeprom information.
> >
> > Sounds like we should keep it disabled though so u-boot can be used
> > to toggle it while waiting for the capemgr. That's because the board
> > has a header for pins, so it's not exactly limited to just the capes.
> >
> > Anybody working on enabling/disabling cape dtb configurations in u-boot?
>
> Well,
>
> Would Tom even approve of that in mainline u-boot? He didn't want my
> "invert" the gpio to enable the usb hub on the older beagle xm A/B..
>
> http://lists.denx.de/pipermail/u-boot/2014-January/172154.html
>
> http://lists.denx.de/pipermail/u-boot/2014-January/172274.html
Right, no idea. But until we have some way to actually use the capes
without conflicting dts entries, I can't merge them.
Regards,
Tony
next prev parent reply other threads:[~2014-05-12 21:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 1:43 [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition Matt Ranostay
2014-05-12 19:50 ` Tony Lindgren
2014-05-12 19:59 ` Robert Nelson
2014-05-12 20:15 ` Tony Lindgren
2014-05-12 20:27 ` Robert Nelson
2014-05-12 20:42 ` Tony Lindgren
2014-05-12 20:57 ` Robert Nelson
2014-05-12 21:07 ` Tony Lindgren [this message]
2014-05-13 12:53 ` Tom Rini
2014-05-13 14:06 ` Javier Martinez Canillas
2014-05-13 14:13 ` Tom Rini
2014-05-13 14:22 ` Matt Porter
2014-05-13 14:39 ` Javier Martinez Canillas
2014-05-13 17:07 ` Pantelis Antoniou
2014-05-13 17:51 ` Javier Martinez Canillas
2014-05-13 20:24 ` John Syn
2014-05-14 3:39 ` Pantelis Antoniou
2014-05-14 5:44 ` John Syn
2014-05-14 7:12 ` Javier Martinez Canillas
2014-05-14 3:24 ` Pantelis Antoniou
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=20140512210747.GE5668@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.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=matt.porter@linaro.org \
--cc=mranostay@gmail.com \
--cc=pantelis.antoniou@gmail.com \
--cc=robertcnelson@gmail.com \
--cc=robh+dt@kernel.org \
--cc=trini@ti.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