From: Marcin Wojtas <hidden> Date: 2021-03-22 00:40:52
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 <redacted>
---
arch/arm64/boot/dts/marvell/armada-ap807.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
From: Andrew Lunn <andrew@lunn.ch> Date: 2021-03-22 12:15:25
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 <redacted>
From: Marcin Wojtas <hidden> Date: 2021-05-12 17:41:49
Hi Gregory,
pon., 22 mar 2021 o 13:14 Andrew Lunn [off-list ref] napisał(a):
On Mon, Mar 22, 2021 at 01:39:15AM +0100, Marcin Wojtas wrote:
quoted
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 <redacted>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Marcin Wojtas <hidden> Date: 2021-06-16 19:12:50
Hi!
śr., 12 maj 2021 o 17:50 Marcin Wojtas [off-list ref] napisał(a):
Hi Gregory,
pon., 22 mar 2021 o 13:14 Andrew Lunn [off-list ref] napisał(a):
quoted
On Mon, Mar 22, 2021 at 01:39:15AM +0100, Marcin Wojtas wrote:
quoted
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 <redacted>
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.
Kind reminder. We are approaching v5.13 and it would be really great
to have this fix in time.
Thanks,
Marcin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
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 <redacted>
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 <redacted>