From: Marcin Wojtas <mw@semihalf.com>
To: "Grégory Clement" <gregory.clement@bootlin.com>
Cc: linux-arm-kernel@lists.infradead.org,
Andrew Lunn <andrew@lunn.ch>,
devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] arm64: dts: ensure backward compatibility of the AP807 Xenon
Date: Wed, 12 May 2021 17:50:19 +0200 [thread overview]
Message-ID: <CAPv3WKdf5aX2W77N_-FBM5hugYW-ME1DvkjNuCUrcU8FG2XENg@mail.gmail.com> (raw)
In-Reply-To: <YFiKHu3hlAk+joOn@lunn.ch>
Hi Gregory,
pon., 22 mar 2021 o 13:14 Andrew Lunn <andrew@lunn.ch> napisał(a):
>
> On Mon, Mar 22, 2021 at 01:39:15AM +0100, Marcin Wojtas wrote:
> > A recent switch to a dedicated AP807 compatible string for the Xenon
> > SD/MMC controller result in the driver not being probed when
> > using updated device tree with the older kernel revisions.
> > It may also be problematic for other OSs/firmware that use
> > Linux device tree sources as a reference. Resolve the problem
> > with backward compatibility by restoring a previous compatible
> > string as secondary one.
> >
> > Signed-off-by: Marcin Wojtas <mw@semihalf.com>
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
>
Do you have any feedback about this patch? I just noticed it's not
merged in v5.13-rc1, it would be great to have it in the next release
though.
Best regards,
Marcin
next prev parent reply other threads:[~2021-05-12 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 0:39 [PATCH] arm64: dts: ensure backward compatibility of the AP807 Xenon Marcin Wojtas
2021-03-22 12:14 ` Andrew Lunn
2021-05-12 15:50 ` Marcin Wojtas [this message]
2021-06-16 19:12 ` Marcin Wojtas
2021-06-17 13:14 ` Gregory CLEMENT
2021-06-17 13:49 ` Marcin Wojtas
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=CAPv3WKdf5aX2W77N_-FBM5hugYW-ME1DvkjNuCUrcU8FG2XENg@mail.gmail.com \
--to=mw@semihalf.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 NNTP newsgroup(s).