All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: "Lucien.Jheng" <lucienzx159@gmail.com>,
	jerome.forissier@linaro.org, skylake.huang@mediatek.com,
	s-vadapalli@ti.com, paul.barker.ct@bp.renesas.com,
	marek.vasut+renesas@mailbox.org, u-boot@lists.denx.de
Cc: lucien.jheng@airoha.com, frank-w@public-files.de, daniel@makrotopia.org
Subject: Re: [U-Boot, v2, 1/1]net: phy: add paged PHY register accessors
Date: Sun, 2 Nov 2025 14:59:01 +0100	[thread overview]
Message-ID: <2f894c99-3279-4d8a-8e09-b002a73d85bb@mailbox.org> (raw)
In-Reply-To: <20251006124915.13647-1-lucienzx159@gmail.com>

On 10/6/25 2:49 PM, Lucien.Jheng wrote:
> Synchronize paged PHY helpers with Linux v6.17.
> 
> Add support for PHY devices that use paged register access by
> implementing the following functions:
> - phy_save_page(): Save current page number
> - phy_select_page(): Switch to a specific page and return previous page
> - phy_restore_page(): Restore previously saved page
> 
> Also adds read_page and write_page callbacks to the phy_driver
> structure to enable driver-specific page handling.
> 
> These helpers allow safe access to paged PHY registers by ensuring
> proper page selection and restoration,
> even in error conditions, which will be used by the Airoha PHY driver.
Are there any users ? If not, this is dead code.

  parent reply	other threads:[~2025-11-02 13:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 12:49 [U-Boot, v2, 1/1]net: phy: add paged PHY register accessors Lucien.Jheng
2025-11-02 12:45 ` Lucien.Jheng
2025-11-02 13:59 ` Marek Vasut [this message]
2025-11-02 15:34   ` Lucien.Jheng
2025-11-02 17:01     ` Marek Vasut
2025-11-03  0:13       ` Lucien Jheng
2025-11-03  0:46         ` Marek Vasut

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=2f894c99-3279-4d8a-8e09-b002a73d85bb@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=daniel@makrotopia.org \
    --cc=frank-w@public-files.de \
    --cc=jerome.forissier@linaro.org \
    --cc=lucien.jheng@airoha.com \
    --cc=lucienzx159@gmail.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=paul.barker.ct@bp.renesas.com \
    --cc=s-vadapalli@ti.com \
    --cc=skylake.huang@mediatek.com \
    --cc=u-boot@lists.denx.de \
    /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.