linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>, <mugunthanvnm@ti.com>
Cc: <linux-omap@vger.kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: ethernet: ti: cpdma: use desc_read in chan_process instead of raw read
Date: Mon, 5 Dec 2016 12:47:16 -0600	[thread overview]
Message-ID: <ed16f5d1-8e5b-470f-1566-4129eef47ee1@ti.com> (raw)
In-Reply-To: <1480730715-16000-1-git-send-email-ivan.khoronzhuk@linaro.org>



On 12/02/2016 08:05 PM, Ivan Khoronzhuk wrote:
> There is desc_read() macros to read desc fields, so no need to
> use __raw_readl();
>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>


I'm going to update it all at once as part of [1].

[1] https://lkml.org/lkml/2016/12/1/781

> ---
> Based on net-next/master
>
>  drivers/net/ethernet/ti/davinci_cpdma.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/ti/davinci_cpdma.c b/drivers/net/ethernet/ti/davinci_cpdma.c
> index c776e45..d96dca5 100644
> --- a/drivers/net/ethernet/ti/davinci_cpdma.c
> +++ b/drivers/net/ethernet/ti/davinci_cpdma.c
> @@ -1132,7 +1132,7 @@ static int __cpdma_chan_process(struct cpdma_chan *chan)
>  	}
>  	desc_dma = desc_phys(pool, desc);
>
> -	status	= __raw_readl(&desc->hw_mode);
> +	status = desc_read(desc, hw_mode);
>  	outlen	= status & 0x7ff;
>  	if (status & CPDMA_DESC_OWNER) {
>  		chan->stats.busy_dequeue++;
>

-- 
regards,
-grygorii

  reply	other threads:[~2016-12-05 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03  2:05 [PATCH] net: ethernet: ti: cpdma: use desc_read in chan_process instead of raw read Ivan Khoronzhuk
2016-12-05 18:47 ` Grygorii Strashko [this message]
2016-12-05 19:47   ` David Miller

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=ed16f5d1-8e5b-470f-1566-4129eef47ee1@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc=ivan.khoronzhuk@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mugunthanvnm@ti.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).