From: Sasha Levin <sashal@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
mturquette@baylibre.com, sboyd@kernel.org,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 6.2 07/16] clk: renesas: rcar-gen3: Disable R-Car H3 ES1.*
Date: Tue, 14 Mar 2023 13:42:09 -0400 [thread overview]
Message-ID: <ZBCx8QV/CsMxiiUu@sashalap> (raw)
In-Reply-To: <CAMuHMdXLBVDPPM5ZGGV5O5uMm4R8=ZHvsgDxMxHQP2q4YKvhhA@mail.gmail.com>
On Sun, Mar 05, 2023 at 02:59:11PM +0100, Geert Uytterhoeven wrote:
>Hi Sasha,
>
>On Sun, Mar 5, 2023 at 2:52 PM Sasha Levin <sashal@kernel.org> wrote:
>> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
>>
>> [ 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@sang-engineering.com>
>> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> Link: https://lore.kernel.org/r/20230202092332.2504-1-wsa+renesas@sang-engineering.com
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
>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.
Ack, I'll drop it from older trees. Thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2023-03-14 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 13:51 [PATCH AUTOSEL 6.2 01/16] clk: qcom: mmcc-apq8084: remove spdm clocks Sasha Levin
2023-03-05 13:51 ` [PATCH AUTOSEL 6.2 07/16] clk: renesas: rcar-gen3: Disable R-Car H3 ES1.* Sasha Levin
2023-03-05 13:59 ` Geert Uytterhoeven
2023-03-14 17:42 ` Sasha Levin [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=ZBCx8QV/CsMxiiUu@sashalap \
--to=sashal@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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