U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Marek Vasut <marek.vasut@mailbox.org>, Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, Paul Barker <paul.barker.ct@bp.renesas.com>,
	Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 4/8] env: Rename SYS_MMC_ENV_DEV to ENV_SDMMC_DEVICE_INDEX
Date: Wed, 26 Mar 2025 10:22:34 +0100	[thread overview]
Message-ID: <d9382933-70f2-4c3c-abf2-4fd711fbfc4f@cherry.de> (raw)
In-Reply-To: <d576535e-f8d0-4ae7-b8b7-f4316535a6ee@mailbox.org>

Hi Marek,

On 3/26/25 2:37 AM, Marek Vasut wrote:
> On 3/26/25 1:15 AM, Tom Rini wrote:
>> On Wed, Mar 26, 2025 at 12:02:08AM +0100, Marek Vasut wrote:
>>> On 3/24/25 1:39 PM, Quentin Schulz wrote:
>>>> Hi Marek,
>>>
>>> Hi,
>>>
>>>> On 3/22/25 10:55 PM, Marek Vasut wrote:
>>>>> Rename the variable and add ENV_ prefix, so that all configuration
>>>>> options which are related to environment would have an CONFIG_ENV_
>>>>> prefix. No functional change.
>>>>>
>>>>> Use ENV_SDMMC_DEVICE_INDEX to clarify this is the SD/MMC device
>>>>> index, a number, as enumerated by U-Boot. Update the help text
>>>>> accordingly.
>>>>>
>>>>
>>>> I disagree with this part of the rename (MMC->SDMMC), our drivers all
>>>> are using mmc (env/mmc.*, drivers/mmc/*, cmd/mmc.c, ...) for both SD 
>>>> and
>>>> MMC. We also have ENV_IS_IN_MMC which is for both. I don't think it's
>>>> worth the confusion.
>>>
>>> My main problem is, that it is confusing to call everything _mmc_ 
>>> even if
>>> most of it also applies to SD . There is no way to discern parts 
>>> which are
>>> MMC specific from parts which are common to SD and MMC now.
>>
>> Do we have support for anything using the MMC part of the standard that
>> is not storage? I certainly agree it's confusingly named atm, but I
>> think changing some parts but not other parts will make it worse, not
>> better.
> That's not what I am concerned about. What I am concerned about is that 
> we are talking about partitions, and only eMMC supports HW partitions, 
> but both SD and MMC support SW partitions . So we should refer to 
> CONFIG_..._SDMMC_..._SW_PARTITION here when talking about SW 
> partitions , but CONFIG_..._MMC_..._HW_PARTITION when talking about eMMC 
> HW partitions. Currently we are missing the two and it yields a horrid 
> confusion. That is in fact what prompted this series.

But the controllers handling SD cards or eMMC are both called mmc in 
device tree and in U-Boot (see mmc command). So for me, MMC covers both. 
As a matter of fact, the mmc command also handles the boot partition 
that is specific to eMMC.

Quite interestingly, the MMC (MultiMediaCard) Wikipedia page starts with

"Not to be confused with SD card or eMMC" and then the first sentence in 
the history section is "The latest version of the eMMC standard", c.f. 
https://en.wikipedia.org/wiki/MultiMediaCard

So essentially, I'm wondering:
- if boot partitions are specific to eMMC and not simpy MMC (and are not 
part of SD card). I know eMMC has a separate standard than MMC.
- if there are other things than eMMC (and SD cards) that are supported 
by the MMC subsystem (outside of the embedded world). It seems like this 
is taking the MMC = eMMC shortcut that I'm not sure is correct?

To add to the confusion, Rockchip often has MMC controllers named SDMMC 
(and their use varies depending on the SoC, sometimes for SD, sometimes 
for eMMC, sometimes for SDIO).

Cheers,
Quentin

  reply	other threads:[~2025-03-26  9:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 21:55 [PATCH 1/8] env: Rename OVERWRITE_ETHADDR_ONCE to ENV_OVERWRITE_ETHADDR_ONCE Marek Vasut
2025-03-22 21:55 ` [PATCH 2/8] env: Rename SYS_REDUNDAND_ENVIRONMENT to ENV_REDUNDAND_ENVIRONMENT Marek Vasut
2025-03-24 12:33   ` Quentin Schulz
2025-03-24 22:52     ` Marek Vasut
2025-03-25  9:02       ` Quentin Schulz
2025-03-25 17:02         ` Tom Rini
2025-03-22 21:55 ` [PATCH 3/8] env: Rename SYS_RELOC_GD_ENV_ADDR to ENV_RELOC_GD_ENV_ADDR Marek Vasut
2025-03-25 17:02   ` Tom Rini
2025-03-22 21:55 ` [PATCH 4/8] env: Rename SYS_MMC_ENV_DEV to ENV_SDMMC_DEVICE_INDEX Marek Vasut
2025-03-24 12:39   ` Quentin Schulz
2025-03-25 23:02     ` Marek Vasut
2025-03-26  0:15       ` Tom Rini
2025-03-26  1:37         ` Marek Vasut
2025-03-26  9:22           ` Quentin Schulz [this message]
2025-03-27 14:36             ` Tom Rini
2025-03-22 21:55 ` [PATCH 5/8] env: Rename SYS_MMC_ENV_PART to ENV_SDMMC_EMMC_HW_PARTITION Marek Vasut
2025-03-24 12:44   ` Quentin Schulz
2025-03-22 21:55 ` [PATCH 6/8] env: Rename ENV_MMC_PARTITION to ENV_SDMMC_SW_PARTITION Marek Vasut
2025-03-24 12:50   ` Quentin Schulz
2025-03-22 21:55 ` [PATCH 7/8] env: Rename DEFAULT_ENV_FILE to ENV_DEFAULT_ENV_TEXT_FILE Marek Vasut
2025-03-22 21:55 ` [PATCH 8/8] env: Drop DELAY_ENVIRONMENT Marek Vasut
2025-03-24 12:27 ` [PATCH 1/8] env: Rename OVERWRITE_ETHADDR_ONCE to ENV_OVERWRITE_ETHADDR_ONCE Quentin Schulz
2025-03-25 17:01 ` Tom Rini

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=d9382933-70f2-4c3c-abf2-4fd711fbfc4f@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=marek.vasut@mailbox.org \
    --cc=paul.barker.ct@bp.renesas.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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