From: 'Andy Shevchenko' <andriy.shevchenko@linux.intel.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: andi.shyti@kernel.org, jarkko.nikula@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, andrew@lunn.ch,
linux-i2c@vger.kernel.org, netdev@vger.kernel.org,
mengyuanlou@net-swift.com, duanqiangwen@net-swift.com,
stable@vger.kernel.org
Subject: Re: [PATCH net 3/3] i2c: designware: support hardware lock for Wangxun 10Gb NIC
Date: Thu, 29 Aug 2024 13:59:35 +0300 [thread overview]
Message-ID: <ZtBUlxDWTfwpzm5V@smile.fi.intel.com> (raw)
In-Reply-To: <02a901daf9f4$063e8cf0$12bba6d0$@trustnetic.com>
On Thu, Aug 29, 2024 at 05:15:42PM +0800, Jiawen Wu wrote:
> On Fri, Aug 23, 2024 10:13 PM, Andy Shevchenko wrote:
> > On Fri, Aug 23, 2024 at 11:02:42AM +0800, Jiawen Wu wrote:
...
> > > +static int i2c_dw_txgbe_acquire_lock(struct dw_i2c_dev *dev)
> > > +{
> > > + void __iomem *req_addr;
> > > + u32 swsm;
> > > + int i;
> > > +
> > > + req_addr = dev->ext + I2C_DW_TXGBE_MNG_SW;
> > > +
> > > + for (i = 0; i < I2C_DW_TXGBE_REQ_RETRY_CNT; i++) {
> >
> > Retry loops much better in a form of
> >
> > unsigned int retries = ...;
> > ...
> > do {
> > ...
> > } while (--retries);
> >
> > BUT... see below.
> >
> > > + writel(I2C_DW_TXGBE_MNG_SW_SM, req_addr);
> > > +
> > > + /* If we set the bit successfully then we got semaphore. */
> > > + swsm = readl(req_addr);
> > > + if (swsm & I2C_DW_TXGBE_MNG_SW_SM)
> > > + break;
> > > +
> > > + udelay(50);
> >
> > So, can a macro from iopoll.h be utilised here? Why not?
>
> I need to write the register first and then read it in this loop.
> It does not seem to apply to the macros in iopoll.h.
I don't see how does it prevent from using read_poll_timeout() macro.
You need to implement a body of the loop as a helper function that you supply
into macro as a parameter.
> > > + }
> > > +
> > > + if (i == I2C_DW_TXGBE_REQ_RETRY_CNT)
> > > + return -ETIMEDOUT;
> > > +
> > > + return 0;
> > > +}
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-08-29 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240823030242.3083528-1-jiawenwu@trustnetic.com>
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' [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=ZtBUlxDWTfwpzm5V@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=duanqiangwen@net-swift.com \
--cc=edumazet@google.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jiawenwu@trustnetic.com \
--cc=jsd@semihalf.com \
--cc=kuba@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mengyuanlou@net-swift.com \
--cc=mika.westerberg@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stable@vger.kernel.org \
/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