From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Ulrich Hecht <uli+renesas@fpond.eu>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Subject: Re: [PATCH v2 3/3] rcar-csi2: Move setting of Field Detection Control Register
Date: Tue, 12 Mar 2019 19:47:42 +0100 [thread overview]
Message-ID: <20190312184742.GD1776@bigcity.dyn.berto.se> (raw)
In-Reply-To: <20190311093910.GK4775@pendragon.ideasonboard.com>
Hi Laurent,
Thanks for your feedback.
On 2019-03-11 11:39:10 +0200, Laurent Pinchart wrote:
> Hi Niklas,
>
> Thank you for the patch.
>
> On Sat, Mar 09, 2019 at 12:57:02AM +0100, Niklas Söderlund wrote:
> > Latest datasheet (rev 1.50) clarifies that the FLD register should be
> > set after LINKCNT.
>
> Wasn't this already the case in rev 1.00 ?
Yes it is, thanks for noticing, will fix for next version.
>
> > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> > Reviewed-by: Ulrich Hecht <uli+renesas@fpond.eu>
> > Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> > ---
> > drivers/media/platform/rcar-vin/rcar-csi2.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/platform/rcar-vin/rcar-csi2.c b/drivers/media/platform/rcar-vin/rcar-csi2.c
> > index 07d5c8c66b7cd382..077e0d344b395b54 100644
> > --- a/drivers/media/platform/rcar-vin/rcar-csi2.c
> > +++ b/drivers/media/platform/rcar-vin/rcar-csi2.c
> > @@ -529,7 +529,6 @@ static int rcsi2_start_receiver(struct rcar_csi2 *priv)
> > rcsi2_write(priv, PHTC_REG, 0);
> >
> > /* Configure */
> > - rcsi2_write(priv, FLD_REG, fld);
> > rcsi2_write(priv, VCDT_REG, vcdt);
> > if (vcdt2)
> > rcsi2_write(priv, VCDT2_REG, vcdt2);
> > @@ -560,6 +559,7 @@ static int rcsi2_start_receiver(struct rcar_csi2 *priv)
> > rcsi2_write(priv, PHYCNT_REG, phycnt);
> > rcsi2_write(priv, LINKCNT_REG, LINKCNT_MONITOR_EN |
> > LINKCNT_REG_MONI_PACT_EN | LINKCNT_ICLK_NONSTOP);
> > + rcsi2_write(priv, FLD_REG, fld);
> > rcsi2_write(priv, PHYCNT_REG, phycnt | PHYCNT_SHUTDOWNZ);
> > rcsi2_write(priv, PHYCNT_REG, phycnt | PHYCNT_SHUTDOWNZ | PHYCNT_RSTZ);
> >
>
> The change looks reasonable, so after updating the commit message,
>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Thanks!
>
> --
> Regards,
>
> Laurent Pinchart
--
Regards,
Niklas Söderlund
next prev parent reply other threads:[~2019-03-12 18:47 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
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 [this message]
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=20190312184742.GD1776@bigcity.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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