From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org, linux-iio@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, gnstark@salutedevices.com,
jic23@kernel.org, lars@metafoo.de, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
christianshewitt@gmail.com,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [RFC PATCH v1 0/2] iio: adc: meson: add MPLL clock workaround for GXLX
Date: Tue, 31 Dec 2024 20:42:05 +0100 [thread overview]
Message-ID: <20241231194207.2772750-1-martin.blumenstingl@googlemail.com> (raw)
Hello,
Amlogic GXLX SoCs seem to be mostly the same silicon as GXL. The only
known differences are:
- one less Mali-450 GPU core
- no VP9 codec
- and an odd one: the three MPLL clocks need a bit toggled in the SAR
ADC register space
This series attempt to fix audio output (which relies on the MPLL
clocks) on the GXLX boards. Unfortunately all we have is a downstream
commit [0] without any further explanation (or anyone who wants to
provide details on this). Since it's not clear if this is a gate, a
reset or some other hardware fix: the driver side includes a warning
for users to update their .dtb along with kernel images in case we
ever figure out what these bits do and how to model them properly.
[0] https://github.com/khadas/linux/commit/d1d98f2ed8c83eb42af8880ed8e206aa402dd70a#diff-c5aaf54323ef93777c5083de37f933058ea8d0af79a1941e0b5a0667dc0f89b3
Martin Blumenstingl (2):
dt-bindings: iio: adc: amlogic,meson-saradc: Add GXLX SoC compatible
iio: adc: meson: add support for the GXLX SoC
.../iio/adc/amlogic,meson-saradc.yaml | 1 +
drivers/iio/adc/meson_saradc.c | 34 +++++++++++++++++++
2 files changed, 35 insertions(+)
--
2.47.1
next reply other threads:[~2024-12-31 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 19:42 Martin Blumenstingl [this message]
2024-12-31 19:42 ` [RFC PATCH v1 1/2] dt-bindings: iio: adc: amlogic,meson-saradc: Add GXLX SoC compatible Martin Blumenstingl
2025-01-02 7:59 ` Krzysztof Kozlowski
2024-12-31 19:42 ` [RFC PATCH v1 2/2] iio: adc: meson: add support for the GXLX SoC Martin Blumenstingl
2025-01-04 13:59 ` Jonathan Cameron
2025-01-05 15:49 ` Martin Blumenstingl
2025-01-06 13:44 ` Christian Hewitt
2025-01-06 22:34 ` Martin Blumenstingl
2025-01-02 9:40 ` [RFC PATCH v1 0/2] iio: adc: meson: add MPLL clock workaround for GXLX neil.armstrong
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=20241231194207.2772750-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=christianshewitt@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gnstark@salutedevices.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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