Hi Sasha, On Sun, Mar 5, 2023 at 2:52 PM Sasha Levin <sashal@xxxxxxxxxx> wrote: > From: Wolfram Sang <wsa+renesas@xxxxxxxxxxxxxxxxxxxx> > > [ Upstream commit b1dec4e78599a2ce5bf8557056cd6dd72e1096b0 ] > > R-Car H3 ES1.* was only available to an internal development group and > needed a lot of quirks and workarounds. These become a maintenance > burden now, so our development group decided to remove upstream support > for this SoC. Public users only have ES2 onwards. > > In addition to the ES1 specific removals, a check for it was added > preventing the machine to boot further. It may otherwise inherit wrong > clock settings from ES2 which could damage the hardware. > > Signed-off-by: Wolfram Sang <wsa+renesas@xxxxxxxxxxxxxxxxxxxx> > Reviewed-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > Link: https://lore.kernel.org/r/20230202092332.2504-1-wsa+renesas@xxxxxxxxxxxxxxxxxxxx > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx> This patch disables hardware support. Do we really want to backport that to stable? Perhaps backporting to v6.2.y and v6.1.y is still acceptable (the next Renesas BSP will be based on v6.1.y LTS), but I would not recommend backporting to older versions. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
