From: Tom Rini <trini@konsulko.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: u-boot@lists.denx.de, Jaehoon Chung <jh80.chung@samsung.com>,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 1/3] arm: mmc: Add "ti, am335-sdhci" compatible for TI's omap_hsmmc driver
Date: Mon, 7 Mar 2022 16:23:12 -0500 [thread overview]
Message-ID: <20220307212312.GG5020@bill-the-cat> (raw)
In-Reply-To: <20220218122844.2493-1-lukma@denx.de>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On Fri, Feb 18, 2022 at 01:28:41PM +0100, Lukasz Majewski wrote:
> In the Linux kernel (v5.16) for this SoC there are two separate drivers
> - namely sdhci-omap.c and omap_hsmmc.c which have separate set of
> compatibles.
>
> The U-Boot's drivers/mmc/omap_hsmmc.c driver supports both eMMC and
> SD devices - hence the compatible for SDHCI can be added.
>
> After this change the am335x DTS description can be easier ported
> from Linux kernel.
>
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-03-07 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220218122905epcas1p2a6d5a4a552cf3d65d1a9c50c3bd09120@epcas1p2.samsung.com>
2022-02-18 12:28 ` [PATCH 1/3] arm: mmc: Add "ti, am335-sdhci" compatible for TI's omap_hsmmc driver Lukasz Majewski
2022-02-18 12:28 ` [PATCH 2/3] arm: dts: Add mmc[01] aliases to am33xx.dtsi Lukasz Majewski
2022-03-07 21:23 ` Tom Rini
2022-02-18 12:28 ` [PATCH 3/3] arm: dts: Add DTS description for MMC2 am33xx devices Lukasz Majewski
2022-03-07 21:23 ` Tom Rini
2022-02-24 12:53 ` [PATCH 1/3] arm: mmc: Add "ti,am335-sdhci" compatible for TI's omap_hsmmc driver Jaehoon Chung
2022-03-03 9:28 ` Lukasz Majewski
2022-03-07 21:23 ` Tom Rini [this message]
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=20220307212312.GG5020@bill-the-cat \
--to=trini@konsulko.com \
--cc=jh80.chung@samsung.com \
--cc=lukma@denx.de \
--cc=peng.fan@nxp.com \
--cc=u-boot@lists.denx.de \
/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