From: Wolfram Sang <wsa@the-dreams.de>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Alexander Sverdlin <alexander.sverdlin@nokia.com>,
Sekhar Nori <nsekhar@ti.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@kernel.org>
Subject: Re: [PATCH] i2c: davinci: Avoid zero value of CLKH
Date: Sat, 21 Jul 2018 00:18:10 +0200 [thread overview]
Message-ID: <20180720221810.67tcrphiu5xuudam@ninjato> (raw)
In-Reply-To: <0c29ccf5-4077-47a2-e7e0-c89ffcf8cb0b@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 625 bytes --]
On Fri, Jul 20, 2018 at 01:43:46PM -0500, Grygorii Strashko wrote:
>
>
> On 07/17/2018 06:57 AM, Sekhar Nori wrote:
> > On Friday 13 July 2018 08:50 PM, Alexander Sverdlin wrote:
> > > If CLKH is set to 0 I2C clock is not generated at all, so avoid this value
> > > and stretch the clock in this case.
> >
> > This must be by observation since specification does not seem to state
> > this.
>
> It will be good to know (mention) on what hw was it observed?
Some more info would also help me to decide if this is stable material
or not. Is it a bug fix or more theoretical (but still valid, of
course)?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-07-20 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 15:20 [PATCH] i2c: davinci: Avoid zero value of CLKH Alexander Sverdlin
2018-07-17 11:57 ` Sekhar Nori
2018-07-20 18:43 ` Grygorii Strashko
2018-07-20 22:18 ` Wolfram Sang [this message]
2018-07-23 18:07 ` Wolfram Sang
2018-07-24 6:17 ` Sekhar Nori
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=20180720221810.67tcrphiu5xuudam@ninjato \
--to=wsa@the-dreams.de \
--cc=alexander.sverdlin@nokia.com \
--cc=grygorii.strashko@ti.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=nsekhar@ti.com \
/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).