From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: "Wolfram Sang" <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Yehuda Yitschak" <yehuday@marvell.com>,
"Jason Cooper" <jason@lakedaemon.net>,
"Antoine Tenart" <antoine.tenart@free-electrons.com>,
"Omri Itach" <omrii@marvell.com>,
"Nadav Haklai" <nadavh@marvell.com>,
"Shadi Ammouri" <shadi@marvell.com>,
"Igal Liberman" <igall@marvell.com>,
"Miquèl Raynal" <miquel.raynal@free-electrons.com>,
"Marcin Wojtas" <mw@semihalf.com>,
"Hanna Hawa" <hannah@marvell.com>,
linux-arm-kernel@lists.infradead.org,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v3 2/2] i2c: mv64xxx: Fix clock resource by adding an optional bus clock
Date: Fri, 12 Jan 2018 12:15:26 +0100 [thread overview]
Message-ID: <87wp0n5nw1.fsf@free-electrons.com> (raw)
In-Reply-To: <20180112105434.juefp2apuber3zti@flea.lan> (Maxime Ripard's message of "Fri, 12 Jan 2018 11:54:34 +0100")
Hi Maxime,
On ven., janv. 12 2018, Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> Hi,
>
> On Fri, Jan 12, 2018 at 11:39:56AM +0100, Gregory CLEMENT wrote:
>> On Armada 7K/8K we need to explicitly enable the bus clock. The bus clock
>> is optional because not all the SoCs need them but at least for Armada
>> 7K/8K it is actually mandatory.
>>
>> The binding documentation is updating accordingly.
>>
>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> ---
>> .../devicetree/bindings/i2c/i2c-mv64xxx.txt | 20 ++++++++++++++++++++
>> drivers/i2c/busses/i2c-mv64xxx.c | 12 +++++++++++-
>> 2 files changed, 31 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt b/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> index 5c30026921ae..3d76bb19492f 100644
>> --- a/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> +++ b/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> @@ -25,6 +25,15 @@ default frequency is 100kHz
>> whenever you're using the "allwinner,sun6i-a31-i2c"
>> compatible.
>>
>> + - clocks: : pointers to the reference clocks for this device, the
>> + first one is the one used for the clock on the i2c bus,
>> + the second one is the clock used for the functional part
>> + of the controller
>
> This documentation is confusing, as usually the functional clock is
> the clock driving the bus, as opposed to the interface clock clocking
> the bus interface.
I don't find it less confusing, for my point of view the interface of a
bus is the lines interfacing the bus with the devices on this bus. But I
don't mind modifying it, as I clearly state that the first clock is the
one used to generate the clock of the i2c bus, so we can change the
name.
>
>> + - clock-names : names of used clocks, mandatory if the second clock is
>> + used, the name must be "core", and "axi" (the latter is
>> + only for Armada 7K/8K).
>> +
>
> Are you sure the i2c controller is on the AXI bus? It seems more
> likely to be on an APB bus.
No I am not sure :)
Actually I don't have this information, so lets call it "reg" for
register clock.
Gregory
>
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] i2c: mv64xxx: Fix clock resource by adding an optional bus clock
Date: Fri, 12 Jan 2018 12:15:26 +0100 [thread overview]
Message-ID: <87wp0n5nw1.fsf@free-electrons.com> (raw)
In-Reply-To: <20180112105434.juefp2apuber3zti@flea.lan> (Maxime Ripard's message of "Fri, 12 Jan 2018 11:54:34 +0100")
Hi Maxime,
On ven., janv. 12 2018, Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> Hi,
>
> On Fri, Jan 12, 2018 at 11:39:56AM +0100, Gregory CLEMENT wrote:
>> On Armada 7K/8K we need to explicitly enable the bus clock. The bus clock
>> is optional because not all the SoCs need them but at least for Armada
>> 7K/8K it is actually mandatory.
>>
>> The binding documentation is updating accordingly.
>>
>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> ---
>> .../devicetree/bindings/i2c/i2c-mv64xxx.txt | 20 ++++++++++++++++++++
>> drivers/i2c/busses/i2c-mv64xxx.c | 12 +++++++++++-
>> 2 files changed, 31 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt b/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> index 5c30026921ae..3d76bb19492f 100644
>> --- a/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> +++ b/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> @@ -25,6 +25,15 @@ default frequency is 100kHz
>> whenever you're using the "allwinner,sun6i-a31-i2c"
>> compatible.
>>
>> + - clocks: : pointers to the reference clocks for this device, the
>> + first one is the one used for the clock on the i2c bus,
>> + the second one is the clock used for the functional part
>> + of the controller
>
> This documentation is confusing, as usually the functional clock is
> the clock driving the bus, as opposed to the interface clock clocking
> the bus interface.
I don't find it less confusing, for my point of view the interface of a
bus is the lines interfacing the bus with the devices on this bus. But I
don't mind modifying it, as I clearly state that the first clock is the
one used to generate the clock of the i2c bus, so we can change the
name.
>
>> + - clock-names : names of used clocks, mandatory if the second clock is
>> + used, the name must be "core", and "axi" (the latter is
>> + only for Armada 7K/8K).
>> +
>
> Are you sure the i2c controller is on the AXI bus? It seems more
> likely to be on an APB bus.
No I am not sure :)
Actually I don't have this information, so lets call it "reg" for
register clock.
Gregory
>
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2018-01-12 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 10:39 [PATCH v3 0/2] i2c: mv64xxx: Fix clock resource for Armada 7K/8K Gregory CLEMENT
2018-01-12 10:39 ` Gregory CLEMENT
2018-01-12 10:39 ` [PATCH v3 1/2] i2c: mv64xxx: Remove useless test before clk_disable_unprepare Gregory CLEMENT
2018-01-12 10:39 ` Gregory CLEMENT
2018-01-12 10:39 ` [PATCH v3 2/2] i2c: mv64xxx: Fix clock resource by adding an optional bus clock Gregory CLEMENT
2018-01-12 10:39 ` Gregory CLEMENT
2018-01-12 10:54 ` Maxime Ripard
2018-01-12 10:54 ` Maxime Ripard
2018-01-12 11:15 ` Gregory CLEMENT [this message]
2018-01-12 11:15 ` Gregory CLEMENT
2018-01-15 17:19 ` Wolfram Sang
2018-01-15 17:19 ` Wolfram Sang
2018-01-16 14:40 ` Gregory CLEMENT
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=87wp0n5nw1.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@free-electrons.com \
--cc=hannah@marvell.com \
--cc=igall@marvell.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=miquel.raynal@free-electrons.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=omrii@marvell.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shadi@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wsa@the-dreams.de \
--cc=yehuday@marvell.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.