linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Ludovic Desroches <ludovic.desroches@microchip.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH] i2c: document the SDA hold time binding
Date: Mon, 11 Feb 2019 14:25:15 +0100	[thread overview]
Message-ID: <20190211132515.24163-1-wsa+renesas@sang-engineering.com> (raw)

The documentation was forgotten when the feature was added.

Fixes: 4717be73c284 ("i2c: core: Parse SDA hold time from firmware")
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---

To everyone on CC: I want to confirm here that you use the value really for
t(hd:sta) and not t(hd:dat). I'd be a little confused otherwise...

 Documentation/devicetree/bindings/i2c/i2c.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/devicetree/bindings/i2c/i2c.txt b/Documentation/devicetree/bindings/i2c/i2c.txt
index 44efafdfd7f5..b7bc4c4cc2e6 100644
--- a/Documentation/devicetree/bindings/i2c/i2c.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c.txt
@@ -55,6 +55,10 @@ wants to support one of the below features, it should adapt the bindings below.
 	Number of nanoseconds the SDA signal takes to fall; t(f) in the I2C
 	specification.
 
+- i2c-sda-hold-time-ns
+	Number of nanoseconds the SDA signal needs to be held; t(hd:sta) in
+	the I2C specification.
+
 - interrupts
 	interrupts used by the device.
 
-- 
2.11.0


             reply	other threads:[~2019-02-11 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 13:25 Wolfram Sang [this message]
2019-02-11 14:40 ` [PATCH] i2c: document the SDA hold time binding Andy Shevchenko
2019-02-13 10:24 ` Ludovic Desroches
2019-02-13 10:27   ` Ludovic Desroches
2019-03-18 10:35 ` Andy Shevchenko
2019-03-18 11:22   ` Jarkko Nikula

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=20190211132515.24163-1-wsa+renesas@sang-engineering.com \
    --to=wsa+renesas@sang-engineering.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=ludovic.desroches@microchip.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).