linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: mx27_3ds: Add VPU support
Date: Wed, 14 Nov 2012 15:34:00 +0100	[thread overview]
Message-ID: <20121114143400.GM10369@pengutronix.de> (raw)
In-Reply-To: <1352899174-28022-1-git-send-email-fabio.estevam@freescale.com>

Hi Fabio,

On Wed, Nov 14, 2012 at 11:19:33AM -0200, Fabio Estevam wrote:
> mx27 has a VPU (Video Processing Unit) block that allows doing H264/MPEG4
> decoding and encoding in hardware.
> 
> Add support for it.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> Changes since v1:
> - Do not allocate the coda buffers explicetely
> 
>  arch/arm/mach-imx/mach-mx27_3ds.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/mach-imx/mach-mx27_3ds.c b/arch/arm/mach-imx/mach-mx27_3ds.c
> index d0e547f..e37a114 100644
> --- a/arch/arm/mach-imx/mach-mx27_3ds.c
> +++ b/arch/arm/mach-imx/mach-mx27_3ds.c
> @@ -531,6 +531,7 @@ static void __init mx27pdk_init(void)
>  	imx27_add_imx_ssi(0, &mx27_3ds_ssi_pdata);
>  
>  	imx_add_platform_device("imx_mc13783", 0, NULL, 0, NULL, 0);
> +	imx27_add_coda();

Why in the board? It's always present so I would register it in the SoC.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  parent reply	other threads:[~2012-11-14 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 13:19 [PATCH v2 1/2] ARM: mx27_3ds: Add VPU support Fabio Estevam
2012-11-14 13:19 ` [PATCH v2 2/2] ARM: imx_v4_v5_defconfig: " Fabio Estevam
2012-11-14 14:34 ` Sascha Hauer [this message]
2012-11-14 15:44   ` [PATCH v2 1/2] ARM: mx27_3ds: " Eric Bénard

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=20121114143400.GM10369@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).