public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Meagan Lloyd <meaganlloyd@linux.microsoft.com>, rjui@broadcom.com
Cc: sbranden@broadcom.com, linux-arm-kernel@lists.infradead.org,
	tgopinath@linux.microsoft.com, adrian.hunter@intel.com,
	linux-mmc@vger.kernel.org
Subject: Re: [RFC PATCH] mmc: host: sdhci-iproc: implement the .hw_reset callback
Date: Mon, 13 Apr 2026 10:43:13 -0700	[thread overview]
Message-ID: <702c52e4-b0b3-4e1e-a40d-29e136e46d7d@broadcom.com> (raw)
In-Reply-To: <3305684d-8517-47dd-8852-2e34d40fc712@linux.microsoft.com>

On 4/13/26 10:38, Meagan Lloyd wrote:
> 
> On 3/27/2026 3:21 PM, Meagan Lloyd wrote:
>> Implement the .hw_reset callback so that the eMMC can be reset as needed
>> given cap-mmc-hw-reset is set in the devicetree and the functionality is
>> enabled on the eMMC.
>>
>> Signed-off-by: Meagan Lloyd <meaganlloyd@linux.microsoft.com>
>> ---
>>
>> SDHCI_POWER_CONTROL[4] (SD Host Controller Standard) has been repurposed
>> on my Broadcomm processor to be eMMC hardware reset
>> (SDIO*_eMMCSDXC_CTRL[12], HRESET).
>>
>> Can you confirm this repurposed bit is consistent across the Broadcomm
>> iProc processors and thus the .hw_reset callback can be uniformly
>> applied in this driver?
> 
> Hi Ray & Scott,
> 
> I hope you're doing well. This bit looks to have been repurposed from
> the SD Host Controller Standard's VDD2 Power Control to being used for
> toggling the hardware reset signal to eMMCs. Can you verify that it
> applies across the iProc processors so that I may finalize this patch?

Which iProc process are you using? If you are not sure this applies 
broadly, can you at least make it specific to the SoC you are using?
-- 
Florian



  reply	other threads:[~2026-04-13 17:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27 22:21 [RFC PATCH] mmc: host: sdhci-iproc: implement the .hw_reset callback Meagan Lloyd
2026-04-13 17:38 ` Meagan Lloyd
2026-04-13 17:43   ` Florian Fainelli [this message]
2026-04-15 18:07     ` Meagan Lloyd
     [not found]       ` <CA+Jzhd+_CKn1X0YDsoh9-OFeCG9sc2Q0OFfphkRaXpEA647xyQ@mail.gmail.com>
2026-04-15 20:43         ` Meagan Lloyd
2026-04-15 20:44           ` Florian Fainelli

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=702c52e4-b0b3-4e1e-a40d-29e136e46d7d@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=adrian.hunter@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=meaganlloyd@linux.microsoft.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=tgopinath@linux.microsoft.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