From: Manish Varma <varmam@google.com>
To: Wolfram Sang <wsa@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@android.com,
Manish Varma <varmam@google.com>
Subject: [PATCH v1 0/2] Override device name using DT "dev-name" property
Date: Wed, 7 Apr 2021 11:50:37 -0700 [thread overview]
Message-ID: <20210407185039.621248-1-varmam@google.com> (raw)
Currently I2C device names are assigned dynamically unless they are
instantiated through ACPI, this names are based on adapter_id and
device_address. While device_address will remain constant for a given
device, the adapter_id may vary across different systems and hence,
overall, the device name won't be unique for the same I2C device.
Changes here addresses this problem by introducing an optional device
tree property "dev-name", which will be used to set the device name,
if present, instead of following <adapter_id>-<device_addr> convention.
Manish Varma (2):
dt-bindings: i2c: add "dev-name" property to assign specific device
name
i2c: use "dev-name" device tree property to override device name
Documentation/devicetree/bindings/i2c/i2c.txt | 5 +++++
drivers/i2c/i2c-core-of.c | 2 ++
2 files changed, 7 insertions(+)
--
2.31.1.295.g9ea45b61b8-goog
next reply other threads:[~2021-04-07 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 18:50 Manish Varma [this message]
2021-04-07 18:50 ` [PATCH v1 1/2] dt-bindings: i2c: add "dev-name" property to assign specific device name Manish Varma
2021-04-09 18:34 ` Rob Herring
2021-04-19 23:21 ` Manish Varma
2021-04-07 18:50 ` [PATCH v1 2/2] i2c: use "dev-name" device tree property to override " Manish Varma
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=20210407185039.621248-1-varmam@google.com \
--to=varmam@google.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wsa@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).