Re: [PATCH v4 3/3] powerpc: doc/dts-bindings: update doc of FSL I2C bindings

On Tue, Feb 9, 2010 at 12:23 PM, Wolfgang Grandegger [off-list ref] wr=
ote:

Wolfgang Grandegger wrote:

quoted

Hi Grant,

Grant Likely wrote:

quoted

On Thu, Jan 28, 2010 at 6:25 AM, Wolfgang Grandegger <wg@grandegger.com=

wrote:

quoted

quoted

quoted

From: Wolfgang Grandegger <redacted>

This patch adds the MPC5121 to the list of supported devices,
enhances the doc of the "clock-frequency" property and removes
the obsolete "cell-index" property from the example nodes.
Furthermore and example for the MPC5121 has been added.

Signed-off-by: Wolfgang Grandegger <redacted>

Thanks Wolfgang. =A0Comments below.

quoted

---
=A0Documentation/powerpc/dts-bindings/fsl/i2c.txt | =A0 30 +++++++++++=

++++++++----

quoted

quoted

quoted

=A01 files changed, 24 insertions(+), 6 deletions(-)

diff --git a/Documentation/powerpc/dts-bindings/fsl/i2c.txt b/Document=

ation/powerpc/dts-bindings/fsl/i2c.txt

quoted

quoted

quoted

index b6d2e21..2f62dae 100644

--- a/Documentation/powerpc/dts-bindings/fsl/i2c.txt
+++ b/Documentation/powerpc/dts-bindings/fsl/i2c.txt

@@ -9,8 +9,9 @@ Recommended properties :

=A0- compatible : compatibility list with 2 entries, the first should
=A0 =A0be "fsl,CHIP-i2c" where CHIP is the name of a compatible proces=

sor,

quoted

quoted

quoted

- =A0 e.g. mpc8313, mpc8543, mpc8544, mpc5200 or mpc5200b. The second =

one

quoted

quoted

quoted

- =A0 should be "fsl-i2c".
+ =A0 e.g. mpc8313, mpc8543, mpc8544, mpc5121, mpc5200 or mpc5200b. Th=

e

quoted

quoted

quoted

+ =A0 second one should be "fsl-i2c". For the mpc5121, an additional n=

ode

quoted

quoted

quoted

+ =A0 "fsl,mpc5121-i2c-ctrl" is required as shown in the example below=

.

quoted

quoted

While you're editing this line; drop the requirement for the second
value to be 'fsl-i2c'. =A0We don't use it anymore, and only preserve it
for backwards compatibility with old trees.

OK.

quoted

quoted

=A0- interrupts : <a b> where a is the interrupt number and b is a
=A0 =A0field that represents an encoding of the sense and level
=A0 =A0information for the interrupt. =A0This should be encoded based =

on

quoted

quoted

quoted

@@ -20,29 +21,46 @@ Recommended properties :

=A0 =A0services interrupts for this device.
=A0- fsl,preserve-clocking : boolean; if defined, the clock settings
=A0 =A0from the bootloader are preserved (not touched).
- - clock-frequency : desired I2C bus clock frequency in Hz.
+ - clock-frequency : desired I2C bus clock frequency in Hz. =A0If thi=

s

quoted

quoted

quoted

+ =A0 property and "fsl,preserve-clocking" is not defined, a safe fixe=

d

quoted

quoted

quoted

+ =A0 clock divider value is used (resulting in a small clock frequenc=

y).

quoted

quoted

Nah, leave this as is. =A0Don't make it sound like omitting both
properties is a valid option. =A0The driver may (and should!) handle th=

e

quoted

quoted

situation gracefully, but that fact does not need to be documented.

The safe value is not a good choice, indeed. Then it will also change
MPC_I2C_CLOCK_SAFE to MPC_I2C_CLOCK_LEGACY in i2c-mpc.c.

I will also fix the other issues you commented on.

And I will also remove the "device_type" line from:

=A0-------------
=A0Required properties :

=A0- device_type : Should be "i2c"
=A0- reg : Offset and length of the register set for the device

Yes, please.

Hmmm.  compatible should also be in the 'required properties' section.

Thanks,
g.