From: <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <pavel@denx.de>, <kazuhiro3.hayashi@toshiba.co.jp>
Cc: <cip-dev@lists.cip-project.org>, <biju.das.jz@bp.renesas.com>,
<yuki.saito@toshiba.co.jp>
Subject: RE: [PATCH 0/1] clk: Fix for restructuring for no reparent case
Date: Thu, 1 Feb 2024 04:12:24 +0000 [thread overview]
Message-ID: <OS0PR01MB63880680E53C59CE9A63B28592432@OS0PR01MB6388.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <ZborIz5UgFSvjKRf@duo.ucw.cz>
Hi,
> -----Original Message-----
> From: Pavel Machek <pavel@denx.de>
> Sent: Wednesday, January 31, 2024 8:13 PM
> To: hayashi kazuhiro(林 和宏 DME ○DIG□MPS○MP4)
> <kazuhiro3.hayashi@toshiba.co.jp>
> Cc: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 ○DITC□
> DIT○OST) <nobuhiro1.iwamatsu@toshiba.co.jp>; pavel@denx.de;
> biju.das.jz@bp.renesas.com; saito yuki(齊藤 優貴 DME ○DIG□EAS○
> EA3) <yuki.saito@toshiba.co.jp>
> Subject: Re: [PATCH 0/1] clk: Fix for restructuring for no reparent case
>
> Hi!
>
> > With v6.1.72-cip13 + Zynq UltraScale+ MPSoC ZCU102, we observed that
> > Ethernet does not work when it's speed is 100Mbps.
> > This issue happens after d94c14f6fa34f2b8b33e5957f5b8dfb5aaf56b1e is
> > backported to the clk framework, which is not a part of linux-6.1.y
> > and probably is one of the dependencies of versa3 clk generator
> > support for Renesas SoCs. See the patch series "Add versa3 clk generator
> support".
> >
> > In mainline, a fix for the backport commit above is provided:
> > be8fa5fd0a48fd2decc4de81ffe72bb3ceacecd9.
> > This should be applied to linux-6.1.y-cip as well.
> > With v6.1.72-cip13 + this patch, we confirmed the ZCU102 Ethernet
> > works at 100Mbps.
>
> Thanks a lot for investigation and sorry for the trouble.
>
> The fix is simple enough, I am currently running tests, and can take it if they
> pass and there are no other comments.
>
I do not have an objection.
Reviewed-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
Best regards,
Nobuhiro
next prev parent reply other threads:[~2024-02-01 4:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 13:56 [PATCH 0/1] clk: Fix for restructuring for no reparent case Kazuhiro Hayashi
2024-01-31 11:12 ` Pavel Machek
2024-02-01 4:12 ` nobuhiro1.iwamatsu [this message]
2024-02-01 9:50 ` Pavel Machek
2024-01-31 13:56 ` [PATCH 1/1] clk: Fix best_parent_rate after moving code into a separate function Kazuhiro Hayashi
2024-01-31 11:17 ` Pavel Machek
2024-02-01 4:51 ` [cip-dev] " kazuhiro3.hayashi
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=OS0PR01MB63880680E53C59CE9A63B28592432@OS0PR01MB6388.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=pavel@denx.de \
--cc=yuki.saito@toshiba.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.