From: Christian Loehle <christian.loehle@arm.com>
To: Patryk <pbiel7@gmail.com>, linux-mmc@vger.kernel.org
Subject: Re: SD card specification and eSDHC controller
Date: Thu, 28 Mar 2024 13:25:31 +0000 [thread overview]
Message-ID: <0cc46baf-8924-4ca7-98f3-c8376f7a5d87@arm.com> (raw)
In-Reply-To: <CA+DkFDb7HQukpUyxVemvoH4rXxt3F3Q957EnKzasnehKfbEEzA@mail.gmail.com>
On 28/03/2024 13:13, Patryk wrote:
> Hi,
> I've got a question regarding sd cards, their specifications, and the
> ability to support them by a host controller.
> In my eSDHC (NXP LS1028a soc) features summary I can find the following:
> - Conforms to the SD Host controller standard specification version
> 3.0, including test event register support
> - Compatible with the SD memory card specification version 3.01, and
> supports the high-capacity SD memory card
> - Compatible with the SDIO card specification version 3.0
>
> I have found that SD cards compatible with SD card specification 4.10
> and higher support something like an extension register and in
> particular power management. I've searched through kernel code and
> found that these registers are parsed by the let's say generic part of
> sd/mmc subsystem not by the host controller driver.
> Does it mean that I can connect the SD card compatible with spec 4.10
> and expect that the sd/mmc subsystem will use power management
> features if the card supports them?
Yes. mmc core will handle it if the card supports it.
"power management features" is a bit misleading, it's
SD_EXT_POWER_OFF_NOTIFY.
> Best regards
> Patryk
>
next prev parent reply other threads:[~2024-03-28 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 13:13 SD card specification and eSDHC controller Patryk
2024-03-28 13:25 ` Christian Loehle [this message]
2024-03-29 7:18 ` Patryk
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=0cc46baf-8924-4ca7-98f3-c8376f7a5d87@arm.com \
--to=christian.loehle@arm.com \
--cc=linux-mmc@vger.kernel.org \
--cc=pbiel7@gmail.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