From: Christian Hewitt <christianshewitt@gmail.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
linux-amlogic@lists.infradead.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, gnstark@salutedevices.com,
lars@metafoo.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Subject: Re: [RFC PATCH v1 2/2] iio: adc: meson: add support for the GXLX SoC
Date: Mon, 6 Jan 2025 17:44:56 +0400 [thread overview]
Message-ID: <5CEDC847-2653-42F3-A85E-A06D6E5DB135@gmail.com> (raw)
In-Reply-To: <CAFBinCBxaVet9HxW98uCSDnv1XVXV6r4V9Z3BRmZJypTcxDZ0Q@mail.gmail.com>
> On 5 Jan 2025, at 7:49 pm, Martin Blumenstingl <martin.blumenstingl@googlemail.com> wrote:
>
> Hi Jonathan,
>
> On Sat, Jan 4, 2025 at 2:59 PM Jonathan Cameron <jic23@kernel.org> wrote:
>>
>> On Tue, 31 Dec 2024 20:42:07 +0100
>> Martin Blumenstingl <martin.blumenstingl@googlemail.com> wrote:
>>
>>> The SARADC IP on the GXLX SoC itself is identical to the one found on
>>> GXL SoCs. However, GXLX SoCs require poking the first three bits in the
>>> MESON_SAR_ADC_REG12 register to get the three MPLL clocks (used as clock
>>> generators for the audio frequencies) to work.
>>>
>>> The reason why there are MPLL clock bits in the ADC register space is
>>> entirely unknown and it seems that nobody is able to comment on this.
>>> So clearly mark this as a workaround and add a warning so users are
>>> notified that this workaround can change (once we know what these bits
>>> actually do).
>>
>> So IIUC this is to make some non ADC component work.
> That's correct
>
>> How are you handling dependencies? The ADC driver might not be loaded or
>> is there some reason it definitely is at the point where the audio driver
>> loads?
> Unfortunately there are no dependencies at the moment.
> To me it's not even 100% clear if those bits are a dependency for the
> audio IP or if they are instead linked with the clock controller (more
> background info: some of the MPLL clocks are - at least in theory, in
> practice we don't use that - are also used as input for the Mali GPU
> and video subsystem. The only practical usage that I'm aware of is the
> audio controller).
In my testing it makes no difference to the audio driver when the adc
bit poke is done. The audio driver probes and loads and you can play
media without generating any visible errors. There’s just no audible
output on GXLX until the poke - it’s like hitting an un-mute button.
For the series:
Tested-by: Christian Hewitt <christianshewitt@gmail.com>
Christian
> Christian and I have both tried with all of our contacts at Amlogic
> but did not get any answers.
> If I knew the purpose of these bits I'd model them as whatever they
> are (resets, clock gates, ...) and provide proper dt-bindings.
>
>
> Best regards,
> Martin
next prev parent reply other threads:[~2025-01-06 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 19:42 [RFC PATCH v1 0/2] iio: adc: meson: add MPLL clock workaround for GXLX Martin Blumenstingl
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 [this message]
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=5CEDC847-2653-42F3-A85E-A06D6E5DB135@gmail.com \
--to=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=martin.blumenstingl@googlemail.com \
--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