All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Towle <william.towle@codethink.co.uk>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: William Towle <william.towle@codethink.co.uk>,
	linux-kernel@lists.codethink.co.uk, linux-media@vger.kernel.org
Subject: Re: [Linux-kernel] RFC: supporting adv7604.c under soc_camera/rcar_vin
Date: Thu, 5 Mar 2015 08:58:11 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1503050847040.4771@xk120.dyn.ducie.codethink.co.uk> (raw)
In-Reply-To: <54F6DC4F.6040504@xs4all.nl>



On Wed, 4 Mar 2015, Hans Verkuil wrote:
> On 03/04/15 10:51, William Towle wrote:
>>     if (timings->pad >= state->source_pad)
>>             return -EINVAL;
>>   It suffices to comment out this line, but clearly this is not ideal.
>> Depending on the intended semantics, should it be filtering out all pad
>> IDs not matching the active one, or all pad IDs that are not valid
>> input sources? Unfortunately the lager board's adv7180 chip is too
>> simple to make a sensible comparison case (that we can also run tests
>> on) here.
>
> The adv7604 code is not ideal, although the pad test is valid (you shouldn't
> be able to ask timings for pads that do not exist).

   Right, thanks. It seems I have initialisation code that is making
inappropriate assumptions earlier on. I'll investigate this.


>>   Please advise. Comments would also be welcome regarding whether the
>> shims describe changes that should live in the driver or elsewhere in
>> soc_camera/rcar_vin in an acceptable solution.
>
> I'm not entirely sure what it is you are referring to.

   Amongst our various modifications to soc_camera/rcar_vin we have a
'struct media_pad' object in order to communicate with the adv7604
driver, and latterly an array of 'struct v4l2_subdev_pad_config's to
handle format information ... but there is more to be done, obviously,
and you have pointed us in the right direction above :)

Cheers,
   Wills.

  reply	other threads:[~2015-03-05  8:58 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 16:19 RFC: supporting adv7604.c under soc_camera/rcar_vin William Towle
2015-01-29 16:19 ` [PATCH 1/8] Add ability to read default input port from DT William Towle
2015-01-29 20:19   ` Jean-Michel Hautbois
2015-01-29 16:19 ` [PATCH 2/8] adv7604.c: formats, default colourspace, and IRQs William Towle
2015-01-29 16:19 ` [PATCH 3/8] WmT: document "adi,adv7612" William Towle
2015-01-29 16:19 ` [PATCH 4/8] WmT: m-5mols_core style pad handling for adv7604 William Towle
2015-01-29 20:23   ` Jean-Michel Hautbois
2015-02-04 14:14     ` William Towle
2015-02-04 14:40       ` Hans Verkuil
2015-01-29 16:19 ` [PATCH 5/8] media: rcar_vin: Add RGB888_1X24 input format support William Towle
2015-01-29 17:05   ` Sergei Shtylyov
2015-01-29 18:18     ` Guennadi Liakhovetski
2015-01-29 18:28       ` Sergei Shtylyov
2015-01-29 20:19         ` Guennadi Liakhovetski
2015-01-29 20:36           ` Sergei Shtylyov
2015-01-29 20:57             ` Guennadi Liakhovetski
2015-01-29 21:11               ` Guennadi Liakhovetski
2015-02-01 18:29   ` Guennadi Liakhovetski
2015-01-29 16:19 ` [PATCH 6/8] WmT: adv7604 driver compatibility William Towle
2015-01-31 23:56   ` Guennadi Liakhovetski
2015-02-01 11:26     ` Guennadi Liakhovetski
2015-02-02 10:01       ` Laurent Pinchart
2015-02-02 10:09         ` Hans Verkuil
2015-02-03 15:22           ` Laurent Pinchart
2015-02-03 15:24             ` Hans Verkuil
2015-02-03 15:29               ` Lars-Peter Clausen
2015-02-03 15:56                 ` Laurent Pinchart
2015-02-03 15:55               ` Laurent Pinchart
2015-01-29 16:19 ` [PATCH 7/8] WmT: rcar_vin new ADV7612 support William Towle
2015-02-01 11:44   ` Guennadi Liakhovetski
2015-01-29 16:19 ` [PATCH 8/8] WmT: dts/i vin0/adv7612 (HDMI) William Towle
2015-01-29 16:51   ` Sergei Shtylyov
2015-02-01 15:51 ` RFC: supporting adv7604.c under soc_camera/rcar_vin Guennadi Liakhovetski
2015-03-04  9:51 ` [Linux-kernel] " William Towle
2015-03-04 10:19   ` Hans Verkuil
2015-03-05  8:58     ` William Towle [this message]
2015-03-25  9:55   ` William Towle

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=alpine.DEB.2.02.1503050847040.4771@xk120.dyn.ducie.codethink.co.uk \
    --to=william.towle@codethink.co.uk \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@lists.codethink.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.