From: jacopo mondi <jacopo@jmondi.org>
To: Simon Horman <horms@verge.net.au>
Cc: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Jacopo Mondi" <jacopo+renesas@jmondi.org>,
laurent.pinchart@ideasonboard.com, geert@glider.be,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 4/4] ARM: dts: rcar-gen2: Remove unused VIN properties
Date: Mon, 4 Jun 2018 14:57:27 +0200 [thread overview]
Message-ID: <20180604125727.GH10472@w540> (raw)
In-Reply-To: <20180604122511.cfb7cg7ojihel5mx@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]
Hi Niklas,
On Mon, Jun 04, 2018 at 02:25:15PM +0200, Simon Horman wrote:
> On Mon, Jun 04, 2018 at 01:31:54PM +0200, Niklas Söderlund wrote:
> > Hi Simon,
> >
> > On 2018-06-04 11:53:09 +0200, Simon Horman wrote:
> > > On Mon, May 21, 2018 at 07:27:43PM +0200, Jacopo Mondi wrote:
> > >
> > > > The 'bus-width' and 'pclk-sample' properties are not parsed by the VIN
> > > > driver and only confuse users. Remove them in all Gen2 SoC that use
> > > > them.
> > >
> > > I think that the rational for removing properties (or not) is their
> > > presence in the bindings as DT should describe the hardware and not the
> > > current state of the driver implementation.
> > >
> > > I see that 'bus-width' may be removed from the binding, as per discussion
> > > in a different sub-thread. I'd like that discussion to reach a conclusion
> > > before considering that part of this patch any further.
> > >
> > > And I'd appreciate Niklas's feedback on the 'pclk-sample' portion.
> >
> > My thoughts on 'pclk-sample' is the same as for 'bus-width', they
> > describe the hardware. So we either should keep or remove both. As our
> > discussion in the other thread I'm leaning towards that both should be
> > kept.
Am I wrong, or we discussed about the face there is no way to specify
the bus widht of the VIN parallel input interface?
>
> Thanks, that sounds reasonable to me.
So they should be documented if we want to keep them. Currently, they
are not.
And again, someone integrating a sensor may try to play around with those
properties, expecting them to change the interface behavior and wasting time
trying to figure out where the error is, on sensor side or VIN side, before
realizing those properties are actually ignored.
Anyway, the most important thing, if we want to keep them is to
provide a patch to document them as optional properties of the VIN
endpoint.
Thanks
j
>
> I'm marking (v4 of) this as deferred pending a conclusion to that
> conversation.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2018-06-04 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 17:27 [PATCH v2 0/4] media: rcar-vin: Brush endpoint properties Jacopo Mondi
2018-05-21 17:27 ` [PATCH v2 1/4] dt-bindings: media: rcar-vin: Describe optional ep properties Jacopo Mondi
2018-05-22 15:30 ` Niklas Söderlund
2018-05-21 17:27 ` [PATCH v2 2/4] dt-bindings: media: rcar-vin: Document data-active Jacopo Mondi
2018-05-22 15:32 ` Niklas Söderlund
2018-05-21 17:27 ` [PATCH v2 3/4] media: rcar-vin: Handle CLOCKENB pin polarity Jacopo Mondi
2018-05-22 15:36 ` Niklas Söderlund
2018-05-21 17:27 ` [PATCH v2 4/4] ARM: dts: rcar-gen2: Remove unused VIN properties Jacopo Mondi
2018-06-04 9:53 ` Simon Horman
2018-06-04 11:31 ` Niklas Söderlund
2018-06-04 12:25 ` Simon Horman
2018-06-04 12:57 ` jacopo mondi [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=20180604125727.GH10472@w540 \
--to=jacopo@jmondi.org \
--cc=geert@glider.be \
--cc=horms@verge.net.au \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
/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).