* [PATCH] i2c: docs: Clarify I2C controller and target driver requirements
@ 2025-04-01 16:49 Arijit Kumar Das
2025-04-02 7:31 ` Wolfram Sang
0 siblings, 1 reply; 2+ messages in thread
From: Arijit Kumar Das @ 2025-04-01 16:49 UTC (permalink / raw)
To: wsa+renesas; +Cc: linux-i2c
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
From: Arijit Kumar Das <arijitkdgit.official@gmail.com>
Hi Wolfram,
I am a new contributor and am looking to gain initial experience in
contributing to the Linux kernel.
This patch improves the I2C documentation by clarifying that each I2C
controller requires separate drivers for its targets. I believe this
small addition makes the documentation clearer for new developers.
Please review and let me know if any modifications are needed.
Thanks,
Arijit
---
Documentation/i2c/summary.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/i2c/summary.rst b/Documentation/i2c/summary.rst
index 579a1c7df200..caca33aae79a 100644
--- a/Documentation/i2c/summary.rst
+++ b/Documentation/i2c/summary.rst
@@ -60,7 +60,7 @@ video-related chips.
For the example configuration in the figure above, you will need one
driver for
the I2C controller, and drivers for your I2C targets. Usually one driver for
-each target.
+each target is required for every I2C controller.
Synonyms
--------
--
2.43.0
[-- Attachment #2: 0001-Added-a-small-clarification-about-I2C-controller-I2C.patch --]
[-- Type: text/x-diff, Size: 830 bytes --]
From 6e4fddc48576f2431729ea4a385156c8c04623d1 Mon Sep 17 00:00:00 2001
From: Arijit Kumar Das <arijitkdgit.official@gmail.com>
Date: Tue, 1 Apr 2025 20:48:28 +0530
Subject: [PATCH] Added a small clarification about I2C controller & I2C
targets drivers
---
Documentation/i2c/summary.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/i2c/summary.rst b/Documentation/i2c/summary.rst
index 579a1c7df200..caca33aae79a 100644
--- a/Documentation/i2c/summary.rst
+++ b/Documentation/i2c/summary.rst
@@ -60,7 +60,7 @@ video-related chips.
For the example configuration in the figure above, you will need one driver for
the I2C controller, and drivers for your I2C targets. Usually one driver for
-each target.
+each target is required for every I2C controller.
Synonyms
--------
--
2.43.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] i2c: docs: Clarify I2C controller and target driver requirements
2025-04-01 16:49 [PATCH] i2c: docs: Clarify I2C controller and target driver requirements Arijit Kumar Das
@ 2025-04-02 7:31 ` Wolfram Sang
0 siblings, 0 replies; 2+ messages in thread
From: Wolfram Sang @ 2025-04-02 7:31 UTC (permalink / raw)
To: Arijit Kumar Das; +Cc: linux-i2c
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Hi Arijitm
> I am a new contributor and am looking to gain initial experience in
> contributing to the Linux kernel.
Welcome! Enjoy the hacking, it is fun.
> This patch improves the I2C documentation by clarifying that each I2C
> controller requires separate drivers for its targets. I believe this
> small addition makes the documentation clearer for new developers.
Frankly, I am not sure it makes something clearer because I myself don't
know what you actually mean. You only need to enable a driver for a
target once in menuconfig. If you have such targets on multiple busses,
then the driver will be reused. You just need to enable it once. Or?
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-04-02 7:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-04-01 16:49 [PATCH] i2c: docs: Clarify I2C controller and target driver requirements Arijit Kumar Das
2025-04-02 7:31 ` Wolfram Sang
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).