All of lore.kernel.org
 help / color / mirror / Atom feed
From: ipaton0@gmail.com (Iain Paton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: imx6: add new board RIoTboard
Date: Thu, 08 May 2014 20:27:55 +0100	[thread overview]
Message-ID: <536BDABB.7090101@gmail.com> (raw)
In-Reply-To: <1399570376.88508577@f371.i.mail.ru>

On 08/05/14 18:32, Alexander Shiyan wrote:
> Thu, 08 May 2014 18:12:02 +0100 ?? Iain Paton <ipaton0@gmail.com>:
>> +&aips2 {
>> +        i2c4: i2c at 021f8000 {
>> +                #address-cells = <1>;
>> +                #size-cells = <0>;
>> +                compatible = "fsl,imx1-i2c";
> 
> Are you sure about use "fsl,imx1-i2c" instead of  "fsl,imx21-i2c"?
> In any case you should add "fsl-imx6dl-i2c" as first compatible string.
> The rest looks good.

Sure?  No.  However that's what currently exists in imx6dl.dtsi for i2c4.

looking at the other i2c interfaces in imx6qdl.dtsi, they're using
fsl,imx6q-i2c as the first compatible string. So I think I should use
either fsl,imx6dl-i2c or fsl,imx6q-i2c. 
What's the difference between that and your suggested fsl-imx6dl-i2c?
If we assume can assume the i2c4 block is functionally identical to
i2c[123] then shouldn't I use an identical compatible string?

The driver has the following compatible strings:
fsl,imx1-i2c
fsl,imx21-i2c
fsl,vf610-i2c

the difference between imx1-i2c and imx21-i2c seems to be an added delay
before generating the stop bit to workaround a hardware bug.

As it seems likely I'm the first to be trying to enable i2c4 I'd want to
check that the hardware bug doesn't apply here and that there's no 
negative effect. 
I think you're probably correct and I should change it, but I'll do the 
tests anyway and post the series if I don't see any problems.

Thanks,
Iain

  reply	other threads:[~2014-05-08 19:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 22:03 [RFC PATCH] ARM: dts: imx6: add new board RIoTboard Iain Paton
2014-05-08  2:27 ` Fabio Estevam
2014-05-08  9:10   ` Iain Paton
2014-05-08  5:41 ` Shawn Guo
2014-05-08  9:09   ` Iain Paton
2014-05-08  9:13   ` [PATCH v2] " Iain Paton
2014-05-08 13:45     ` Fabio Estevam
2014-05-08 13:54       ` Alexander Shiyan
2014-05-08 14:36       ` Iain Paton
2014-05-08 14:50         ` Alexander Shiyan
2014-05-08 17:12           ` Iain Paton
2014-05-08 17:32             ` Alexander Shiyan
2014-05-08 19:27               ` Iain Paton [this message]
2014-05-08 19:37                 ` Alexander Shiyan
2014-05-09  2:19             ` Shawn Guo
2014-05-09  3:09     ` Shawn Guo
2014-05-09  7:48       ` Iain Paton
2014-05-09 12:08         ` Shawn Guo
2014-05-09 14:16           ` Iain Paton
2014-05-09 14:21             ` Shawn Guo
2014-05-09 15:01               ` [PATCH v3 1/2] ARM: dts: imx6: i2c4 cleanup Iain Paton
2014-05-09 15:30                 ` Fabio Estevam
2014-05-10  6:28                 ` Shawn Guo
2014-05-09 15:02               ` [PATCH v3 2/2] ARM: dts: imx6: add new board RIoTboard Iain Paton
2014-05-09 15:31                 ` Fabio Estevam
2014-05-10  6:28                 ` Shawn Guo

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=536BDABB.7090101@gmail.com \
    --to=ipaton0@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.