From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
"crope@iki.fi" <crope@iki.fi>,
Chris Paterson <Chris.Paterson2@renesas.com>,
"geert+renesas@glider.be" <geert+renesas@glider.be>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v3 2/7] dt-bindings: media: Add MAX2175 binding description
Date: Tue, 11 Apr 2017 14:27:17 +0300 [thread overview]
Message-ID: <6297638.5S79beP3Jj@avalon> (raw)
In-Reply-To: <HK2PR06MB0545282102FBC0472D9831AEC3000@HK2PR06MB0545.apcprd06.prod.outlook.com>
Hi Ramesh,
On Tuesday 11 Apr 2017 09:57:45 Ramesh Shanmugasundaram wrote:
> > On Tuesday 07 Feb 2017 15:02:32 Ramesh Shanmugasundaram wrote:
> >> Add device tree binding documentation for MAX2175 Rf to bits tuner
> >> device.
> >>
> >> Signed-off-by: Ramesh Shanmugasundaram
> >> <ramesh.shanmugasundaram@bp.renesas.com> ---
> >>
> >> .../devicetree/bindings/media/i2c/max2175.txt | 61 +++++++++++++++
> >> .../devicetree/bindings/property-units.txt | 1 +
> >> 2 files changed, 62 insertions(+)
> >> create mode 100644
> >>
> >> Documentation/devicetree/bindings/media/i2c/max2175.txt
> >>
> >> diff --git a/Documentation/devicetree/bindings/media/i2c/max2175.txt
> >> b/Documentation/devicetree/bindings/media/i2c/max2175.txt new file
> >> mode 100644
> >> index 0000000..f591ab4
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/media/i2c/max2175.txt
[snip]
> >> +- maxim,am-hiz : empty property indicates AM Hi-Z filter path
> >> is
> >> + selected for AM antenna input. By default this
> >> + filter path is not used.
> >
> > Isn't this something that should be selected at runtime through a control
> > ? Or does the hardware design dictate whether the filter has to be used or
> > must not be used ?
>
> This is dictated by the h/w design and not selectable at run-time.
> I will update these changes in the next patchset.
In that case I'm fine with a property, but could we name it in such a way that
it describes the hardware instead of instructing the software on how to
configure the device ? For instance (and this is a made-up example as I don't
know exactly how this works), if the AM Hi-Z filter is required when dealing
with AM frequencies and forbidden when dealing with other frequency bands, and
*if* boards have to be designed specifically for one frequency band (AM, FM,
VHF, L, ...) without any way to accept different bands, then you could instead
use
maxim,frequency-band = "AM";
and enable the filter accordingly in the driver. This would be in my opinion a
better system hardware description.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
To: Ramesh Shanmugasundaram
<ramesh.shanmugasundaram-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
Cc: "robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"mark.rutland-5wv7dgnIgG8@public.gmane.org"
<mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"mchehab-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<mchehab-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org"
<hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>,
"sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org"
<sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"crope-X3B1VOXEql0@public.gmane.org"
<crope-X3B1VOXEql0@public.gmane.org>,
Chris Paterson
<Chris.Paterson2-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>,
"geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org"
<geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>,
"linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v3 2/7] dt-bindings: media: Add MAX2175 binding description
Date: Tue, 11 Apr 2017 14:27:17 +0300 [thread overview]
Message-ID: <6297638.5S79beP3Jj@avalon> (raw)
In-Reply-To: <HK2PR06MB0545282102FBC0472D9831AEC3000-jAC1QCBx2F1Af0bSEaWBKm0DtJ1/0DrXvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
Hi Ramesh,
On Tuesday 11 Apr 2017 09:57:45 Ramesh Shanmugasundaram wrote:
> > On Tuesday 07 Feb 2017 15:02:32 Ramesh Shanmugasundaram wrote:
> >> Add device tree binding documentation for MAX2175 Rf to bits tuner
> >> device.
> >>
> >> Signed-off-by: Ramesh Shanmugasundaram
> >> <ramesh.shanmugasundaram-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org> ---
> >>
> >> .../devicetree/bindings/media/i2c/max2175.txt | 61 +++++++++++++++
> >> .../devicetree/bindings/property-units.txt | 1 +
> >> 2 files changed, 62 insertions(+)
> >> create mode 100644
> >>
> >> Documentation/devicetree/bindings/media/i2c/max2175.txt
> >>
> >> diff --git a/Documentation/devicetree/bindings/media/i2c/max2175.txt
> >> b/Documentation/devicetree/bindings/media/i2c/max2175.txt new file
> >> mode 100644
> >> index 0000000..f591ab4
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/media/i2c/max2175.txt
[snip]
> >> +- maxim,am-hiz : empty property indicates AM Hi-Z filter path
> >> is
> >> + selected for AM antenna input. By default this
> >> + filter path is not used.
> >
> > Isn't this something that should be selected at runtime through a control
> > ? Or does the hardware design dictate whether the filter has to be used or
> > must not be used ?
>
> This is dictated by the h/w design and not selectable at run-time.
> I will update these changes in the next patchset.
In that case I'm fine with a property, but could we name it in such a way that
it describes the hardware instead of instructing the software on how to
configure the device ? For instance (and this is a made-up example as I don't
know exactly how this works), if the AM Hi-Z filter is required when dealing
with AM frequencies and forbidden when dealing with other frequency bands, and
*if* boards have to be designed specifically for one frequency band (AM, FM,
VHF, L, ...) without any way to accept different bands, then you could instead
use
maxim,frequency-band = "AM";
and enable the filter accordingly in the driver. This would be in my opinion a
better system hardware description.
--
Regards,
Laurent Pinchart
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-04-11 11:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 15:02 [PATCH v3 0/7] Add V4L2 SDR (DRIF & MAX2175) driver Ramesh Shanmugasundaram
2017-02-07 15:02 ` [PATCH v3 1/7] media: v4l2-ctrls: Reserve controls for MAX217X Ramesh Shanmugasundaram
2017-02-07 15:02 ` Ramesh Shanmugasundaram
2017-04-11 8:28 ` Laurent Pinchart
2017-02-07 15:02 ` [PATCH v3 2/7] dt-bindings: media: Add MAX2175 binding description Ramesh Shanmugasundaram
2017-02-15 16:59 ` Rob Herring
2017-04-11 9:42 ` Laurent Pinchart
2017-04-11 9:57 ` Ramesh Shanmugasundaram
2017-04-11 11:27 ` Laurent Pinchart [this message]
2017-04-11 11:27 ` Laurent Pinchart
2017-04-11 12:19 ` Ramesh Shanmugasundaram
2017-04-11 12:58 ` Laurent Pinchart
2017-04-11 12:58 ` Laurent Pinchart
2017-02-07 15:02 ` [PATCH v3 3/7] media: i2c: max2175: Add MAX2175 support Ramesh Shanmugasundaram
2017-02-13 12:40 ` Hans Verkuil
2017-02-07 15:02 ` [PATCH v3 4/7] media: Add new SDR formats PC16, PC18 & PC20 Ramesh Shanmugasundaram
2017-02-07 15:02 ` [PATCH v3 5/7] doc_rst: media: New " Ramesh Shanmugasundaram
2017-04-11 12:39 ` Laurent Pinchart
2017-04-18 17:13 ` Ramesh Shanmugasundaram
2017-02-07 15:02 ` [PATCH v3 6/7] dt-bindings: media: Add Renesas R-Car DRIF binding Ramesh Shanmugasundaram
2017-02-15 17:09 ` Rob Herring
2017-02-15 17:09 ` Rob Herring
2017-02-16 11:02 ` Ramesh Shanmugasundaram
2017-04-11 22:41 ` Laurent Pinchart
2017-04-11 22:35 ` Laurent Pinchart
2017-02-07 15:02 ` [PATCH v3 7/7] media: platform: rcar_drif: Add DRIF support Ramesh Shanmugasundaram
2017-04-11 22:24 ` Laurent Pinchart
2017-04-11 22:24 ` Laurent Pinchart
2017-04-18 17:12 ` Ramesh Shanmugasundaram
2017-02-13 12:46 ` [PATCH v3 0/7] Add V4L2 SDR (DRIF & MAX2175) driver Hans Verkuil
2017-02-14 13:42 ` Laurent Pinchart
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=6297638.5S79beP3Jj@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Chris.Paterson2@renesas.com \
--cc=crope@iki.fi \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=ramesh.shanmugasundaram@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.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 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.