mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Eugen.Hristev@microchip.com
Cc: akinobu.mita@gmail.com, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, jacopo@jmondi.org
Subject: Re: [PATCH] media: i2c: ov7740: implement get_mbus_config
Date: Wed, 3 Nov 2021 16:17:21 +0200	[thread overview]
Message-ID: <YYKZ8emK6JrE4pyr@paasikivi.fi.intel.com> (raw)
In-Reply-To: <84ff4389-3458-0811-b43f-ded957c01f88@microchip.com>

On Wed, Nov 03, 2021 at 12:39:52PM +0000, Eugen.Hristev@microchip.com wrote:
> On 11/3/21 10:08 AM, Sakari Ailus wrote:
> > Hi Eugen,
> > 
> > Thanks for the patch.
> > 
> > On Tue, Nov 02, 2021 at 05:30:08PM +0200, Eugen Hristev wrote:
> >> Implement the get_mbus_config callback.
> >> ov7740 is a parallel sensor, and according to datasheet, the register
> >> REG12 controls the CCIR656 mode. This register is written to 0 in yuyv mode.
> >> According to REG12[5] , CCIR656 mode, the behavior is:
> >> CCIR656: disabled
> >> REG28 controls the polarity of the signals. This register is unused.
> >> The default behavior is then:
> >> HSYNC polarity : positive
> >> VSYNC polarity : positive
> >> HREF polarity: positive
> >>
> > 
> > Doesn't the receiver driver get this information from DT?
> > 
> 
> Hi Sakari,
> 
> This patch comes as a result of my discussions with Jacopo, he advised 
> to get mbus configuration via the get_mbus_config . I agree that this 
> information can be taken from DT as you said.
> In the end , my understanding is that get_mbus_config should be used 
> only for runtime configuration which can change.
> Thus, if all this information is static, then, I will proceed with 
> obtaining it from DT, and you can disregard this patch, as it is not useful.

Yes, please.

Getting this from DT is preferred if no dynamic configuration is needed.

-- 
Sakari Ailus

      parent reply	other threads:[~2021-11-03 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 15:30 Eugen Hristev
2021-11-03  8:08 ` Sakari Ailus
2021-11-03 12:39   ` Eugen.Hristev
2021-11-03 13:46     ` Jacopo Mondi
2021-11-03 14:17     ` Sakari Ailus [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=YYKZ8emK6JrE4pyr@paasikivi.fi.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=Eugen.Hristev@microchip.com \
    --cc=akinobu.mita@gmail.com \
    --cc=jacopo@jmondi.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.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®