public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>, Nishanth Menon <nm@ti.com>
Subject: Re: sdhci-omap: issues with PM features since 5.16
Date: Tue, 30 Jan 2024 13:15:11 +0200	[thread overview]
Message-ID: <20240130111511.GY5185@atomide.com> (raw)
In-Reply-To: <f80b5390-8bfa-43d8-80ce-70b069aef947@smile.fr>

* Romain Naour <romain.naour@smile.fr> [240129 17:42]:
> OK, I reproduced the same behavior on the AM574x evaluation board. I didn't know
> that ios can report clock 0 Hz and vdd invalid when the device is idle. I
> thought that was a symptom of my initial issue "mmc1: cache flush error -110".
> 
> So, there is no issue on AM574x evaluation board.

OK

> I don't understand how the emmc_pwrseq node can work on am5729-beagleboneai
> using gpio5_7 as reset-gpio since this pin it's not connected (F13 ball)
> 
> 	emmc_pwrseq: emmc_pwrseq {
> 		compatible = "mmc-pwrseq-emmc";
> 		reset-gpios = <&gpio5 7 GPIO_ACTIVE_LOW>;
> 	};
> 
> https://openbeagle.org/beagleboard/beaglebone-ai/-/blob/master/BeagleBone-AI_RevA2_sch.pdf

Sounds like that's only wired for some different revisions then?

> Note that mmc2 node is using ti,needs-special-reset property that is not used in
> shdci-omap driver but only in omap_hsmmc.

OK I think that's leftover from the earier use of omap_hsmmc.

Can you check that you have the dts property non-removable set for the emmc?

Regards,

Tony

  parent reply	other threads:[~2024-01-30 11:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 20:53 sdhci-omap: issues with PM features since 5.16 Romain Naour
2024-01-27  4:48 ` Tony Lindgren
2024-01-29 10:11   ` Romain Naour
2024-01-29 11:17     ` Tony Lindgren
2024-01-29 17:42       ` Romain Naour
2024-01-30 11:14         ` Romain Naour
2024-01-31 10:30           ` Tony Lindgren
2024-02-01  9:04             ` Romain Naour
2024-02-02  4:36               ` Tony Lindgren
2024-02-08 11:29                 ` Romain Naour
2024-02-08 12:57                   ` Adam Ford
2024-02-12  7:27                     ` Tony Lindgren
2024-02-12 13:24                       ` Adam Ford
2024-02-13  6:03                         ` Tony Lindgren
2024-02-13 12:43                           ` Adam Ford
2024-02-13 12:58                             ` Tony Lindgren
2024-03-15 23:49                   ` Romain Naour
2024-03-21  9:48                     ` Tony Lindgren
2024-01-30 11:15         ` Tony Lindgren [this message]
2024-01-30 11:22           ` Romain Naour

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=20240130111511.GY5185@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=romain.naour@smile.fr \
    /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