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:44:05 +0300 [thread overview]
Message-ID: <538CA9D5.1070506@gmail.com> (raw)
In-Reply-To: <538CA422.8000504@ti.com>
On 2.06.2014 19:19, Nishanth Menon wrote:
>
> I think that slipped my check list unfortunately. :( But then, if we
> think that it is just n900 that is impacted, then I wonder if we can
> override the alias? just wondering..
>
That https://lkml.org/lkml/2014/6/1/49 patch will allow such override, I
tested it on N900 with Fremantle and it works fine. Ofc I had to add
aliases {
i2c1 = &i2c1;
i2c2 = &i2c2;
i2c3 = &i2c3;
};
to omap3-n900.dts (while keeping omap3.dtsi intact) for it to work.
I checked in some Nemo N9/N950 adaptation kernel and it seems those will
be broken too(and I bet it is the same in stock Nokia N9/50 kernels):
static void __init rm680_i2c_init(void)
{
omap3_pmic_get_config(&rm680_twl_data, TWL_COMMON_PDATA_USB,
TWL_COMMON_REGULATOR_VDAC |
TWL_COMMON_REGULATOR_VPLL2);
omap_pmic_init(1, 2900, "twl5031", INT_34XX_SYS_NIRQ, &rm680_twl_data);
omap_register_i2c_bus(2, 400, rm696_peripherals_i2c_board_info_2,
ARRAY_SIZE(rm696_peripherals_i2c_board_info_2));
omap_register_i2c_bus(3, 400, rm696_peripherals_i2c_board_info_3,
ARRAY_SIZE(rm696_peripherals_i2c_board_info_3));
}
Again 1,2 and 3 for bus indexes just like on N900.
Anyway, I am fine with the alias override. If the patch makes it to the
upstream :)
Regards,
Ivo
prev parent reply other threads:[~2014-06-02 16:44 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
2014-06-02 16:19 ` Nishanth Menon
2014-06-02 16:44 ` Ivaylo Dimitrov [this message]
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=538CA9D5.1070506@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).