From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Mark Brown <broonie@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Codrin Ciubotariu <codrin.ciubotariu@microchip.com>,
Rob Herring <robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/2] ARM: dts: at91: Fixes for AT91SAM9G20-EK DTS
Date: Wed, 13 Apr 2022 18:45:00 +0200 [thread overview]
Message-ID: <2ece2c68-789e-9df9-dd22-c1da5d402179@microchip.com> (raw)
In-Reply-To: <20220404102806.581374-1-broonie@kernel.org>
On 04/04/2022 at 12:28, Mark Brown wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> The DT description for the audio subsystem on the AT91SAM9G20-EK
> reference board is a bit bitrotted, the clocking for the WM8731 audio
> CODEC is not described. Previously this was handled in the machine
> driver but at some point in the transition to the common clock framework
> that code was broken and rendered mostly redundant so the first patch
> adds a mapping of the MCLK on the CODEC which is used via existing code
> in it's driver.
>
> We also have some warnings on the WM8731, EEPROM and the MMC from the
> regulator framework since the supplies on the board aren't described.
> These don't fundamentally matter since they are fixed voltage regulators
> and not controlled by software at runtime but it's nicer to fix them.
>
> v2:
> - Rebase onto v5.18-rc1.
> - Also cover the serial EEPROM supply which is requested by that driver.
>
> Mark Brown (2):
> ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek
> ARM: dts: at91: Describe regulators on at91sam9g20ek
For the whole series:
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
I'm gonna queue these patches for 5.18 "fixes".
Thanks a lot Mark, that's really appreciated!
Best regards,
Nicolas
>
> arch/arm/boot/dts/at91sam9g20ek_common.dtsi | 43 +++++++++++++++++++++
> 1 file changed, 43 insertions(+)
>
>
> base-commit: 3123109284176b1532874591f7c81f3837bbdc17
> --
> 2.30.2
>
--
Nicolas Ferre
prev parent reply other threads:[~2022-04-13 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 10:28 [PATCH v2 0/2] ARM: dts: at91: Fixes for AT91SAM9G20-EK DTS Mark Brown
2022-04-04 10:28 ` [PATCH v2 1/2] ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek Mark Brown
2022-04-04 10:28 ` [PATCH v2 2/2] ARM: dts: at91: Describe regulators " Mark Brown
2022-04-13 16:45 ` Nicolas Ferre [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=2ece2c68-789e-9df9-dd22-c1da5d402179@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=codrin.ciubotariu@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).