From: Maxime COQUELIN <maxime.coquelin-qxv4g6HH51o@public.gmane.org>
To: Stephen GALLIMORE
<stephen.gallimore-qxv4g6HH51o@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Stuart MENEFY <stuart.menefy-qxv4g6HH51o@public.gmane.org>,
Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Gabriel FERNANDEZ
<gabriel.fernandez-qxv4g6HH51o@public.gmane.org>,
Srinivas KANDAGATLA
<srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
Subject: Re: [PATCH v4 3/4] ARM: STi: Supply I2C configuration to STiH415 SoC
Date: Thu, 10 Oct 2013 14:49:45 +0200 [thread overview]
Message-ID: <5256A269.9070809@st.com> (raw)
In-Reply-To: <A3BF01DB4A606149A4C20C4C4C808F6C5BC8A70D4E-+EwDPpWUVoThJTuQ9jeba9BPR1lH4CV8@public.gmane.org>
On 10/10/2013 02:33 PM, Stephen GALLIMORE wrote:
>> -----Original Message-----
>> From: Maxime COQUELIN [mailto:maxime.coquelin-qxv4g6HH51o@public.gmane.org]
>> Sent: 08 October 2013 17:43
>> .....
>> +
>> + i2c@fed40000 {
>> + compatible = "st,comms-ssc-i2c";
>> + reg = <0xfed40000 0x110>;
>> + interrupts = <GIC_SPI 187 IRQ_TYPE_EDGE_RISING>;
> This should specify level (high) triggered, not edge triggered, for our
> SoC integrations.
>
> Note that level triggered is the default GIC setup and was therefore
> what was being used when you specified "0" for the flags previously.
Thanks Stephen.
As discussed this morning, I agree this should be high level triggered.
This will be fixed in next revision.
>
>> + clocks = <&CLKS_ICN_REG_0>;
>> + clock-names = "ssc";
>> + clock-frequency = <400000>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pinctrl_i2c0_default>;
>> +
>> + status = "disabled";
>> + };
WARNING: multiple messages have this Message-ID (diff)
From: Maxime COQUELIN <maxime.coquelin@st.com>
To: Stephen GALLIMORE <stephen.gallimore@st.com>,
Wolfram Sang <wsa@the-dreams.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Cc: Stuart MENEFY <stuart.menefy@st.com>,
Lee Jones <lee.jones@linaro.org>,
Gabriel FERNANDEZ <gabriel.fernandez@st.com>,
Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
Subject: Re: [PATCH v4 3/4] ARM: STi: Supply I2C configuration to STiH415 SoC
Date: Thu, 10 Oct 2013 14:49:45 +0200 [thread overview]
Message-ID: <5256A269.9070809@st.com> (raw)
In-Reply-To: <A3BF01DB4A606149A4C20C4C4C808F6C5BC8A70D4E@SAFEX1MAIL1.st.com>
On 10/10/2013 02:33 PM, Stephen GALLIMORE wrote:
>> -----Original Message-----
>> From: Maxime COQUELIN [mailto:maxime.coquelin@st.com]
>> Sent: 08 October 2013 17:43
>> .....
>> +
>> + i2c@fed40000 {
>> + compatible = "st,comms-ssc-i2c";
>> + reg = <0xfed40000 0x110>;
>> + interrupts = <GIC_SPI 187 IRQ_TYPE_EDGE_RISING>;
> This should specify level (high) triggered, not edge triggered, for our
> SoC integrations.
>
> Note that level triggered is the default GIC setup and was therefore
> what was being used when you specified "0" for the flags previously.
Thanks Stephen.
As discussed this morning, I agree this should be high level triggered.
This will be fixed in next revision.
>
>> + clocks = <&CLKS_ICN_REG_0>;
>> + clock-names = "ssc";
>> + clock-frequency = <400000>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pinctrl_i2c0_default>;
>> +
>> + status = "disabled";
>> + };
next prev parent reply other threads:[~2013-10-10 12:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 16:42 [PATCH v4 0/4] Add I2C support to ST SoCs Maxime COQUELIN
2013-10-08 16:42 ` Maxime COQUELIN
2013-10-08 16:42 ` Maxime COQUELIN
2013-10-08 16:42 ` [PATCH v4 1/4] i2c: busses: i2c-st: Add ST I2C controller Maxime COQUELIN
2013-10-08 16:42 ` Maxime COQUELIN
2013-10-08 16:42 ` [PATCH v4 2/4] ARM: STi: Supply I2C configuration to STiH416 SoC Maxime COQUELIN
2013-10-08 16:42 ` Maxime COQUELIN
2013-10-08 16:42 ` [PATCH v4 3/4] ARM: STi: Supply I2C configuration to STiH415 SoC Maxime COQUELIN
2013-10-08 16:42 ` Maxime COQUELIN
2013-10-10 12:33 ` Stephen GALLIMORE
[not found] ` <A3BF01DB4A606149A4C20C4C4C808F6C5BC8A70D4E-+EwDPpWUVoThJTuQ9jeba9BPR1lH4CV8@public.gmane.org>
2013-10-10 12:49 ` Maxime COQUELIN [this message]
2013-10-10 12:49 ` Maxime COQUELIN
2013-10-08 16:42 ` [PATCH v4 4/4] ARM: STi: Add I2C config to B2000 and B2020 boards Maxime COQUELIN
2013-10-08 16:42 ` Maxime COQUELIN
[not found] ` <1381250576-7916-1-git-send-email-maxime.coquelin-qxv4g6HH51o@public.gmane.org>
2013-10-10 9:39 ` [PATCH v4 0/4] Add I2C support to ST SoCs Maxime COQUELIN
2013-10-10 9:39 ` Maxime COQUELIN
2013-10-10 9:39 ` Maxime COQUELIN
2013-10-10 10:03 ` Wolfram Sang
2013-10-10 10:03 ` Wolfram Sang
2013-10-10 13:33 ` Maxime COQUELIN
2013-10-10 13:33 ` Maxime COQUELIN
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=5256A269.9070809@st.com \
--to=maxime.coquelin-qxv4g6hh51o@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gabriel.fernandez-qxv4g6HH51o@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=srinivas.kandagatla-qxv4g6HH51o@public.gmane.org \
--cc=stephen.gallimore-qxv4g6HH51o@public.gmane.org \
--cc=stuart.menefy-qxv4g6HH51o@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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.