From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
sukrut bellary <sukrut.bellary@gmail.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am625-sk: Add support for WL1837 module onboard
Date: Mon, 4 Dec 2023 10:38:25 +0200 [thread overview]
Message-ID: <20231204083825.GL5169@atomide.com> (raw)
In-Reply-To: <20231203140710.irc7mmwff2b5voak@observant>
* Nishanth Menon <nm@ti.com> [231203 14:07]:
> dts can remain common, the m2 is a dtso, we generate a dtbo and the
> original will be an additional dtb? I think this can work out without
> dts/dtsi duplication.
That sounds good to me, I'll take a look.
> arch/arm64/boot/dts/ti/Makefile has previous examples of the form.
OK
> I believe the issue was around the wlan firmware load itself, but i
> think the mmc-pwrseq will probably help resolve it.
Yes mmc-pwrseq makes sense.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
sukrut bellary <sukrut.bellary@gmail.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am625-sk: Add support for WL1837 module onboard
Date: Mon, 4 Dec 2023 10:38:25 +0200 [thread overview]
Message-ID: <20231204083825.GL5169@atomide.com> (raw)
In-Reply-To: <20231203140710.irc7mmwff2b5voak@observant>
* Nishanth Menon <nm@ti.com> [231203 14:07]:
> dts can remain common, the m2 is a dtso, we generate a dtbo and the
> original will be an additional dtb? I think this can work out without
> dts/dtsi duplication.
That sounds good to me, I'll take a look.
> arch/arm64/boot/dts/ti/Makefile has previous examples of the form.
OK
> I believe the issue was around the wlan firmware load itself, but i
> think the mmc-pwrseq will probably help resolve it.
Yes mmc-pwrseq makes sense.
Regards,
Tony
next prev parent reply other threads:[~2023-12-04 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 12:24 [PATCH] arm64: dts: ti: k3-am625-sk: Add support for WL1837 module onboard Tony Lindgren
2023-11-21 12:24 ` Tony Lindgren
2023-11-23 7:10 ` Nishanth Menon
2023-11-23 7:10 ` Nishanth Menon
2023-11-29 8:34 ` Tony Lindgren
2023-11-29 8:34 ` Tony Lindgren
2023-12-03 14:07 ` Nishanth Menon
2023-12-03 14:07 ` Nishanth Menon
2023-12-04 8:38 ` Tony Lindgren [this message]
2023-12-04 8:38 ` 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=20231204083825.GL5169@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nm@ti.com \
--cc=sukrut.bellary@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.