From: Hsin-Yi Wang <hsinyi@chromium.org>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 1/7] arm64: dts: mt8183: jacuzzi: remove unused ddc-i2c-bus
Date: Wed, 10 Nov 2021 14:31:12 +0800 [thread overview]
Message-ID: <20211110063118.3412564-1-hsinyi@chromium.org> (raw)
EDID is read from bridge, so the ddc-i2c-bus is unused.
Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
---
arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi.dtsi b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi.dtsi
index d8826c82bcda29..8f7bf33f607da2 100644
--- a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi.dtsi
@@ -9,7 +9,6 @@ / {
panel: panel {
compatible = "auo,b116xw03";
power-supply = <&pp3300_panel>;
- ddc-i2c-bus = <&i2c4>;
backlight = <&backlight_lcd0>;
port {
--
2.34.0.rc0.344.g81b53c2807-goog
next reply other threads:[~2021-11-10 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 6:31 Hsin-Yi Wang [this message]
2021-11-10 6:31 ` [PATCH v3 2/7] arm64: dts: mt8183: Add kukui-jacuzzi-cozmo board Hsin-Yi Wang
2021-11-10 6:31 ` [PATCH v3 3/7] arm64: dts: mt8183: Add more fennel SKUs Hsin-Yi Wang
2021-11-10 6:31 ` [PATCH v3 4/7] arm64: dts: mt8183: Add kakadu sku22 Hsin-Yi Wang
2021-11-10 6:31 ` [PATCH v3 5/7] dt-bindings: arm64: dts: mediatek: Add mt8183-kukui-jacuzzi-cozmo Hsin-Yi Wang
2021-11-10 6:31 ` [PATCH v3 6/7] dt-bindings: arm64: dts: mediatek: Add more SKUs for mt8183 fennel board Hsin-Yi Wang
2021-11-10 6:31 ` [PATCH v3 7/7] dt-bindings: arm64: dts: mediatek: Add sku22 for mt8183 kakadu board Hsin-Yi Wang
2021-11-17 17:38 ` [PATCH v3 1/7] arm64: dts: mt8183: jacuzzi: remove unused ddc-i2c-bus Matthias Brugger
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=20211110063118.3412564-1-hsinyi@chromium.org \
--to=hsinyi@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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).