linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "André Hentschel" <nerv@dawncrow.de>
To: robh+dt@kernel.org, bcousson@baylibre.com, tony@atomide.com,
	linux-omap@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] ARM: dts: omap3-echo: Add ath6kl node
Date: Sat, 30 Jan 2021 13:25:14 +0100	[thread overview]
Message-ID: <20210130122514.58375-2-nerv@dawncrow.de> (raw)
In-Reply-To: <20210130122514.58375-1-nerv@dawncrow.de>

Signed-off-by: André Hentschel <nerv@dawncrow.de>
---

Attention, here I am not sure if this is supposed to work like that. The ath6kl driver needs to
be loaded as a module anyway and automatically find the right device. So this might be useful for
documentation purpose, but also might be wrong device-tree wise.

 arch/arm/boot/dts/omap3-echo.dts | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/arch/arm/boot/dts/omap3-echo.dts b/arch/arm/boot/dts/omap3-echo.dts
index 3382480d5f19..8f02ff5e7da6 100644
--- a/arch/arm/boot/dts/omap3-echo.dts
+++ b/arch/arm/boot/dts/omap3-echo.dts
@@ -606,6 +606,8 @@ &mmc2 {
 };
 
 &mmc3 {
+	#address-cells = <1>;
+	#size-cells = <0>;
 	status = "okay";
 	bus-width = <4>;
 	pinctrl-names = "default";
@@ -615,6 +617,11 @@ &mmc3 {
 	mmc-pwrseq = <&sdio_pwrseq>;
 	vmmc-supply = <&vcc3v3>;
 	vqmmc-supply = <&vcc1v8>;
+	atheros@0 {
+		compatible = "atheros,ath6kl";
+		reg = <0>;
+		bus-width = <4>;
+	};
 };
 
 &tps {
-- 
2.25.1


  reply	other threads:[~2021-01-30 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30 12:25 [PATCH 1/2] ARM: dts: omap3-echo: Update LED configuration André Hentschel
2021-01-30 12:25 ` André Hentschel [this message]
2021-03-24 12:04 ` Tony Lindgren

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=20210130122514.58375-2-nerv@dawncrow.de \
    --to=nerv@dawncrow.de \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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).