From: "Pali Rohár" <pali@kernel.org>
To: Tom Rini <trini@konsulko.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: mmc: Read eMMC partition access bits before card reset
Date: Sat, 24 Jun 2023 11:26:42 +0200 [thread overview]
Message-ID: <20230624092642.dhfv7qwrveliwego@pali> (raw)
In-Reply-To: <20230612181141.GP835503@bill-the-cat>
On Monday 12 June 2023 14:11:41 Tom Rini wrote:
> > > > https://patchwork.ozlabs.org/project/uboot/patch/20220828151929.32588-1-kabel@kernel.org/
> > >
> > > AFAICT, this patch has some open issues still.
> >
> > There were suggestion to make (that new kconfig option) enabled for
> > everything. But nobody respond if it is possible to have it
> > unconditionally enabled for every one board. Hence new config option in
> > that patch was introduced.
>
> Yes, the feedback was to change things so that the behavior is the
> default, since it looks like what we're doing now is wrong.
Sorry, but from the discussion I have not deduced this fact. Instead
from long silence it looks like that we cannot do any global change and
so config option was proposed there.
> And you have
> access to a few platforms to test things on to see if it breaks other
> platforms,
Unfortunately I do not have any other platform which is booting XIP
booting, which could be affected by that patch.
> and then putting it in to -next or early in the merge cycle
> on master would shake out any other problems with the approach. So if
> you're still interested in that platform, please make it a generic
> change or report back where it does fail so we can see what's going on
> elsewhere. Making the init_sequence_f table even more difficult to read
> is something we do want to avoid.
>
> --
> Tom
next prev parent reply other threads:[~2023-06-24 21:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 9:18 Please pull u-boot-marvell/master Stefan Roese
2023-05-03 17:14 ` Tom Rini
2023-05-05 19:37 ` mmc: Read eMMC partition access bits before card reset Pali Rohár
2023-05-07 13:54 ` Tom Rini
2023-05-07 14:01 ` Pali Rohár
2023-05-07 14:40 ` Tom Rini
2023-05-07 14:56 ` Pali Rohár
2023-05-07 16:45 ` Tom Rini
2023-05-07 20:36 ` Pali Rohár
2023-05-16 7:04 ` Pali Rohár
2023-05-16 15:36 ` Tom Rini
2023-05-16 18:52 ` Pali Rohár
2023-05-16 18:56 ` Tom Rini
2023-05-16 22:30 ` Pali Rohár
2023-05-17 8:26 ` Stefan Roese
2023-05-18 20:55 ` Tony Dinh
2023-05-25 12:57 ` Stefan Roese
2023-06-11 13:03 ` Pali Rohár
2023-06-12 9:22 ` Stefan Roese
2023-06-12 17:39 ` Pali Rohár
2023-06-12 18:11 ` Tom Rini
2023-06-12 19:11 ` Marek Behún
2023-06-24 9:26 ` Pali Rohár [this message]
2023-06-24 16:57 ` 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=20230624092642.dhfv7qwrveliwego@pali \
--to=pali@kernel.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;
as well as URLs for NNTP newsgroup(s).