linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH] media: fdp1: Support M3N and E3 platforms
Date: Thu, 16 May 2019 13:36:36 +0300	[thread overview]
Message-ID: <20190516103636.GF4995@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20190515153912.5182-1-kieran.bingham+renesas@ideasonboard.com>

Hi Kieran,

Thank you for the patch.

On Wed, May 15, 2019 at 04:39:12PM +0100, Kieran Bingham wrote:
> New Gen3 R-Car platforms incorporate the FDP1 with an updated version
> register. No code change is required to support these targets, but they
> will currently report an error stating that the device can not be
> identified.
> 
> Update the driver to match against the new device types.
> 
> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>

Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

and applied to my tree.

> ---
>  drivers/media/platform/rcar_fdp1.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/media/platform/rcar_fdp1.c b/drivers/media/platform/rcar_fdp1.c
> index 6bda1eee9170..4f103be215d3 100644
> --- a/drivers/media/platform/rcar_fdp1.c
> +++ b/drivers/media/platform/rcar_fdp1.c
> @@ -257,6 +257,8 @@ MODULE_PARM_DESC(debug, "activate debug info");
>  #define FD1_IP_H3_ES1			0x02010101
>  #define FD1_IP_M3W			0x02010202
>  #define FD1_IP_H3			0x02010203
> +#define FD1_IP_M3N			0x02010204
> +#define FD1_IP_E3			0x02010205
>  
>  /* LUTs */
>  #define FD1_LUT_DIF_ADJ			0x1000
> @@ -2365,6 +2367,12 @@ static int fdp1_probe(struct platform_device *pdev)
>  	case FD1_IP_H3:
>  		dprintk(fdp1, "FDP1 Version R-Car H3\n");
>  		break;
> +	case FD1_IP_M3N:
> +		dprintk(fdp1, "FDP1 Version R-Car M3N\n");
> +		break;
> +	case FD1_IP_E3:
> +		dprintk(fdp1, "FDP1 Version R-Car E3\n");
> +		break;
>  	default:
>  		dev_err(fdp1->dev, "FDP1 Unidentifiable (0x%08x)\n",
>  				hw_version);

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2019-05-16 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 15:39 [PATCH] media: fdp1: Support M3N and E3 platforms Kieran Bingham
2019-05-16 10:36 ` Laurent Pinchart [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=20190516103636.GF4995@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).