From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: "H. Nikolaus Schaller" <hns@messlink.de>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>
Subject: Re: omap_hsmmc RX DMA errors
Date: Mon, 16 Jan 2023 08:43:11 +0200 [thread overview]
Message-ID: <Y8Tx/49BYvLDNje6@atomide.com> (raw)
In-Reply-To: <CAHCN7x+EaXd3cR-0pUnjwDJAWqyb6Oamrh9HJyskpmLJfMobqw@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [230115 18:55]:
> On Sun, Jan 8, 2023 at 11:58 PM Tony Lindgren <tony@atomide.com> wrote:
> > Things should be ready to flip the remaining SoCs to use sdhci so we
> > should do that.
>
> Do you want me to push a patch? It might bring more clout if it comes
> from you, but I don't mind. If so, how do we handle the backwards
> compatibility stuff with older device trees?
Sure please go ahead and post a patch for omap3.dtsi. It's best to do it
one SoC type at a time. Older dtb files will work as long as there is
the old mmc driver in place. But considering we don't even have complete
data in the dts files in general, I would not worry about supporting older
dtb files. In most cases we can add boot timer warnings if needed.
Regards,
Tony
prev parent reply other threads:[~2023-01-16 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 17:54 omap_hsmmc RX DMA errors Adam Ford
2023-01-05 19:01 ` H. Nikolaus Schaller
[not found] ` <5DD8AC17-A7FD-4D44-953E-F2EF84C6896D@messlink.de>
2023-01-05 19:08 ` Adam Ford
2023-01-05 19:20 ` Adam Ford
2023-01-09 5:58 ` Tony Lindgren
2023-01-15 18:53 ` Adam Ford
2023-01-15 18:55 ` Adam Ford
2023-01-16 6:43 ` 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=Y8Tx/49BYvLDNje6@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=hns@messlink.de \
--cc=letux-kernel@openphoenux.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.