From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 4/9] tegra: fdt: i2c: Add extra I2C bindings for U-Boot
Date: Wed, 07 Mar 2012 13:35:09 -0700 [thread overview]
Message-ID: <4F57C67D.9030903@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ0Xu-8cXWW=Z7mQd6UqNXT_RnRKAP-y3dvA4WtZtL1jKQ@mail.gmail.com>
On 03/06/2012 09:22 PM, Simon Glass wrote:
> Hi Stephen,
>
> On Wed, Feb 29, 2012 at 12:36 PM, Stephen Warren <swarren@nvidia.com> wrote:
>> On 02/29/2012 01:32 PM, Simon Glass wrote:
>>> Hi Stephen,
>>>
>>> On Wed, Feb 29, 2012 at 12:21 PM, Stephen Warren <swarren@nvidia.com> wrote:
>>>> On 02/29/2012 10:31 AM, Simon Glass wrote:
>>>>> Add U-Boot's peripheral clock information to the Tegra20 device tree file.
>>>>
>>>>> diff --git a/arch/arm/dts/tegra20.dtsi b/arch/arm/dts/tegra20.dtsi
>>>>
>>>>> compatible = "nvidia,tegra20-i2c";
>>>>> reg = <0x7000C000 0x100>;
>>>>> interrupts = < 70 >;
>>>>> + clocks = <&tegra_car 12>; /* PERIPH_ID_I2C1 */
>>>>> };
>>>>
>>>> The I2C modules all require 2 clocks; the one you've added in this patch
>>>> and a second reference to pll_p_out3. Can you please list both of these
>>>> here, and update the I2C binding to describe the set of clocks that it
>>>> requires. Thanks.
>>>
>>> OK - do you have a pointer to the kernel commit please? I always seem
>>> to have trouble tracking this stuff down.
>>
>> The clock stuff isn't in the kernel yet, so there's no commit to point
>> to. The commit I asked you to create would update the bindings to define
>> which clocks the I2C node needs, and would then go into U-Boot and the
>> kernel.
>
> Which binding should I update? I have had a look through Olof's trees at:
Oh, it looks like we don't have any binding documentation for the Tegra
I2C controller at all yet.
So, there's nothing in the kernel to update. Sorry about that. If you
want, you could submit a kernel patch to add such a binding, but since
there isn't one already I won't hold you to it. I see you added a rough
placeholder binding doc in the U-Boot tree in your updated U-Boot patch
which is probably fine for now if you want.
prev parent reply other threads:[~2012-03-07 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:31 [U-Boot] [PATCH v4 4/9] tegra: fdt: i2c: Add extra I2C bindings for U-Boot Simon Glass
2012-02-29 17:31 ` [U-Boot] [PATCH v4 5/9] tegra: i2c: Add I2C driver Simon Glass
2012-02-29 20:30 ` Stephen Warren
2012-03-07 4:46 ` Simon Glass
2012-03-01 7:50 ` Heiko Schocher
2012-03-01 20:29 ` Mike Frysinger
2012-03-07 4:48 ` Simon Glass
2012-02-29 17:31 ` [U-Boot] [PATCH v4 7/9] tegra: i2c: Select I2C ordering for Seaboard Simon Glass
2012-02-29 20:31 ` Stephen Warren
2012-02-29 20:21 ` [U-Boot] [PATCH v4 4/9] tegra: fdt: i2c: Add extra I2C bindings for U-Boot Stephen Warren
2012-02-29 20:32 ` Simon Glass
2012-02-29 20:36 ` Stephen Warren
2012-03-07 4:22 ` Simon Glass
2012-03-07 20:35 ` Stephen Warren [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=4F57C67D.9030903@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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