From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: ep93xx: Enable i2c support for ep9302
Date: Tue, 12 Jun 2012 07:50:59 +1000 [thread overview]
Message-ID: <4FD66843.6000504@gmail.com> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F0020698D1354E@AUSP01VMBX24.collaborationhost.net>
On 12/06/12 01:45, H Hartley Sweeten wrote:
> On Sunday, June 10, 2012 4:58 PM, Ryan Mallon wrote:
>> On 10/06/12 22:44, Todor Colov wrote:
>>>
>>> Enable i2c support for ep9302. i2c support is needed when external RTC is
>>> used.
>>>
>>> Signed-off-by: Todor Colov <todorcolov@gmail.com>
>>
>> Thanks. Applied to ep93xx-fixes.
>
> Ryan,
>
> I'm not sure about this patch...
>
> The EDB9302 does not have a built-on external RTC connected to the I2C
> bus. The EECLK and EEDAT pins are simply routed to two headers. They are
> not connected to any I2C devices built onto the board.
>
> This patch will cause _all_ edb9302 boards to bind the ds1337 driver to the
> I2C bus but that device will only exist if a user has connected the part
> externally to the board.
>
> Just my 2 cents...
Hmm, the binding is not really a problem, since it will just fail if the
ds1337 device is not present at that i2c address. I guess the main problem
is if there are users of the edb9302 who want i2c on the headers and others
who want to use the pins as gpio. Without being able to auto-detect such
boards at runtime (which seems very unlikely) I can't think of a good
solution to this, other than it being time for me to do more DT reading :-).
I'm inclined to leave the patch in. The ep93xx doesn't have a lot of users,
so I think it is okay to tailor it a bit to the users we do have. I'm happy
to revert it, and find a better solution if this breaks someone else's
setup.
~Ryan
next prev parent reply other threads:[~2012-06-11 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 12:44 [PATCH] arm: ep93xx: Enable i2c support for ep9302 Todor Colov
2012-06-10 23:58 ` Ryan Mallon
2012-06-11 15:45 ` H Hartley Sweeten
2012-06-11 21:50 ` Ryan Mallon [this message]
2012-06-21 19:33 ` Martin Guy
2012-07-01 22:57 ` Ryan Mallon
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=4FD66843.6000504@gmail.com \
--to=rmallon@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).