From: Dinh Nguyen <dinguyen@kernel.org>
To: jarkko.nikula@linux.intel.com
Cc: dinguyen@kernel.org, andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, robh+dt@kernel.org,
krzk+dt@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH 2/2] dt-bindings: i2c: dw: Add Intel's SoCFPGA I2C controller
Date: Wed, 18 May 2022 15:22:17 -0500 [thread overview]
Message-ID: <20220518202217.85803-2-dinguyen@kernel.org> (raw)
In-Reply-To: <20220518202217.85803-1-dinguyen@kernel.org>
The I2C pins on Intel's SoCFPGA platform are not connected to GPIOs and
thus cannot be recovered by the standard GPIO method.
Document the "intel,socfpga-i2c" binding.
Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
---
Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml b/Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml
index d9293c57f573..a130059e97ab 100644
--- a/Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml
+++ b/Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml
@@ -33,6 +33,8 @@ properties:
- const: snps,designware-i2c
- description: Baikal-T1 SoC System I2C controller
const: baikal,bt1-sys-i2c
+ - description: Intel's SoCFPGA I2C controller
+ const: intel,socfpga-i2c
reg:
minItems: 1
--
2.25.1
next prev parent reply other threads:[~2022-05-18 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 20:22 [PATCH 1/2] i2c: designware: introduce a custom scl recovery for SoCFPGA platforms Dinh Nguyen
2022-05-18 20:22 ` Dinh Nguyen [this message]
2022-05-21 15:16 ` [PATCH 2/2] dt-bindings: i2c: dw: Add Intel's SoCFPGA I2C controller Krzysztof Kozlowski
2022-05-19 10:20 ` [PATCH 1/2] i2c: designware: introduce a custom scl recovery for SoCFPGA platforms Andy Shevchenko
2022-05-19 12:41 ` Dinh Nguyen
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=20220518202217.85803-2-dinguyen@kernel.org \
--to=dinguyen@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=robh+dt@kernel.org \
/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).