From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 1/2] net: fec_mxc: Adjust RX DMA alignment for mx6solox
Date: Sat, 30 Aug 2014 15:21:32 -0400 [thread overview]
Message-ID: <20140830192132.GY19374@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5C2EZDPE679KtMii8NPLKccKDG9-0ALgzjZLPCXw+7ueg@mail.gmail.com>
On Sat, Aug 30, 2014 at 02:22:22PM -0300, Fabio Estevam wrote:
> Tom, Joe or Stefano,
>
> On Mon, Aug 25, 2014 at 4:51 PM, Marek Vasut <marex@denx.de> wrote:
> > On Monday, August 25, 2014 at 06:34:16 PM, Fabio Estevam wrote:
> >> 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: Marek Vasut <marex@denx.de>
>
> Could this one be applied for 2014.10-rc?
I'd like this via the imx tree.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140830/3341cdf0/attachment.pgp>
next prev parent reply other threads:[~2014-08-30 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 16:34 [U-Boot] [PATCH v7 1/2] net: fec_mxc: Adjust RX DMA alignment for mx6solox Fabio Estevam
2014-08-25 16:34 ` [U-Boot] [PATCH v7 2/2] net: fec_mxc: Poll FEC_TBD_READY after polling TDAR Fabio Estevam
2014-08-25 19:51 ` Marek Vasut
2014-09-09 13:10 ` Stefano Babic
2014-08-25 19:51 ` [U-Boot] [PATCH v7 1/2] net: fec_mxc: Adjust RX DMA alignment for mx6solox Marek Vasut
2014-08-30 17:22 ` Fabio Estevam
2014-08-30 19:21 ` Tom Rini [this message]
2014-09-08 23:52 ` Fabio Estevam
2014-09-09 13:09 ` Stefano Babic
2014-09-09 13:37 ` Fabio Estevam
2014-09-03 22:21 ` 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=20140830192132.GY19374@bill-the-cat \
--to=trini@ti.com \
--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