From: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
To: devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, mark.rutland@arm.com, bleung@chromium.org,
enric.balletbo@collabora.com, groeck@chromium.org,
dafna.hirschfeld@collabora.com, linux-kernel@vger.kernel.org,
helen.koike@collabora.com, ezequiel@collabora.com,
kernel@collabora.com, dafna3@gmail.com,
sebastian.reichel@collabora.com
Subject: [PATCH v5 2/2] arm64: tegra: fix nodes names under i2c-tunnel
Date: Thu, 27 Feb 2020 15:55:28 +0100 [thread overview]
Message-ID: <20200227145528.8940-2-dafna.hirschfeld@collabora.com> (raw)
In-Reply-To: <20200227145528.8940-1-dafna.hirschfeld@collabora.com>
Change the node names so that they match the class
of the device and have a unit address.
The changes are:
bq24735 -> charger@9
smart-battery -> battery@b
This also fixes the warning:
'bq24735', 'smart-battery' do not match any of the
regexes: '^.*@[0-9a-f]+$', 'pinctrl-[0-9]+'
Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
---
arch/arm64/boot/dts/nvidia/tegra132-norrin.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra132-norrin.dts b/arch/arm64/boot/dts/nvidia/tegra132-norrin.dts
index a0385a386a3f..4cd99dac541b 100644
--- a/arch/arm64/boot/dts/nvidia/tegra132-norrin.dts
+++ b/arch/arm64/boot/dts/nvidia/tegra132-norrin.dts
@@ -767,7 +767,7 @@
google,remote-bus = <0>;
- charger: bq24735 {
+ charger: charger@9 {
compatible = "ti,bq24735";
reg = <0x9>;
interrupt-parent = <&gpio>;
@@ -778,7 +778,7 @@
GPIO_ACTIVE_HIGH>;
};
- battery: smart-battery {
+ battery: battery@b {
compatible = "sbs,sbs-battery";
reg = <0xb>;
battery-name = "battery";
--
2.17.1
next prev parent reply other threads:[~2020-02-27 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 14:55 [PATCH v5 1/2] dt-bindings: i2c: cros-ec-tunnel: convert i2c-cros-ec-tunnel.txt to yaml Dafna Hirschfeld
2020-02-27 14:55 ` Dafna Hirschfeld [this message]
2020-02-27 21:23 ` Enric Balletbo Serra
2020-03-03 1:26 ` Rob Herring
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=20200227145528.8940-2-dafna.hirschfeld@collabora.com \
--to=dafna.hirschfeld@collabora.com \
--cc=bleung@chromium.org \
--cc=dafna3@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=ezequiel@collabora.com \
--cc=groeck@chromium.org \
--cc=helen.koike@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.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