From: Yixun Lan <dlan@kernel.org>
To: Inochi Amaoto <inochiama@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org,
Yixun Lan <dlan@gentoo.org>, Longbin Li <looong.bin@gmail.com>
Subject: Re: [PATCH 1/2] riscv: dts: spacemit: Add enough deassert time for the PHY on PICO ITX
Date: Sat, 25 Jul 2026 01:10:30 +0000 [thread overview]
Message-ID: <20260725011030-GKA77474@kernel.org> (raw)
In-Reply-To: <amQKpgD7NKlR8qEE@inochi.infowork>
Hi Inochi,
On 09:01 Sat 25 Jul , Inochi Amaoto wrote:
> On Fri, Jul 10, 2026 at 10:38:04PM +0000, Yixun Lan wrote:
> > Hi Inochi,
> >
> > On 14:33 Fri 10 Jul , Inochi Amaoto wrote:
> > > RTL8211F require at least 50ms deassert to guarantee the register
> > > access, 10ms is only enough for the PHY reset.
> > >
> > IMO, it's kind of too trivial to split into two separate patches,
> > while duplicating the commit message
> >
>
> For backport, I suggest keeping two patches, so it can be backported
> in a more clear way
>
Ok, fine by me, I will queue the patches for v7.3
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-25 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 6:33 [PATCH 1/2] riscv: dts: spacemit: Add enough deassert time for the PHY on PICO ITX Inochi Amaoto
2026-07-10 6:33 ` [PATCH 2/2] riscv: dts: spacemit: Add enough deassert time for the PHY on com260 board Inochi Amaoto
2026-07-10 22:38 ` [PATCH 1/2] riscv: dts: spacemit: Add enough deassert time for the PHY on PICO ITX Yixun Lan
2026-07-25 1:01 ` Inochi Amaoto
2026-07-25 1:10 ` Yixun Lan [this message]
2026-07-11 7:19 ` E Shattow
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=20260725011030-GKA77474@kernel.org \
--to=dlan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=looong.bin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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