Linux-OMAP Archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jeremy Mattfeld <jmmattfeld@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: sdhci-omap signal contention
Date: Wed, 3 Apr 2024 10:49:52 +0300	[thread overview]
Message-ID: <20240403074952.GJ5132@atomide.com> (raw)
In-Reply-To: <CABbzQ=fqmBeq_9YLjWq_8Lf=1E1L0igMxHUKcHr6hohyYnvvkQ@mail.gmail.com>

* Jeremy Mattfeld <jmmattfeld@gmail.com> [240315 23:04]:
> I have no specific requirements to read/write on the eMMC while
> performing I/O on the spi but I still get sdhci errors errors while
> using the mux drivers when I want to talk to the adc's.  I am hoping
> there is some kind of software workaround for this problem.

Not sure what the issue might be, but please check if this recent fix
helps:

f9e2a5b00a35 ("mmc: sdhci-omap: re-tuning is needed after a pm transition
to support emmc HS200 mode")

Regards,

Tony

      reply	other threads:[~2024-04-03  7:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 23:04 sdhci-omap signal contention Jeremy Mattfeld
2024-04-03  7:49 ` Tony Lindgren [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=20240403074952.GJ5132@atomide.com \
    --to=tony@atomide.com \
    --cc=jmmattfeld@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).