From: Sricharan R <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] OMAP5: I2C: Enable i2c5 clocks
Date: Tue, 9 Apr 2013 12:01:56 +0530 [thread overview]
Message-ID: <5163B5DC.2020904@ti.com> (raw)
In-Reply-To: <51628F66.7010406@mm-sol.com>
Hi Lubomir,
On Monday 08 April 2013 03:05 PM, Lubomir Popov wrote:
> Hi Sricharan,
>
> On 08/04/13 09:09, Sricharan R wrote:
>> On Thursday 04 April 2013 09:22 PM, Lubomir Popov wrote:
>>> V2 fixes line wrap issue of the patch itself.
>>>
>>> I2C5 is used on all known OMAP5 hardware platforms, therefore enable.
>>>
>>> Signed-off-by: Lubomir Popov <lpopov@mm-sol.com>
>>>
>>> ---
>>> arch/arm/cpu/armv7/omap5/hw_data.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/arch/arm/cpu/armv7/omap5/hw_data.c b/arch/arm/cpu/armv7/omap5/hw_data.c
>>> index e5e41fd..5698876 100644
>>> --- a/arch/arm/cpu/armv7/omap5/hw_data.c
>>> +++ b/arch/arm/cpu/armv7/omap5/hw_data.c
>>> @@ -412,6 +412,7 @@ void enable_basic_uboot_clocks(void)
>>> (*prcm)->cm_l4per_i2c2_clkctrl,
>>> (*prcm)->cm_l4per_i2c3_clkctrl,
>>> (*prcm)->cm_l4per_i2c4_clkctrl,
>>> + (*prcm)->cm_l4per_i2c5_clkctrl,
>>
>> This is fine.
>> Can you also mention what device is connected on them ? and
>> how you are using it ?
>>
>> Also can you add these in a series.
>>
>> Regards,
>> Sricharan
>>
>
> On our board we have an I/O expander on I2C5 - the same chip that is used on
> the TI sEVM (the handset) and uEVM (the PandaBoard5) platforms (on both of
> which it is also connected to I2C5). Therefore it seems reasonable to have
> I2C5 enabled in the mainline. This requires that the base address is defined,
> and that I2C_BUS_MAX is set to 5 (please see related patches).
>
> I shall do make a new series on I2C5 support.
>
> One more thing I would like to clarify to myself: in your patch series of
> Apr. 1 you rename the omap5_evm to omap5_uevm. On the other hand, uEVM was
> the TI-internal name for the PandaBoard5, and the evm was known as sEVM.
> Doesn't this cause confusion? After all, these are two quite different
> hardware platforms.
>
Thanks for the explanation.
It would good to have the reasoning in the original commit log.
For the next one,Tom already answered this. So uEVM is the and also
the only official.
Regards,
Sricharan
prev parent reply other threads:[~2013-04-09 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 15:52 [U-Boot] [PATCH v2] OMAP5: I2C: Enable i2c5 clocks Lubomir Popov
2013-04-08 6:09 ` Sricharan R
2013-04-08 9:35 ` Lubomir Popov
2013-04-08 12:34 ` Tom Rini
2013-04-09 6:31 ` Sricharan R [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=5163B5DC.2020904@ti.com \
--to=r.sricharan@ti.com \
--cc=u-boot@lists.denx.de \
/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