All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@st.com>
To: Wolfram Sang <wsa@the-dreams.de>,
	Peter Griffin <peter.griffin@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, srinivas.kandagatla@gmail.com,
	patrice.chotard@st.com, lee.jones@linaro.org,
	linux-i2c@vger.kernel.org,
	Frederic Pillon <frederic.pillon@st.com>
Subject: Re: [PATCH] i2c: st: Implement i2c_bus_recovery_info callbacks
Date: Fri, 29 Apr 2016 13:26:16 +0200	[thread overview]
Message-ID: <572344D8.6060401@st.com> (raw)
In-Reply-To: <20160428145720.GA1541@katana>



On 04/28/2016 04:57 PM, Wolfram Sang wrote:
>> The trick is to switch to SPI mode, 9 bits words and write a 0,
>> so that 9 clock pulses are generated.
> Heh. As long as it works :) But as you said, it really needs a comment.
>
:)
I didn't faced the problem myself, but it looks good with an oscilloscope,
and a customer reported it to work.

Peter, will you resend with adding the explanations I provided as comment?

Thanks in advance,
Maxime

WARNING: multiple messages have this Message-ID (diff)
From: maxime.coquelin@st.com (Maxime Coquelin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: st: Implement i2c_bus_recovery_info callbacks
Date: Fri, 29 Apr 2016 13:26:16 +0200	[thread overview]
Message-ID: <572344D8.6060401@st.com> (raw)
In-Reply-To: <20160428145720.GA1541@katana>



On 04/28/2016 04:57 PM, Wolfram Sang wrote:
>> The trick is to switch to SPI mode, 9 bits words and write a 0,
>> so that 9 clock pulses are generated.
> Heh. As long as it works :) But as you said, it really needs a comment.
>
:)
I didn't faced the problem myself, but it looks good with an oscilloscope,
and a customer reported it to work.

Peter, will you resend with adding the explanations I provided as comment?

Thanks in advance,
Maxime

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Coquelin <maxime.coquelin@st.com>
To: Wolfram Sang <wsa@the-dreams.de>,
	Peter Griffin <peter.griffin@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <srinivas.kandagatla@gmail.com>,
	<patrice.chotard@st.com>, <lee.jones@linaro.org>,
	<linux-i2c@vger.kernel.org>,
	Frederic Pillon <frederic.pillon@st.com>
Subject: Re: [PATCH] i2c: st: Implement i2c_bus_recovery_info callbacks
Date: Fri, 29 Apr 2016 13:26:16 +0200	[thread overview]
Message-ID: <572344D8.6060401@st.com> (raw)
In-Reply-To: <20160428145720.GA1541@katana>



On 04/28/2016 04:57 PM, Wolfram Sang wrote:
>> The trick is to switch to SPI mode, 9 bits words and write a 0,
>> so that 9 clock pulses are generated.
> Heh. As long as it works :) But as you said, it really needs a comment.
>
:)
I didn't faced the problem myself, but it looks good with an oscilloscope,
and a customer reported it to work.

Peter, will you resend with adding the explanations I provided as comment?

Thanks in advance,
Maxime

  reply	other threads:[~2016-04-29 11:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 13:29 [PATCH] i2c: st: Implement i2c_bus_recovery_info callbacks Peter Griffin
2016-04-12 13:29 ` Peter Griffin
2016-04-24 21:10 ` Wolfram Sang
2016-04-24 21:10   ` Wolfram Sang
2016-04-28 13:30   ` Maxime Coquelin
2016-04-28 13:30     ` Maxime Coquelin
2016-04-28 13:30     ` Maxime Coquelin
2016-04-28 14:57     ` Wolfram Sang
2016-04-28 14:57       ` Wolfram Sang
2016-04-29 11:26       ` Maxime Coquelin [this message]
2016-04-29 11:26         ` Maxime Coquelin
2016-04-29 11:26         ` Maxime Coquelin
2016-04-29 14:03         ` Peter Griffin
2016-04-29 14:03           ` Peter Griffin
2016-05-11 15:01           ` Wolfram Sang
2016-05-11 15:01             ` Wolfram Sang
2016-05-11 15:26             ` Peter Griffin
2016-05-11 15:26               ` Peter Griffin
2016-05-11 16:22   ` Peter Griffin
2016-05-11 16:22     ` Peter Griffin

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=572344D8.6060401@st.com \
    --to=maxime.coquelin@st.com \
    --cc=frederic.pillon@st.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrice.chotard@st.com \
    --cc=peter.griffin@linaro.org \
    --cc=srinivas.kandagatla@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: 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.