From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: Michael Rodin <mrodin@de.adit-jv.com>,
mchehab@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, michael@rodin.online,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] media: i2c: adv748x: initialize bit 7 of csi_tx_top_reg_1f
Date: Fri, 10 May 2019 21:01:24 +0200 [thread overview]
Message-ID: <20190510190124.GE28561@bigcity.dyn.berto.se> (raw)
In-Reply-To: <26e001a0-298f-e23b-9e46-98e62a8399c2@ideasonboard.com>
Hi Kieran and Michael,
On 2019-05-10 17:25:24 +0100, Kieran Bingham wrote:
<snip>
>
> Niklas, how does RCar-CSI determine the top/bottom sequence?
That patch just got merged in the media tree a few days ago,
9f7983bdc4925ae2 ("media: rcar-csi2: Propagate the FLD signal for NTSC and PAL")
>
> Do we have field inversion currently? (or one which is perhaps swapped
> somewhere along the pipeline in rcar-vin?)
>
I'm not sure which tree this patch is developed on but Steve Longerbeam
posted a RFC which IMHO had the fields inverted, there was a discussion
in his thread [1] where I tried to get to the bottom of the issue. My
conclusions there might be wrong due to the issues addressed in this
patch.
Michael: Did you have Steve's patch in your tree when testing this?
1. https://patchwork.kernel.org/patch/10904263/
--
Regards,
Niklas Söderlund
next prev parent reply other threads:[~2019-05-10 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 15:30 Michael Rodin
2019-05-10 16:25 ` Kieran Bingham
2019-05-10 19:01 ` Niklas Söderlund [this message]
2019-05-16 14:24 ` Rodin, Michael (Ferchau; ADITG/ESM1)
2019-05-16 20:44 ` niklas.soderlund
-- strict thread matches above, loose matches on Subject: below --
2019-05-10 15:26 Michael Rodin
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=20190510190124.GE28561@bigcity.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michael@rodin.online \
--cc=mrodin@de.adit-jv.com \
/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®