From: <Claudiu.Beznea@microchip.com>
To: <m.grzeschik@pengutronix.de>, <linux-arm-kernel@lists.infradead.org>
Cc: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>, <linux-clk@vger.kernel.org>,
<kernel@pengutronix.de>
Subject: Re: [PATCH v3 1/3] clk: at91: rm9200: fix usb device clock id
Date: Fri, 11 Nov 2022 11:00:53 +0000 [thread overview]
Message-ID: <048269a7-3aea-129f-f4db-4cd321e89fa3@microchip.com> (raw)
In-Reply-To: <94c6679c-f518-aa74-5cda-f28f1dc3129a@microchip.com>
On 10.11.2022 12:41, Claudiu Beznea - M18063 wrote:
> On 09.11.2022 14:46, Michael Grzeschik wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> Referring to the datasheet the index 2 is the MCKUDP. When enabled, it
>> "Enables the automatic disable of the Master Clock of the USB Device
>> Port when a suspend condition occurs". We fix the index to the real UDP
>> id which "Enables the 48 MHz clock of the USB Device Port".
>>
>> Cc: mturquette@baylibre.com
>> Cc: sboyd@kernel.org
>> Cc: nicolas.ferre@microchip.com
>> Cc: alexandre.belloni@bootlin.com
>> Cc: ludovic.desroches@microchip.com
>> Cc: claudiu.beznea@microchip.com
>> Cc: linux-clk@vger.kernel.org
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: kernel@pengutronix.de
>> Fixes: 02ff48e4d7f7 ("clk: at91: add at91rm9200 pmc driver")
>> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
>
> Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
Actually, looking again at this... I think it is best to squash this patch
with path 2/3 from this series. Otherwise applying them independently will
lead to usb driver probe failure. Back porting them (with proper
dependency) to older kernel version may also lead to failures.
>
>
>>
>> ---
>> v1 -> v2: - removed ; from patch description
>> - added fixes tag
>> v2 -> v3: - updated the fixes tag
>>
>> drivers/clk/at91/at91rm9200.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/clk/at91/at91rm9200.c b/drivers/clk/at91/at91rm9200.c
>> index b174f727a8ef8d..16870943a13e54 100644
>> --- a/drivers/clk/at91/at91rm9200.c
>> +++ b/drivers/clk/at91/at91rm9200.c
>> @@ -40,7 +40,7 @@ static const struct clk_pll_characteristics rm9200_pll_characteristics = {
>> };
>>
>> static const struct sck at91rm9200_systemck[] = {
>> - { .n = "udpck", .p = "usbck", .id = 2 },
>> + { .n = "udpck", .p = "usbck", .id = 1 },
>> { .n = "uhpck", .p = "usbck", .id = 4 },
>> { .n = "pck0", .p = "prog0", .id = 8 },
>> { .n = "pck1", .p = "prog1", .id = 9 },
>> --
>> 2.30.2
>>
>
next prev parent reply other threads:[~2022-11-11 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 12:46 [PATCH v3 0/3] ARM: at91: USB Device Port fixes Michael Grzeschik
2022-11-09 12:46 ` [PATCH v3 1/3] clk: at91: rm9200: fix usb device clock id Michael Grzeschik
2022-11-10 10:41 ` Claudiu.Beznea
2022-11-11 11:00 ` Claudiu.Beznea [this message]
2022-11-14 18:59 ` Michael Grzeschik
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=048269a7-3aea-129f-f4db-4cd321e89fa3@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=mturquette@baylibre.com \
--cc=sboyd@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