mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>,
	barebox@lists.infradead.org
Subject: Re: [PATCH v3 2/2] net: macb: convert to volatile accesses
Date: Wed, 29 Nov 2023 13:03:11 +0100	[thread overview]
Message-ID: <7b717a50-8d5a-4bc5-9a2a-6b6f0216ca55@pengutronix.de> (raw)
In-Reply-To: <20231129-v2023-08-0-topic-macb-v3-2-65ad6db834dc@pengutronix.de>

Hi,

On 29.11.23 12:33, Steffen Trumtrar wrote:
>  		dma_sync_single_for_cpu(macb->dev,
>  					macb->rx_buffer_phys + macb->rx_buffer_size * macb->rx_tail,
>  					length,	DMA_FROM_DEVICE);
> @@ -198,6 +190,7 @@ static int gem_recv(struct eth_device *edev)
>  		dma_sync_single_for_device(macb->dev,
>  					   macb->rx_buffer_phys + macb->rx_buffer_size * macb->rx_tail,
>  					   length, DMA_FROM_DEVICE);
> +		clrbits_le32(&macb->rx_ring[macb->rx_tail].addr, MACB_BIT(RX_USED));

This is being moved around in the previous patch and moved back here, so that move
seems to have been unintentional.

By the way, did you see my comment about increasing PKTSIZE to be a multiple
of 64 bytes?

Thanks,
Ahmad

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




      reply	other threads:[~2023-11-29 12:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 11:33 [PATCH v3 0/2] net: macb: fix dma usage Steffen Trumtrar
2023-11-29 11:33 ` [PATCH v3 1/2] net: macb: fix dma_alloc for rx_buffer Steffen Trumtrar
2023-11-29 11:59   ` Ahmad Fatoum
2023-11-29 11:33 ` [PATCH v3 2/2] net: macb: convert to volatile accesses Steffen Trumtrar
2023-11-29 12:03   ` Ahmad Fatoum [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=7b717a50-8d5a-4bc5-9a2a-6b6f0216ca55@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.trumtrar@pengutronix.de \
    /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