From: Kurt Kanzenbach <kurt@linutronix.de>
To: Ong Boon Leong <boon.leong.ong@intel.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Lay Kuan Loon <kuan.loon.lay@intel.com>,
Wong Vee Khee <vee.khee.wong@linux.intel.com>
Subject: Re: [PATCH net-next v2 1/1] net: phy: dp83867: introduce critical chip default init for non-of platform
Date: Wed, 13 Oct 2021 09:34:21 +0200 [thread overview]
Message-ID: <87a6jd5qf6.fsf@kurt> (raw)
In-Reply-To: <20211013065941.2124858-2-boon.leong.ong@intel.com>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
On Wed Oct 13 2021, Ong Boon Leong wrote:
> From: "Lay, Kuan Loon" <kuan.loon.lay@intel.com>
>
> PHY driver dp83867 has rich supports for OF-platform to fine-tune the PHY
> chip during phy configuration. However, for non-OF platform, certain PHY
> tunable parameters such as IO impedance and RX & TX internal delays are
> critical and should be initialized to its default during PHY driver probe.
>
> Tested-by: Clement <clement@intel.com>
> Signed-off-by: Lay, Kuan Loon <kuan.loon.lay@intel.com>
> Co-developed-by: Ong Boon Leong <boon.leong.ong@intel.com>
> Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com>
Thanks!
Tested-by: Kurt Kanzenbach <kurt@linutronix.de>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-10-13 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 6:59 [PATCH net-next v2 0/1] net: phy: dp83867 non-OF and loopback support Ong Boon Leong
2021-10-13 6:59 ` [PATCH net-next v2 1/1] net: phy: dp83867: introduce critical chip default init for non-of platform Ong Boon Leong
2021-10-13 7:34 ` Kurt Kanzenbach [this message]
2021-10-15 2:20 ` [PATCH net-next v2 0/1] net: phy: dp83867 non-OF and loopback support patchwork-bot+netdevbpf
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=87a6jd5qf6.fsf@kurt \
--to=kurt@linutronix.de \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuan.loon.lay@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=vee.khee.wong@linux.intel.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 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.