From: gregory.clement@bootlin.com
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Vladimir Zapolskiy <vz@mleia.com>,
Sylvain Lemieux <slemieux.tyco@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: lpc32xx: stop overwriting TEST_CLK_SEL
Date: Mon, 15 Apr 2019 09:59:39 +0200 [thread overview]
Message-ID: <b5b97198d85ead33afa2fcf619a50944@bootlin.com> (raw)
In-Reply-To: <20190411141209.3106-1-alexandre.belloni@bootlin.com>
On 2019-04-11 16:12, Alexandre Belloni wrote:
> While the UDA1380 is described in some lpc3250 device trees, there is
> currently no real user of that codec. Anyway, if the codec needs a
> clock,
> it should take it explicitly.
>
> lpc3250_machine_init is called for all the lpc32xx machines and some
> are
> using test1_clk (for example to strobe an HW watchdog). Overwriting
> TEST_CLK_SEL prevents booting those platforms.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> ---
> arch/arm/mach-lpc32xx/phy3250.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/arm/mach-lpc32xx/phy3250.c
> b/arch/arm/mach-lpc32xx/phy3250.c
> index fdbb1409c32b..1db8508493a5 100644
> --- a/arch/arm/mach-lpc32xx/phy3250.c
> +++ b/arch/arm/mach-lpc32xx/phy3250.c
> @@ -128,11 +128,6 @@ static void __init lpc3250_machine_init(void)
> {
> lpc32xx_serial_init();
>
> - /* Test clock needed for UDA1380 initial init */
> - __raw_writel(LPC32XX_CLKPWR_TESTCLK2_SEL_MOSC |
> - LPC32XX_CLKPWR_TESTCLK_TESTCLK2_EN,
> - LPC32XX_CLKPWR_TEST_CLK_SEL);
> -
> of_platform_default_populate(NULL, lpc32xx_auxdata_lookup, NULL);
> }
next prev parent reply other threads:[~2019-04-15 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 14:12 [PATCH] ARM: lpc32xx: stop overwriting TEST_CLK_SEL Alexandre Belloni
2019-04-15 7:59 ` gregory.clement [this message]
2019-04-19 19:57 ` Vladimir Zapolskiy
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=b5b97198d85ead33afa2fcf619a50944@bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slemieux.tyco@gmail.com \
--cc=vz@mleia.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