From: Andrew Lunn <andrew@lunn.ch>
To: Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-omap@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kishon@ti.com, vigneshr@ti.com, lkp@intel.com
Subject: Re: [PATCH v3 net-next] net: ethernet: ti: davinci_mdio: Add workaround for errata i2329
Date: Sat, 20 Aug 2022 21:57:26 +0200 [thread overview]
Message-ID: <YwE8pob0SOiHZ7K7@lunn.ch> (raw)
In-Reply-To: <20220817094406.10658-1-r-gunasekaran@ti.com>
On Wed, Aug 17, 2022 at 03:14:06PM +0530, Ravi Gunasekaran wrote:
> On the CPSW and ICSS peripherals, there is a possibility that the MDIO
> interface returns corrupt data on MDIO reads or writes incorrect data
> on MDIO writes. There is also a possibility for the MDIO interface to
> become unavailable until the next peripheral reset.
>
> The workaround is to configure the MDIO in manual mode and disable the
> MDIO state machine and emulate the MDIO protocol by reading and writing
> appropriate fields in MDIO_MANUAL_IF_REG register of the MDIO controller
> to manipulate the MDIO clock and data pins.
>
> More details about the errata i2329 and the workaround is available in:
> https://www.ti.com/lit/er/sprz487a/sprz487a.pdf
>
> Add implementation to disable MDIO state machine, configure MDIO in manual
> mode and achieve MDIO read and writes via MDIO Bitbanging
>
> Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
> Reported-by: kernel test robot <lkp@intel.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2022-08-20 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 9:44 [PATCH v3 net-next] net: ethernet: ti: davinci_mdio: Add workaround for errata i2329 Ravi Gunasekaran
2022-08-20 19:57 ` Andrew Lunn [this message]
2022-08-22 12:00 ` 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=YwE8pob0SOiHZ7K7@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kishon@ti.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).