public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Rengarajan.S@microchip.com
Cc: linux-usb@vger.kernel.org, davem@davemloft.net,
	Woojung.Huh@microchip.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, pabeni@redhat.com,
	UNGLinuxDriver@microchip.com, edumazet@google.com,
	kuba@kernel.org
Subject: Re: [PATCH net-next v1] lan78xx: lan7801 MAC support with lan8841
Date: Fri, 28 Jun 2024 15:03:27 +0200	[thread overview]
Message-ID: <2aa4fba0-c5bd-47e9-97a7-3f73048282cb@lunn.ch> (raw)
In-Reply-To: <369cd82f60db7a9d6fd67a467e3c45b68348155b.camel@microchip.com>

> Although, there is no specific errata available for adding fixup
> specific to lan78xx USB dongle, we have added the fixup for handing
> specific configurations to ensure the PHY operates correctly with the
> MAC. In this case while transmitting from MAC to PHY the device does
> not add the delay locally at its TX input pins. It expects the TXC
> delay to be provided by on-chip MAC. Since the delay calculated in this
> case is specific to the lan78xx USB dongle it is not possible to use
> this fixup for interfacing with generic MAC.

Have you tried PHY_INTERFACE_MODE_RGMII_TXID when connecting to the
PHY? The four PHY_INTERFACE_MODE_RGMII_* values are the official way
to ask the PHY to insert delays, or not. If that is all you are doing,
i don't think you need these fixups at all.

> > Please give me a details explanation why this fixup will not be
> > applied to other instances of this PHY in the system.
> 
> As stated above, the TXC delay calculated for the PHY is specific to
> the lan78xx on-chip MAC. This delay ensures that both the phy and MAC
> clock delay timing is met. Any other MACs connected will need a
> different delay values to be synchronized with MAC and hence these
> instances will get failed.

You did not answer my question. Show me the code path which prevents
this being applied to other PHYs. Is there a comparison to netdev
somewhere when applying the fixup? Give me the file:line number.

	  Andrew

      reply	other threads:[~2024-06-28 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  9:42 [PATCH net-next v1] lan78xx: lan7801 MAC support with lan8841 Rengarajan S
2024-06-13  1:33 ` Jakub Kicinski
2024-06-20  5:33   ` Rengarajan.S
2024-06-13 20:46 ` Andrew Lunn
2024-06-20  5:48   ` Rengarajan.S
2024-06-20 13:49     ` Andrew Lunn
2024-06-28 10:59       ` Rengarajan.S
2024-06-28 13:03         ` Andrew Lunn [this message]

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=2aa4fba0-c5bd-47e9-97a7-3f73048282cb@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Rengarajan.S@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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