[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1490691283.3177.112.camel@kernel.crashing.org>
Date: Tue, 28 Mar 2017 19:54:43 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Brendan Higgins <brendanhiggins@...gle.com>, wsa@...-dreams.de,
robh+dt@...nel.org, mark.rutland@....com, tglx@...utronix.de,
jason@...edaemon.net, marc.zyngier@....com, joel@....id.au,
vz@...ia.com, mouse@...c.ru, clg@...d.org
Cc: linux-i2c@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, openbmc@...ts.ozlabs.org
Subject: Re: [PATCH v6 3/5] i2c: aspeed: added documentation for Aspeed I2C
driver
On Mon, 2017-03-27 at 22:12 -0700, Brendan Higgins wrote:
> Added device tree binding documentation for Aspeed I2C busses.
>
> Signed-off-by: Brendan Higgins <brendanhiggins@...gle.com>
> + i2c0: i2c-bus@40 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + #interrupt-cells = <1>;
> + reg = <0x40 0x40>;
> + compatible = "aspeed,ast2400-i2c-bus";
> + 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.
> + status = "disabled";
> + interrupts = <0>;
> + interrupt-parent = <&i2c_ic>;
> + };
> +};
Powered by blists - more mailing lists