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: 10+ 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 ` [PATCH v4 1/4] i2c: busses: i2c-st: Add ST I2C controller 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 ` [PATCH v4 3/4] ARM: STi: Supply I2C configuration to STiH415 SoC Maxime COQUELIN
2013-10-10 12:33 ` Stephen GALLIMORE
2013-10-10 12:49 ` Maxime COQUELIN [this message]
2013-10-08 16:42 ` [PATCH v4 4/4] ARM: STi: Add I2C config to B2000 and B2020 boards Maxime COQUELIN
2013-10-10 9:39 ` [PATCH v4 0/4] Add I2C support to ST SoCs Maxime COQUELIN
2013-10-10 10:03 ` Wolfram Sang
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@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@st.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@st.com \
--cc=stephen.gallimore@st.com \
--cc=stuart.menefy@st.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome