linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Aswath Govindraju <a-govindraju@ti.com>
Cc: "Lokesh Vutla" <lokeshvutla@ti.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Kishon Vijay Abraham I" <kishon@ti.com>,
	"Grygorii Strashko" <grygorii.strashko@ti.com>,
	"Aswath Govindraju" <a-govindraju@ti.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>, "Nishanth Menon" <nm@ti.com>,
	"Tero Kristo" <kristo@kernel.org>,
	linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] ARM: dts: am437x: align ti, pindir-d0-out-d1-in property with dt-shema
Date: Wed, 2 Jun 2021 18:04:12 +0530	[thread overview]
Message-ID: <20210602123416.20378-3-a-govindraju@ti.com> (raw)
In-Reply-To: <20210602123416.20378-1-a-govindraju@ti.com>

ti,pindir-d0-out-d1-in property is expected to be of type boolean.
Therefore, fix the property accordingly.

Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
---
 arch/arm/boot/dts/am43x-epos-evm.dts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/boot/dts/am43x-epos-evm.dts b/arch/arm/boot/dts/am43x-epos-evm.dts
index d717d5ada812..aae0af10a5b1 100644
--- a/arch/arm/boot/dts/am43x-epos-evm.dts
+++ b/arch/arm/boot/dts/am43x-epos-evm.dts
@@ -860,7 +860,7 @@
 	pinctrl-names = "default", "sleep";
 	pinctrl-0 = <&spi0_pins_default>;
 	pinctrl-1 = <&spi0_pins_sleep>;
-	ti,pindir-d0-out-d1-in = <1>;
+	ti,pindir-d0-out-d1-in;
 };
 
 &spi1 {
@@ -868,7 +868,7 @@
 	pinctrl-names = "default", "sleep";
 	pinctrl-0 = <&spi1_pins_default>;
 	pinctrl-1 = <&spi1_pins_sleep>;
-	ti,pindir-d0-out-d1-in = <1>;
+	ti,pindir-d0-out-d1-in;
 };
 
 &usb2_phy1 {
-- 
2.17.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-06-02 12:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 12:34 [PATCH 0/5] dt-bindings: spi: omap-spi: Convert to json-schema Aswath Govindraju
2021-06-02 12:34 ` [PATCH 1/5] ARM: dts: am335x: align ti, pindir-d0-out-d1-in property with dt-shema Aswath Govindraju
2021-06-02 12:34 ` Aswath Govindraju [this message]
2021-06-02 12:34 ` [PATCH 3/5] arm64: dts: ti: am65: " Aswath Govindraju
2021-06-07 13:40   ` [PATCH 3/5] arm64: dts: ti: am65: align ti,pindir-d0-out-d1-in " Nishanth Menon
2021-06-07 13:48     ` Aswath Govindraju
2021-06-07 20:24       ` Nishanth Menon
2021-06-02 12:34 ` [PATCH 4/5] arm64: dts: ti: k3-am642-evm: align ti, pindir-d0-out-d1-in " Aswath Govindraju
2021-06-02 12:34 ` [PATCH 5/5] dt-bindings: spi: omap-spi: Convert to json-schema Aswath Govindraju

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=20210602123416.20378-3-a-govindraju@ti.com \
    --to=a-govindraju@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=kishon@ti.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.com \
    --cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).