From: sashiko-bot@kernel.org
To: "Chih Kai Hsu" <hsu.chih.kai@realtek.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH net-next v6 02/10] r8152: add new init writes for RTL8156B/8157/8159
Date: Fri, 09 Oct 2026 08:17:18 +0000 [thread overview]
Message-ID: <sashiko-outbox-165061@kernel.org> (raw)
In-Reply-To: <20261008081556.47901-3-nic_swsd@realtek.com>
> Bring the per-chip init functions in line with the vendor init
> sequence by adding writes the shared r8156_init() never performed.
>
> - Clear PREBOOT_OPTION and RMT_WAKE_EN in all four init functions.
>
> - Add r8156b_u2phy_backup() for RTL8156B.
>
> - Clear AUTO_SPEEDUP in r8157_init() and r8159_init().
>
> - Disable interrupt mitigation (0xcf04) in r8157_init() and
> r8159_init().
>
> - Clear the Warm RST / Bus RST event flag (0xcd06 BIT(11)) in
> r8157_init() and r8159_init().
>
> - Clear the FW u1u2 patch option (0xb9a6 BIT(0)) and enable the u3phy
> patch backup (0xb9a2) in r8159_init() only.
>
> - Clear RX_END_TRANSFER_EN (0xd406 BIT(11)) in r8157_init().
> While it is set, incoming packets are buffered in the RX FIFO and
> Bulk-in transfers are suspended. The bit is zero by default and
> isn't used now. Clear it unconditionally for safety.
>
> Signed-off-by: Chih Kai Hsu <hsu.chih.kai@realtek.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008081556.47901-1-nic_swsd@realtek.com?part=2
next prev parent reply other threads:[~2026-10-09 8:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 8:15 [PATCH net-next v6 0/10] r8152: refactor and extend RTL8157/8159 support Chih Kai Hsu
2026-10-08 8:15 ` [PATCH net-next v6 01/10] r8152: split r8156_init per chip and factor out wait_autoload_done Chih Kai Hsu
2026-10-08 12:17 ` Birger Koblitz
2026-10-09 8:17 ` sashiko-bot
2026-10-08 8:15 ` [PATCH net-next v6 02/10] r8152: add new init writes for RTL8156B/8157/8159 Chih Kai Hsu
2026-10-09 8:17 ` sashiko-bot [this message]
2026-10-08 8:15 ` [PATCH net-next v6 03/10] r8152: split RTL_VER_17 into QFN68 and QFN100 package variants Chih Kai Hsu
2026-10-09 8:17 ` sashiko-bot
2026-10-08 8:15 ` [PATCH net-next v6 04/10] r8152: split rtl8156_enable/up/down into per-chip-family functions Chih Kai Hsu
2026-10-09 8:17 ` sashiko-bot
2026-10-08 8:15 ` [PATCH net-next v6 05/10] r8152: fix up and down register settings for RTL8156/8156B/8157/8159 Chih Kai Hsu
2026-10-09 8:17 ` sashiko-bot
2026-10-08 8:15 ` [PATCH net-next v6 06/10] r8152: split r8157_hw_phy_cfg into RTL8157 and RTL8159 variants Chih Kai Hsu
2026-10-09 8:17 ` sashiko-bot
2026-10-08 8:15 ` [PATCH net-next v6 07/10] r8152: add rtl8157_unload and rtl8157_change_mtu Chih Kai Hsu
2026-10-09 8:17 ` sashiko-bot
2026-10-08 8:15 ` [PATCH net-next v6 08/10] r8152: add TGPHY register access for RTL8157 and RTL8159 Chih Kai Hsu
2026-10-09 8:17 ` sashiko-bot
2026-10-08 8:15 ` [PATCH net-next v6 09/10] r8152: extract rtl_fc_pause_pkt_en() and apply it to RTL8156/8157/8159 Chih Kai Hsu
2026-10-09 8:17 ` sashiko-bot
2026-10-08 8:15 ` [PATCH net-next v6 10/10] r8152: enable UPS for RTL8157 and RTL8159 QFN68 Chih Kai Hsu
2026-10-09 8:17 ` sashiko-bot
2026-10-08 8:19 ` [PATCH net-next v6 0/10] r8152: refactor and extend RTL8157/8159 support netdev-bot+sinfo
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=sashiko-outbox-165061@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=hsu.chih.kai@realtek.com \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@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