public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6 1/2] net: fec_mxc: Adjust RX DMA alignment for mx6solox
Date: Mon, 25 Aug 2014 10:02:59 +0200	[thread overview]
Message-ID: <201408251002.59801.marex@denx.de> (raw)
In-Reply-To: <1408797711-3700-1-git-send-email-festevam@gmail.com>

On Saturday, August 23, 2014 at 02:41:50 PM, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
> 
> mx6solox has a requirement for 64 bytes alignment for RX DMA transfer.
> Other SoCs work with the standard 32 bytes alignment.
> 
> Adjust it accordingly by using 64 bytes aligment in the FEC RX DMA buffers,
> which addresses the needs from mx6solox and also works for the other SoCs.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> Acked-by: Stefan Roese <sr@denx.de>
> ---
> Changes since v5:
> - Add Stefan's Ack
> Changes since v4:
> - None
> 
>  drivers/net/fec_mxc.c | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c
> index 4cefda4..56178d4 100644
> --- a/drivers/net/fec_mxc.c
> +++ b/drivers/net/fec_mxc.c
> @@ -28,6 +28,14 @@ DECLARE_GLOBAL_DATA_PTR;
>   */
>  #define FEC_XFER_TIMEOUT	5000
> 
> +/*
> + * The standard 32-byte DMA alignment does not work on mx6solox, which
> requires + * 64-byte alignment in the DMA RX FEC buffer.
> + * Introduce the FEC_DMA_RX_MINALIGN which can cover mx6solox needs and
> also + * satisfies the alignment on other SoCs (32-bytes)
> + */
> +#define FEC_DMA_RX_MINALIGN	64
> +
>  #ifndef CONFIG_MII
>  #error "CONFIG_MII has to be defined!"
>  #endif
> @@ -286,7 +294,7 @@ static void fec_rbd_init(struct fec_priv *fec, int
> count, int dsize) * Reload the RX descriptors with default values and wipe
>  	 * the RX buffers.
>  	 */
> -	size = roundup(dsize, ARCH_DMA_MINALIGN);
> +	size = roundup(dsize, FEC_DMA_RX_MINALIGN);

This $size here is used only by the cache flushing functions. We agreed in the 
previous iterations, that the cacheline is 32b on MX6SX . This change is 
pointless unless ARCH_DMA_MINALIGN != 32 on MX6SX. Is that right ?
[...]

Best regards,
Marek Vasut

  parent reply	other threads:[~2014-08-25  8:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23 12:41 [U-Boot] [PATCH v6 1/2] net: fec_mxc: Adjust RX DMA alignment for mx6solox Fabio Estevam
2014-08-23 12:41 ` [U-Boot] [PATCH v6 2/2] net: fec_mxc: Poll FEC_TBD_READY after polling TDAR Fabio Estevam
2014-08-25  8:02 ` Marek Vasut [this message]
2014-08-25 14:16   ` [U-Boot] [PATCH v6 1/2] net: fec_mxc: Adjust RX DMA alignment for mx6solox Fabio Estevam

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=201408251002.59801.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.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