From: Dragan Simic <dsimic@manjaro.org>
To: Alex Bee <knaerzche@gmail.com>
Cc: Diederik de Haas <didi.debian@cknow.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Johan Jonker <jbx6244@gmail.com>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: [PATCH v3 1/2] arm64: dts: rockchip: Add sdmmc_ext for RK3328
Date: Sat, 13 Jul 2024 16:58:45 +0200 [thread overview]
Message-ID: <529bd79969ced12bbb5a3b1c3d5ba53c@manjaro.org> (raw)
In-Reply-To: <969642dd-fe5f-4dfd-baac-21e75e30a271@gmail.com>
Hello Alex,
On 2024-07-13 16:56, Alex Bee wrote:
> Am 13.07.24 um 16:35 schrieb Diederik de Haas:
>> Hi Dragan,
>>
>> Thanks for the reviews!
>>
>> On Saturday, 13 July 2024 15:45:12 CEST Dragan Simic wrote:
>>> Looking good to me, cross-referencing the RK3328 TRM and the
>>> downstream RK3328 SoC dtsi checks out. Though, it will remain inert
>>> in our codebase, because no supported boards use it, but that's fine,
>>> we're still improving the correctness of the RK3328 SoC dtsi.
>> Indeed. But it's hard to argue with technically correct ;-)
>
> FWIW: (upstream supported) ROC-RK3328-PC has sdio wifi connected to
> this
> controller.
Oh, it does? Good to hear, so the additions to the RK3328 SoC dtsi
shouldn't remain inert. :)
next prev parent reply other threads:[~2024-07-13 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 13:28 [PATCH v3 0/2] sdmmc/sdio/emmc improvements " Diederik de Haas
2024-07-10 13:28 ` [PATCH v3 1/2] arm64: dts: rockchip: Add sdmmc_ext " Diederik de Haas
2024-07-13 13:45 ` Dragan Simic
2024-07-13 14:35 ` Diederik de Haas
2024-07-13 14:56 ` Alex Bee
2024-07-13 14:58 ` Dragan Simic [this message]
2024-07-10 13:28 ` [PATCH v3 2/2] arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls " Diederik de Haas
2024-07-13 13:32 ` Dragan Simic
2024-07-29 20:21 ` [PATCH v3 0/2] sdmmc/sdio/emmc improvements " Heiko Stuebner
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=529bd79969ced12bbb5a3b1c3d5ba53c@manjaro.org \
--to=dsimic@manjaro.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®