From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Ulrich Hecht <uli+renesas@fpond.eu>
Subject: Re: [PATCH v2 1/3] rcar-csi2: Update V3M and E3 start procedure
Date: Mon, 11 Mar 2019 11:29:02 +0200 [thread overview]
Message-ID: <20190311092902.GJ4775@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20190308235702.27057-2-niklas.soderlund+renesas@ragnatech.se>
Hi Niklas,
Thank you for the patch.
On Sat, Mar 09, 2019 at 12:57:00AM +0100, Niklas Söderlund wrote:
> The latest datasheet (rev 1.50) updates the start procedure for V3M and
> E3. Update the driver to match these changes.
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> Reviewed-by: Ulrich Hecht <uli+renesas@fpond.eu>
This matches the datasheet, so
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> drivers/media/platform/rcar-vin/rcar-csi2.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/media/platform/rcar-vin/rcar-csi2.c b/drivers/media/platform/rcar-vin/rcar-csi2.c
> index d9b29dbbcc2949de..6be81d4839f35a0e 100644
> --- a/drivers/media/platform/rcar-vin/rcar-csi2.c
> +++ b/drivers/media/platform/rcar-vin/rcar-csi2.c
> @@ -922,11 +922,11 @@ static int rcsi2_init_phtw_v3m_e3(struct rcar_csi2 *priv, unsigned int mbps)
> static int rcsi2_confirm_start_v3m_e3(struct rcar_csi2 *priv)
> {
> static const struct phtw_value step1[] = {
> - { .data = 0xed, .code = 0x34 },
> - { .data = 0xed, .code = 0x44 },
> - { .data = 0xed, .code = 0x54 },
> - { .data = 0xed, .code = 0x84 },
> - { .data = 0xed, .code = 0x94 },
> + { .data = 0xee, .code = 0x34 },
> + { .data = 0xee, .code = 0x44 },
> + { .data = 0xee, .code = 0x54 },
> + { .data = 0xee, .code = 0x84 },
> + { .data = 0xee, .code = 0x94 },
> { /* sentinel */ },
> };
>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2019-03-11 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 23:56 [PATCH v2 0/3] rcar-csi2: Update start procedures to latest revision of datasheet Niklas Söderlund
2019-03-08 23:57 ` [PATCH v2 1/3] rcar-csi2: Update V3M and E3 start procedure Niklas Söderlund
2019-03-11 9:29 ` Laurent Pinchart [this message]
2019-03-08 23:57 ` [PATCH v2 2/3] rcar-csi2: Update start procedure for H3 ES2 Niklas Söderlund
2019-03-11 9:27 ` Laurent Pinchart
2019-03-12 18:44 ` Niklas Söderlund
2019-03-08 23:57 ` [PATCH v2 3/3] rcar-csi2: Move setting of Field Detection Control Register Niklas Söderlund
2019-03-11 9:39 ` Laurent Pinchart
2019-03-12 18:47 ` Niklas Söderlund
2019-04-10 13:59 ` Hans Verkuil
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=20190311092902.GJ4775@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=uli+renesas@fpond.eu \
/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