mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Martin Kepplinger <martink@posteo.de>, mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: coda: Fix definition of CODA_STD_MJPG
Date: Wed, 08 Nov 2017 16:17:34 +0100	[thread overview]
Message-ID: <1510154254.9225.6.camel@pengutronix.de> (raw)
In-Reply-To: <20171108141247.24824-1-martink@posteo.de>

Hi Martin,

thank you for the patch. I'd prefer to just drop CODA_STD_MJPG
altogether, to avoid confusion. Explanation below:

On Wed, 2017-11-08 at 15:12 +0100, Martin Kepplinger wrote:
> According to i.MX 6 VPU API Reference Manual Rev. L3.0.35_1.1.0, 01/2013
> chapter 3.2.1.5, the MJPG video codec is refernced to by number 7, not 3.
> So change this accordingly.
> 
> This isn't yet being used right now and therefore probably hasn't been
> noticed. Fixing this avoids causing trouble in the future.
> 
> Signed-off-by: Martin Kepplinger <martink@posteo.de>
> ---
>  drivers/media/platform/coda/coda_regs.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/media/platform/coda/coda_regs.h b/drivers/media/platform/coda/coda_regs.h
> index 38df5fd9a2fa..8d726faaf86e 100644
> --- a/drivers/media/platform/coda/coda_regs.h
> +++ b/drivers/media/platform/coda/coda_regs.h
> @@ -254,7 +254,7 @@
>  #define		CODA9_STD_H264					0
>  #define		CODA_STD_H263					1
>  #define		CODA_STD_H264					2
> -#define		CODA_STD_MJPG					3
> +#define		CODA_STD_MJPG					7

These are only ever used to feed them into the CMD_ENC_SEQ_COD_STD
register, and only for MPEG4, H263 (which we don't support), and H264.

On i.MX53 the correct value was 3 once, but it was only used in the
userspace library, it was never written to any register. On i.MX6 JPEG
encoding can be implemented without going through the BIT processor at
all.

regards
Philipp

      reply	other threads:[~2017-11-08 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 14:12 Martin Kepplinger
2017-11-08 15:17 ` Philipp Zabel [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=1510154254.9225.6.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=martink@posteo.de \
    --cc=mchehab@kernel.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

all inboxes | Powered by JetHome®