Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sdma-imx: Add SDMA firmware for Freescale i.MX SOCs
Date: Thu, 17 Jan 2013 21:50:31 +0800	[thread overview]
Message-ID: <20130117135028.GA29285@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <1358424987-22312-1-git-send-email-fabio.estevam@freescale.com>

Hi Fabio,

On Thu, Jan 17, 2013 at 10:16:27AM -0200, Fabio Estevam wrote:
> Add SDMA firmware for Freescale i.MX SOCs.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  LICENCE.fsl_firmware        |  140 +++++++++++++++++++++++++++++++++++++++++++
>  WHENCE                      |   13 ++++
>  imx/sdma/sdma-imx25-to1.bin |  Bin 0 -> 694 bytes
>  imx/sdma/sdma-imx31-to2.bin |  Bin 0 -> 3762 bytes
>  imx/sdma/sdma-imx35-to2.bin |  Bin 0 -> 1746 bytes
>  imx/sdma/sdma-imx51.bin     |  Bin 0 -> 1894 bytes
>  imx/sdma/sdma-imx53.bin     |  Bin 0 -> 1406 bytes
>  imx/sdma/sdma-imx6q-to1.bin |  Bin 0 -> 1838 bytes

Can we have a consistent name schema?  If we want to have a "tox"
suffix, we should give one for imx51 and imx53 too.  Or we remove
the suffix for everyone else based on the fact that we will only
upload the firmware for production revision.

I'm fine with either way.  Just want to see them be named consistently.

Shawn

  reply	other threads:[~2013-01-17 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 12:16 [PATCH] sdma-imx: Add SDMA firmware for Freescale i.MX SOCs Fabio Estevam
2013-01-17 13:50 ` Shawn Guo [this message]
2013-01-17 14:38 ` Uwe Kleine-König
2013-01-17 14:58   ` Fabio Estevam
2013-01-17 15:16     ` Uwe Kleine-König
2013-01-21  1:38 ` Ben Hutchings

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=20130117135028.GA29285@S2101-09.ap.freescale.net \
    --to=shawn.guo@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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