linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Alex Elder <elder@linaro.org>, davem@davemloft.net, kuba@kernel.org
Cc: bjorn.andersson@linaro.org, evgreen@chromium.org,
	cpratapa@codeaurora.org, subashab@codeaurora.org,
	elder@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/4] net: ipa: introduce dma_addr_high32()
Date: Wed, 17 Mar 2021 15:47:47 -0700	[thread overview]
Message-ID: <36b9977b-32b1-eb4a-0056-4f742e3fe4d6@gmail.com> (raw)
In-Reply-To: <20210317222946.118125-3-elder@linaro.org>



On 3/17/2021 3:29 PM, Alex Elder wrote:
> Create a new helper function to encapsulate extracting the
> high-order 32 bits of a DMA address.  It returns 0 for builds
> in which a DMA address is not 64 bits.
> 
> This avoids doing a 32-position shift on a DMA address if it
> happens not to be 64 bits wide.
> 
> Signed-off-by: Alex Elder <elder@linaro.org>
> ---
>  drivers/net/ipa/gsi.c | 14 ++++++++++++--
>  1 file changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/ipa/gsi.c b/drivers/net/ipa/gsi.c
> index 2119367b93ea9..53698c64cf882 100644
> --- a/drivers/net/ipa/gsi.c
> +++ b/drivers/net/ipa/gsi.c
> @@ -688,6 +688,16 @@ static void gsi_evt_ring_doorbell(struct gsi *gsi, u32 evt_ring_id, u32 index)
>  	iowrite32(val, gsi->virt + GSI_EV_CH_E_DOORBELL_0_OFFSET(evt_ring_id));
>  }
>  
> +/* Encapsulate extracting high-order 32 bits of DMA address */
> +static u32 dma_addr_high32(dma_addr_t addr)
> +{
> +#ifdef CONFIG_ARCH_DMA_ADDR_T_64BIT
> +	return (u32)(addr >> 32);

You can probably use upper_32bits() here...

> +#else /* !CONFIG_ARCH_DMA_ADDR_T_64BIT */
> +	return 0;
> +#endif /* !CONFIG_ARCH_DMA_ADDR_T_64BIT */
> +}
> +
>  /* Program an event ring for use */
>  static void gsi_evt_ring_program(struct gsi *gsi, u32 evt_ring_id)
>  {
> @@ -711,7 +721,7 @@ static void gsi_evt_ring_program(struct gsi *gsi, u32 evt_ring_id)
>  	val = evt_ring->ring.addr & GENMASK(31, 0);

...and you can use lower_32bits() here.

>  	iowrite32(val, gsi->virt + GSI_EV_CH_E_CNTXT_2_OFFSET(evt_ring_id));
>  
> -	val = evt_ring->ring.addr >> 32;
> +	val = dma_addr_high32(evt_ring->ring.addr);

Does the compiler do a good job at eliminating the assignment when
CONFIG_ARCH_DMA_ADDR_T_64BIT is not defined?

>  	iowrite32(val, gsi->virt + GSI_EV_CH_E_CNTXT_3_OFFSET(evt_ring_id));
>  
>  	/* Enable interrupt moderation by setting the moderation delay */
> @@ -819,7 +829,7 @@ static void gsi_channel_program(struct gsi_channel *channel, bool doorbell)
>  	val = channel->tre_ring.addr & GENMASK(31, 0);
>  	iowrite32(val, gsi->virt + GSI_CH_C_CNTXT_2_OFFSET(channel_id));
>  
> -	val = channel->tre_ring.addr >> 32;
> +	val = dma_addr_high32(channel->tre_ring.addr);
>  	iowrite32(val, gsi->virt + GSI_CH_C_CNTXT_3_OFFSET(channel_id));
>  
>  	/* Command channel gets low weighted round-robin priority */
> 

-- 
Florian

  reply	other threads:[~2021-03-17 22:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 22:29 [PATCH net-next 0/4] net: ipa: support 32-bit targets Alex Elder
2021-03-17 22:29 ` [PATCH net-next 1/4] net: ipa: fix assumptions about DMA address size Alex Elder
2021-03-17 22:29 ` [PATCH net-next 2/4] net: ipa: introduce dma_addr_high32() Alex Elder
2021-03-17 22:47   ` Florian Fainelli [this message]
2021-03-17 22:49     ` Alex Elder
2021-03-17 23:00       ` Florian Fainelli
2021-03-18 13:33         ` Alex Elder
2021-03-17 22:29 ` [PATCH net-next 3/4] net: ipa: fix table alignment requirement Alex Elder
2021-03-17 22:29 ` [PATCH net-next 4/4] net: ipa: relax 64-bit build requirement Alex Elder

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=36b9977b-32b1-eb4a-0056-4f742e3fe4d6@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=cpratapa@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=elder@kernel.org \
    --cc=elder@linaro.org \
    --cc=evgreen@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=subashab@codeaurora.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).