From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Nishanth Menon <nm@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Pavel Machek" <pavel@ucw.cz>,
sre@kernel.org
Subject: Re: [RFC] OMAP DT i2c aliases
Date: Mon, 02 Jun 2014 19:03:24 +0300 [thread overview]
Message-ID: <538CA04C.1070509@gmail.com> (raw)
In-Reply-To: <538C9B62.9090404@ti.com>
On 2.06.2014 18:42, Nishanth Menon wrote:
> On 06/01/2014 09:28 AM, Ivaylo Dimitrov wrote:
>> Hi,
>>
>> patch https://lkml.org/lkml/2013/10/16/744 fixes DT i2c bus ids in case
>> of deferred probe and assigns id 0,1 and 2 for i2c buses 1,2 and 3.
>> Unfortunately, this breaks Maemo userspace on N900, where board code (in
>> case of legacy boot) assigns ids 1, 2 and 3, but with DT boot ids are
>
> ughh.. missed that :(
>
>> 0,1 and 2. I've already send a patch https://lkml.org/lkml/2014/6/1/49
>> that will allow me to fix that from board .dts, but I was wondering if
>> it is the correct way, or ids should be changed in omap3.dtsi for all
>> omap devices.
>
> Should'nt we retain 0,1,2 as indexing to make this consistent for all
> SoCs?
>
>
I think this is the most sane thing, esp if the "alias replace" patch
gets accepted(thus allowing us to workaround the problems on N900 and
N9/50), however I wanted to hear from you on the matter. Esp that
indexing is different with legacy boot compared to DT boot.
next prev parent reply other threads:[~2014-06-02 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 14:28 [RFC] OMAP DT i2c aliases Ivaylo Dimitrov
2014-06-02 15:42 ` Nishanth Menon
2014-06-02 16:03 ` Ivaylo Dimitrov [this message]
2014-06-02 16:19 ` Nishanth Menon
2014-06-02 16:44 ` Ivaylo Dimitrov
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=538CA04C.1070509@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@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;
as well as URLs for NNTP newsgroup(s).