From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty: serial: amba-pl011: Remove QDF2xxx workarounds
Date: Thu, 1 Feb 2024 15:48:08 +0100 [thread overview]
Message-ID: <226874eb-18c0-4834-aca5-46396b8a07e6@linaro.org> (raw)
In-Reply-To: <baf69674-7c69-4658-94ad-9b39fbb9924d@sirena.org.uk>
On 31.01.2024 14:44, Mark Brown wrote:
> On Mon, Jan 22, 2024 at 03:27:20PM +0100, Konrad Dybcio wrote:
>> This SoC family was destined for server use, featuring Qualcomm's very
>> interesting Kryo cores (before "Kryo" became a marketing term for Arm
>> cores with small modifications). It did however not leave the labs of
>> Qualcomm and presumably some partners, nor was it ever productized.
>>
>> Remove the workarounds, as they are long obsolete.
>
> There's one in Linaro's test lab which gets used by KernelCI:
>
> https://lkft.validation.linaro.org/scheduler/device_type/qcom-qdf2400
>
> While the platform is pretty old it works well enough and provides
> coverage of server platforms, ideally more server vendors would arrange
> for their boards to be available but that's not actually the case yet.
> The fact that it's a unique implementation of the architecture is also
> interesting from a test point of view. Given how trivial the workaround
> here is it seems more useful to keep the support, could we revert this
> commit please?
Right, sorry for the mess. It actually turned out that Qualcomm is apparently
still using some of these internally and was interested in still keeping it
alive, at least for the time being.. I mentioned this on another similarly-
themed patch threads, but forgot this one.
Should I submit a revert, or can this be dropped?
Konrad
next prev parent reply other threads:[~2024-02-01 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 14:27 [PATCH] tty: serial: amba-pl011: Remove QDF2xxx workarounds Konrad Dybcio
2024-01-30 17:05 ` Nathan Chancellor
2024-02-01 1:13 ` Peter Hilber
2024-01-31 13:44 ` Mark Brown
2024-02-01 14:48 ` Konrad Dybcio [this message]
2024-02-01 16:28 ` Mark Brown
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=226874eb-18c0-4834-aca5-46396b8a07e6@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marijn.suijten@somainline.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