From: "Jiawen Wu" <jiawenwu@trustnetic•com>
To: "'Jarkko Nikula'" <jarkko.nikula@linux•intel.com>,
<andi.shyti@kernel•org>, <andriy.shevchenko@linux•intel.com>,
<mika.westerberg@linux•intel.com>, <jsd@semihalf•com>,
<davem@davemloft•net>, <edumazet@google•com>, <kuba@kernel•org>,
<pabeni@redhat•com>, <rmk+kernel@armlinux•org.uk>,
<piotr.raczynski@intel•com>, <andrew@lunn•ch>,
<linux-i2c@vger•kernel.org>, <netdev@vger•kernel.org>
Cc: <mengyuanlou@net-swift•com>, <duanqiangwen@net-swift•com>
Subject: RE: [PATCH net 0/3] Add I2C bus lock for Wangxun
Date: Tue, 27 Aug 2024 10:26:37 +0800 [thread overview]
Message-ID: <021001daf828$8b4cd6e0$a1e684a0$@trustnetic.com> (raw)
In-Reply-To: <cacbd4a1-1e7f-4067-95ad-215dde7eedcc@linux.intel.com>
On Fri, Aug 23, 2024 7:05 PM, Jarkko Nikula wrote:
> Hi
> Hi
>
> On 8/23/24 6:02 AM, Jiawen Wu wrote:
> > Sometimes the driver can not get the SFP information because the I2C bus
> > is accessed by the firmware at the same time. So we need to add the lock
> > on the I2C bus access. The hardware semaphores perform this lock.
> >
> > Jiawen Wu (3):
> > net: txgbe: add IO address in I2C platform device data
> > i2c: designware: add device private data passing to lock functions
> > i2c: designware: support hardware lock for Wangxun 10Gb NIC
> >
> I was wondering the Fixes tag use in the series. Obviously patchset is
> not fixing a regression so question is what happens when issue occurs?
>
> I don't think e.g. failing I2C transfer with an error code yet qualifies
> backporting into Linux stable?
Ah, I think this was a leftover bug from when I added Wangxun NIC support
in I2C designware, so I added a fix tag.
next prev parent reply other threads:[~2024-08-27 2:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 3:02 [PATCH net 0/3] Add I2C bus lock for Wangxun Jiawen Wu
2024-08-23 3:02 ` [PATCH net 1/3] net: txgbe: add IO address in I2C platform device data Jiawen Wu
2024-08-23 14:14 ` Andy Shevchenko
2024-08-23 3:02 ` [PATCH net 2/3] i2c: designware: add device private data passing to lock functions Jiawen Wu
2024-08-23 14:06 ` Andy Shevchenko
2024-08-27 13:24 ` Paolo Abeni
2024-08-29 5:16 ` kernel test robot
2024-08-23 3:02 ` [PATCH net 3/3] i2c: designware: support hardware lock for Wangxun 10Gb NIC Jiawen Wu
2024-08-23 14:13 ` Andy Shevchenko
2024-08-29 9:15 ` Jiawen Wu
2024-08-29 10:59 ` 'Andy Shevchenko'
2024-08-23 11:04 ` [PATCH net 0/3] Add I2C bus lock for Wangxun Jarkko Nikula
2024-08-27 2:26 ` Jiawen Wu [this message]
2024-08-26 1:32 ` Andrew Lunn
2024-08-26 2:04 ` Jiawen Wu
2024-08-26 2:33 ` Andrew Lunn
2024-08-27 2:21 ` Jiawen Wu
2024-08-27 12:18 ` Andrew Lunn
2024-08-29 6:40 ` Jiawen Wu
2024-08-29 15:27 ` Andrew Lunn
2024-09-03 6:31 ` Jiawen Wu
2024-09-03 12:45 ` Andrew Lunn
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='021001daf828$8b4cd6e0$a1e684a0$@trustnetic.com' \
--to=jiawenwu@trustnetic$(echo .)com \
--cc=andi.shyti@kernel$(echo .)org \
--cc=andrew@lunn$(echo .)ch \
--cc=andriy.shevchenko@linux$(echo .)intel.com \
--cc=davem@davemloft$(echo .)net \
--cc=duanqiangwen@net-swift$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=jarkko.nikula@linux$(echo .)intel.com \
--cc=jsd@semihalf$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-i2c@vger$(echo .)kernel.org \
--cc=mengyuanlou@net-swift$(echo .)com \
--cc=mika.westerberg@linux$(echo .)intel.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=piotr.raczynski@intel$(echo .)com \
--cc=rmk+kernel@armlinux$(echo .)org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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