netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Jose.Abreu@synopsys.com
Cc: netdev@vger.kernel.org, Joao.Pinto@synopsys.com
Subject: Re: [PATCH net-next 01/12] net: stmmac: Get correct timestamp values from XGMAC
Date: Fri, 09 Aug 2019 12:43:27 -0700 (PDT)	[thread overview]
Message-ID: <20190809.124327.1282600811774499704.davem@davemloft.net> (raw)
In-Reply-To: <7acdee903b01dd5462f687c31163628cefa0e372.1565375521.git.joabreu@synopsys.com>

From: Jose Abreu <Jose.Abreu@synopsys.com>
Date: Fri,  9 Aug 2019 20:36:09 +0200

> +	void __iomem *ioaddr = hw->pcsr;
> +	int count = 0;
> +	u32 value;
> +
> +	do {
> +		if (readl_poll_timeout_atomic(ioaddr + XGMAC_TIMESTAMP_STATUS,
> +					      value, value & XGMAC_TXTSC,
> +					      100, 10000))
> +			break;
> +
> +		*ts = readl(ioaddr + XGMAC_TXTIMESTAMP_NSEC) & XGMAC_TXTSSTSLO;
> +		*ts += readl(ioaddr + XGMAC_TXTIMESTAMP_SEC) * 1000000000ULL;
> +	} while (count++);
> +
> +	if (count)
> +		return 0;
> +	return -EBUSY;

This is a very strange construct, the loop never executes more than once.
Simplified it is essentially:

	if (readl_poll_timeout_atomic(ioaddr + XGMAC_TIMESTAMP_STATUS,
				      value, value & XGMAC_TXTSC,
				      100, 10000))
		return -EBUSY;

	*ts = readl(ioaddr + XGMAC_TXTIMESTAMP_NSEC) & XGMAC_TXTSSTSLO;
	*ts += readl(ioaddr + XGMAC_TXTIMESTAMP_SEC) * 1000000000ULL;
	return 0;

Don't make the code more complicated than it needs to be, there is no
reason to use a loop here.  And using a loop makes it look like the
loop is the polling/timeout construct, when it isn't, because
readl_poll_timeout_atomic() is serving that purpose.


  reply	other threads:[~2019-08-09 19:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 18:36 [PATCH net-next 00/12] net: stmmac: Improvements for -next Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 01/12] net: stmmac: Get correct timestamp values from XGMAC Jose Abreu
2019-08-09 19:43   ` David Miller [this message]
2019-08-09 18:36 ` [PATCH net-next 02/12] net: stmmac: Prepare to add Split Header support Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 03/12] net: stmmac: xgmac: Correctly return that RX descriptor is not last one Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 04/12] net: stmmac: Add Split Header support and enable it in XGMAC cores Jose Abreu
2019-08-09 19:44   ` David Miller
2019-08-09 18:36 ` [PATCH net-next 05/12] net: stmmac: Add a counter for Split Header packets Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 06/12] net: stmmac: dwxgmac: Add Flexible PPS support Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 07/12] net: stmmac: Add ethtool register dump for XGMAC cores Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 08/12] net: stmmac: Add support for SA Insertion/Replacement in " Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 09/12] net: stmmac: selftests: Add tests for SA Insertion/Replacement Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 10/12] net: stmmac: xgmac: Add EEE support Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 11/12] net: stmmac: Add support for VLAN Insertion Offload Jose Abreu
2019-08-09 18:36 ` [PATCH net-next 12/12] net: stmmac: selftests: Add selftest for VLAN TX Offload Jose Abreu

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=20190809.124327.1282600811774499704.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Joao.Pinto@synopsys.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).