linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Jagan Teki <jagan@amarulasolutions.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media <linux-media@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: Michael Trimarchi <michael@amarulasolutions.com>
Subject: Re: Configure video PAL decoder into media pipeline
Date: Fri, 7 Dec 2018 13:11:33 +0100	[thread overview]
Message-ID: <850c2502-217c-a9f0-b433-0cd26d0419fd@xs4all.nl> (raw)
In-Reply-To: <CAMty3ZAa2_o87YJ=1iak-o-rfZjoYz7PKXM9uGrbHsh6JLOCWw@mail.gmail.com>

On 12/07/2018 12:51 PM, Jagan Teki wrote:
> Hi,
> 
> We have some unconventional setup for parallel CSI design where analog
> input data is converted into to digital composite using PAL decoder
> and it feed to adv7180, camera sensor.
> 
> Analog input =>  Video PAL Decoder => ADV7180 => IPU-CSI0

Just PAL? No NTSC support?

> 
> The PAL decoder is I2C based, tda9885 chip. We setup it up via dt
> bindings and the chip is
> detected fine.
> 
> But we need to know, is this to be part of media control subdev
> pipeline? so-that we can configure pads, links like what we do on
> conventional pipeline  or it should not to be part of media pipeline?

Yes, I would say it should be part of the pipeline.

> 
> Please advise for best possible way to fit this into the design.
> 
> Another observation is since the IPU has more than one sink, source
> pads, we source or sink the other components on the pipeline but look
> like the same thing seems not possible with adv7180 since if has only
> one pad. If it has only one pad sourcing to adv7180 from tda9885 seems
> not possible, If I'm not mistaken.

Correct, in all cases where the adv7180 is used it is directly connected
to the video input connector on a board.

So to support this the adv7180 driver should be modified to add an input pad
so you can connect the decoder. It will be needed at some point anyway once
we add support for connector entities.

Regards,

	Hans

> 
> I tried to look for similar design in mainline, but I couldn't find
> it. is there any design similar to this in mainline?
> 
> Please let us know if anyone has any suggestions on this.
> 
> Jagan.
> 


  reply	other threads:[~2018-12-07 12:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 11:51 Configure video PAL decoder into media pipeline Jagan Teki
2018-12-07 12:11 ` Hans Verkuil [this message]
2018-12-08 11:48   ` Michael Nazzareno Trimarchi
2018-12-08 17:07     ` Michael Nazzareno Trimarchi
2018-12-09 19:39       ` jacopo mondi
2018-12-09 20:06         ` Michael Nazzareno Trimarchi
2018-12-10 21:45         ` Michael Nazzareno Trimarchi
2018-12-11 11:39           ` jacopo mondi
2018-12-11 13:53             ` Michael Nazzareno Trimarchi
2018-12-12  8:39               ` jacopo mondi
2018-12-12  8:43                 ` Michael Nazzareno Trimarchi
2018-12-12  8:54                   ` jacopo mondi
2018-12-12  9:09                     ` Michael Nazzareno Trimarchi

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=850c2502-217c-a9f0-b433-0cd26d0419fd@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=jagan@amarulasolutions.com \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=michael@amarulasolutions.com \
    --cc=p.zabel@pengutronix.de \
    /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).