From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Wolfram Sang <wsa@the-dreams.de>,
Luis Oliveira <Luis.Oliveira@synopsys.com>
Cc: linux-i2c@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] i2c: designware: Don't set SCL timings and speed mode when in slave mode
Date: Thu, 19 Oct 2017 12:32:15 +0300 [thread overview]
Message-ID: <74ce49f5-8d4d-786c-cf57-24909356e5f5@linux.intel.com> (raw)
In-Reply-To: <20171005111825.kbfb4gcvq26wexnq@ninjato>
Hi Luis
On 10/05/2017 02:18 PM, Wolfram Sang wrote:
> On Wed, Aug 23, 2017 at 04:46:12PM +0300, Jarkko Nikula wrote:
>> According to data sheet SCL timing parameters and DW_IC_CON SPEED mode
>> bits are not used when operating in slave mode.
>>
>> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
>> ---
>> I've done quick testing with i2c-slave-eeprom and i2cdump over together
>> hooked busses without issues. Would like to hear tested by or comment
>> from Luis though. Patch is not urgent so can wait after vacation etc.
>
> Luis?
>
Do you have possibility test my patch it doesn't break anything?
--
Jarkko
next prev parent reply other threads:[~2017-10-19 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 13:46 [PATCH] i2c: designware: Don't set SCL timings and speed mode when in slave mode Jarkko Nikula
2017-10-05 11:18 ` Wolfram Sang
2017-10-19 9:32 ` Jarkko Nikula [this message]
2017-10-19 11:52 ` Luis Oliveira
2017-11-14 11:17 ` Jarkko Nikula
2017-11-22 11:15 ` Luis Oliveira
2017-11-22 11:37 ` Jarkko Nikula
2017-11-27 17:30 ` 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=74ce49f5-8d4d-786c-cf57-24909356e5f5@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=Luis.Oliveira@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).