From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 2/5] i2c: emev2: add binding documentation
Date: Tue, 7 Jul 2015 11:17:58 +0200 [thread overview]
Message-ID: <20150707091758.GF1532@katana> (raw)
In-Reply-To: <CAMuHMdU1iEn+38FY2ncDL_L_k2ytJFWH+Ek=kF42pC4pdsuAzQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
On Tue, Jul 07, 2015 at 10:41:37AM +0200, Geert Uytterhoeven wrote:
> Hi Wolfram,
>
> On Mon, Jul 6, 2015 at 11:46 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
> > diff --git a/Documentation/devicetree/bindings/i2c/i2c-emev2.txt b/Documentation/devicetree/bindings/i2c/i2c-emev2.txt
> > new file mode 100644
> > index 00000000000000..a6740066835056
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/i2c/i2c-emev2.txt
> > @@ -0,0 +1,22 @@
> > +Device tree configuration for Renesas EMEV2 IIC driver
> > +
> > +Required properties:
> > +- compatible : "renesas,iic-<soctype>". "renesas,iic-emev2" as fallback
>
> What's the "<soctype>"? Isn't that "emev2"?
Hmm, I though emev2 was the family but looking again I might be wrong.
But it is still confusing to me. EM (EMMA Mobile) is the family and EV2
is the SoC? I should probably just skip the <soctype> thing above, then
it should be good.
> > + interrupts = <0 32 IRQ_TYPE_EDGE_RISING>;
>
> Are you sure about rising edge? All other emev2 interrupts are
> IRQ_TYPE_LEVEL_HIGH.
Yes. R19UH00356EJ0800_1chip.pdf, chapter 7.1.1
64
IIC0
IIC0_INT
IIC #0 interrupt
Edge
65
IIC1
IIC1_INT
IIC #1 interrupt
Edge
Thanks,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 2/5] i2c: emev2: add binding documentation
Date: Tue, 07 Jul 2015 09:17:58 +0000 [thread overview]
Message-ID: <20150707091758.GF1532@katana> (raw)
In-Reply-To: <CAMuHMdU1iEn+38FY2ncDL_L_k2ytJFWH+Ek=kF42pC4pdsuAzQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
On Tue, Jul 07, 2015 at 10:41:37AM +0200, Geert Uytterhoeven wrote:
> Hi Wolfram,
>
> On Mon, Jul 6, 2015 at 11:46 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
> > diff --git a/Documentation/devicetree/bindings/i2c/i2c-emev2.txt b/Documentation/devicetree/bindings/i2c/i2c-emev2.txt
> > new file mode 100644
> > index 00000000000000..a6740066835056
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/i2c/i2c-emev2.txt
> > @@ -0,0 +1,22 @@
> > +Device tree configuration for Renesas EMEV2 IIC driver
> > +
> > +Required properties:
> > +- compatible : "renesas,iic-<soctype>". "renesas,iic-emev2" as fallback
>
> What's the "<soctype>"? Isn't that "emev2"?
Hmm, I though emev2 was the family but looking again I might be wrong.
But it is still confusing to me. EM (EMMA Mobile) is the family and EV2
is the SoC? I should probably just skip the <soctype> thing above, then
it should be good.
> > + interrupts = <0 32 IRQ_TYPE_EDGE_RISING>;
>
> Are you sure about rising edge? All other emev2 interrupts are
> IRQ_TYPE_LEVEL_HIGH.
Yes. R19UH00356EJ0800_1chip.pdf, chapter 7.1.1
64
IIC0
IIC0_INT
IIC #0 interrupt
Edge
65
IIC1
IIC1_INT
IIC #1 interrupt
Edge
Thanks,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-07 9:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 21:46 [PATCH 0/5] enable I2C on Renesas EMEV2 and KZM9D board Wolfram Sang
2015-07-06 21:46 ` Wolfram Sang
2015-07-06 21:46 ` [PATCH 1/5] clk: shmobile: emev2: deassert reset for IIC0/1 Wolfram Sang
2015-07-06 21:46 ` Wolfram Sang
2015-07-06 21:57 ` Stephen Boyd
2015-07-06 21:57 ` Stephen Boyd
2015-07-06 21:46 ` [PATCH 2/5] i2c: emev2: add binding documentation Wolfram Sang
2015-07-06 21:46 ` Wolfram Sang
2015-07-07 8:41 ` Geert Uytterhoeven
2015-07-07 8:41 ` Geert Uytterhoeven
2015-07-07 9:17 ` Wolfram Sang [this message]
2015-07-07 9:17 ` Wolfram Sang
2015-07-07 9:22 ` Geert Uytterhoeven
2015-07-07 9:22 ` Geert Uytterhoeven
2015-07-07 17:26 ` Laurent Pinchart
2015-07-07 17:26 ` Laurent Pinchart
2015-07-07 19:43 ` Wolfram Sang
2015-07-07 19:43 ` Wolfram Sang
2015-07-07 19:47 ` Laurent Pinchart
2015-07-07 19:47 ` Laurent Pinchart
2015-07-07 19:53 ` Wolfram Sang
2015-07-07 19:53 ` Wolfram Sang
2015-07-09 0:35 ` Laurent Pinchart
2015-07-09 0:35 ` Laurent Pinchart
2015-07-09 15:20 ` Wolfram Sang
2015-07-09 15:20 ` Wolfram Sang
2015-07-06 21:46 ` [PATCH 4/5] ARM: shmobile: emev2: add IIC cores to dtsi Wolfram Sang
2015-07-06 21:46 ` Wolfram Sang
[not found] ` <1436219188-4325-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-07-06 21:46 ` [PATCH 3/5] i2c: emev2: add driver Wolfram Sang
2015-07-06 21:46 ` Wolfram Sang
2015-07-07 18:40 ` Laurent Pinchart
2015-07-07 18:40 ` Laurent Pinchart
2015-07-07 19:49 ` Wolfram Sang
2015-07-07 19:49 ` Wolfram Sang
2015-07-06 21:46 ` [PATCH 5/5] ARM: shmobile: emev2: kzm9d: enable IIC busses Wolfram Sang
2015-07-06 21:46 ` Wolfram Sang
2015-07-07 8:38 ` [PATCH 0/5] enable I2C on Renesas EMEV2 and KZM9D board Geert Uytterhoeven
2015-07-07 8:38 ` Geert Uytterhoeven
[not found] ` <CAMuHMdUwivjTgj-nOKnHhmmU2po0JMPDhHqW6z7ngiO-D+a6iA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-07 9:10 ` Wolfram Sang
2015-07-07 9:10 ` Wolfram Sang
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=20150707091758.GF1532@katana \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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.