From: Tony Lindgren <tony@atomide.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: 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@gmail.com, matt.porter@linaro.org
Subject: Re: [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition
Date: Mon, 12 May 2014 13:42:13 -0700 [thread overview]
Message-ID: <20140512204213.GD5668@atomide.com> (raw)
In-Reply-To: <CAOCHtYg6XpF0Gbo4iFqsFvP=QSivQQvCzov8UfxeLXMzrRYEWw@mail.gmail.com>
* Robert Nelson <robertcnelson@gmail.com> [140512 13:27]:
> >> >
> >> > If these pins are not used for i2c2 on some capes, this device
> >> > should be set to status = "disabled" state by default. Then
> >> > u-boot could re-enable it on the boards that have i2c2 in use.
> >>
> >> To-date, this is the i2c bus that all capes have placed an at24 eeprom
> >> for cape identification.
> >
> > And how many capes actually implement the eeprom cape identification
> > out of the available capes? :)
>
> Not including one off designs in someone's lab. We will never have an
> accurate number. ;)
>
> So far; just the ones that want their "cape" detected in the default
> image currently being shipped by CircuitCo. Otherwise the few that
> I've seen without an eeprom, usually follow this default pinmux.
>
> http://elinux.org/CircuitCo:Basic_Proto_Cape
>
> Which includes that i2c bus enabled.
OK thanks for the info.
> 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?
Regards,
Tony
next prev parent reply other threads:[~2014-05-12 20:42 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 [this message]
2014-05-12 20:57 ` Robert Nelson
2014-05-12 21:07 ` Tony Lindgren
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=20140512204213.GD5668@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 \
/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