From: Geert Uytterhoeven <geert@linux-m68k.org> To: Wolfram Sang <wsa@the-dreams.de> 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 08:41:37 +0000 [thread overview] Message-ID: <CAMuHMdU1iEn+38FY2ncDL_L_k2ytJFWH+Ek=kF42pC4pdsuAzQ@mail.gmail.com> (raw) In-Reply-To: <1436219188-4325-3-git-send-email-wsa@the-dreams.de> 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"? > +- reg : address start and address range size of device > +- interrupts : 1 interrupt > +- clocks : phandle to the IP core SCLK > +- clock-names : must be "sclk" > +- #address-cells : should be <1> > +- #size-cells : should be <0> > + > +Example: > + > + iic0: i2c@e0070000 { > + #address-cells = <1>; > + #size-cells = <0>; > + compatible = "renesas,iic-emev2"; > + reg = <0xe0070000 0x28>; > + interrupts = <0 32 IRQ_TYPE_EDGE_RISING>; Are you sure about rising edge? All other emev2 interrupts are IRQ_TYPE_LEVEL_HIGH. > + clocks = <&iic0_sclk>; > + clock-names = "sclk"; > + }; Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: Wolfram Sang <wsa@the-dreams.de> 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 10:41:37 +0200 [thread overview] Message-ID: <CAMuHMdU1iEn+38FY2ncDL_L_k2ytJFWH+Ek=kF42pC4pdsuAzQ@mail.gmail.com> (raw) In-Reply-To: <1436219188-4325-3-git-send-email-wsa@the-dreams.de> 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"? > +- reg : address start and address range size of device > +- interrupts : 1 interrupt > +- clocks : phandle to the IP core SCLK > +- clock-names : must be "sclk" > +- #address-cells : should be <1> > +- #size-cells : should be <0> > + > +Example: > + > + iic0: i2c@e0070000 { > + #address-cells = <1>; > + #size-cells = <0>; > + compatible = "renesas,iic-emev2"; > + reg = <0xe0070000 0x28>; > + interrupts = <0 32 IRQ_TYPE_EDGE_RISING>; Are you sure about rising edge? All other emev2 interrupts are IRQ_TYPE_LEVEL_HIGH. > + clocks = <&iic0_sclk>; > + clock-names = "sclk"; > + }; Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
next prev parent reply other threads:[~2015-07-07 8:41 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 [this message] 2015-07-07 8:41 ` Geert Uytterhoeven 2015-07-07 9:17 ` Wolfram Sang 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='CAMuHMdU1iEn+38FY2ncDL_L_k2ytJFWH+Ek=kF42pC4pdsuAzQ@mail.gmail.com' \ --to=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 \ --cc=wsa@the-dreams.de \ /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: linkBe 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.