[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFd5g45gYTEtjAAaFoF3Jm6NBfbdyHtnjE6-vxDyhDfLX9nLNg@mail.gmail.com>
Date: Wed, 29 Mar 2017 03:25:51 -0700
From: Brendan Higgins <brendanhiggins@...gle.com>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: Wolfram Sang <wsa@...-dreams.de>, robh+dt@...nel.org,
mark.rutland@....com, tglx@...utronix.de, jason@...edaemon.net,
Marc Zyngier <marc.zyngier@....com>,
Joel Stanley <joel@....id.au>,
Vladimir Zapolskiy <vz@...ia.com>,
Kachalov Anton <mouse@...c.ru>,
Cédric Le Goater <clg@...d.org>,
linux-i2c@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
OpenBMC Maillist <openbmc@...ts.ozlabs.org>
Subject: Re: [PATCH v6 3/5] i2c: aspeed: added documentation for Aspeed I2C driver
>> + bus = <0>;
>> + clocks = <&clk_apb>;
>> + clock-frequency = <100000>;
>
> For busses it's more traditional to make this "bus-frequency" but
> that's a nit and Linux/fdt has not respected that tradition terribly
> well. If you respin, it might be work changing.
>
> The clock-frequency tends to be the frequency of the controller itself.
Ah, okay. I will change this on the next revision.
Powered by blists - more mailing lists