All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: andrew@lunn.ch, 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: Mon, 22 Aug 2022 12:00:15 +0000	[thread overview]
Message-ID: <166116961521.23061.17601464950387342608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220817094406.10658-1-r-gunasekaran@ti.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed, 17 Aug 2022 15:14:06 +0530 you 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.
> 
> [...]

Here is the summary with links:
  - [v3,net-next] net: ethernet: ti: davinci_mdio: Add workaround for errata i2329
    https://git.kernel.org/netdev/net-next/c/d04807b80691

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: andrew@lunn.ch, 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: Mon, 22 Aug 2022 12:00:15 +0000	[thread overview]
Message-ID: <166116961521.23061.17601464950387342608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220817094406.10658-1-r-gunasekaran@ti.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed, 17 Aug 2022 15:14:06 +0530 you 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.
> 
> [...]

Here is the summary with links:
  - [v3,net-next] net: ethernet: ti: davinci_mdio: Add workaround for errata i2329
    https://git.kernel.org/netdev/net-next/c/d04807b80691

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-08-22 12:01 UTC|newest]

Thread overview: 6+ 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-17  9:44 ` Ravi Gunasekaran
2022-08-20 19:57 ` Andrew Lunn
2022-08-20 19:57   ` Andrew Lunn
2022-08-22 12:00 ` patchwork-bot+netdevbpf [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=166116961521.23061.17601464950387342608.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=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 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.