From: Rob Herring <robh@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: devicetree@vger.kernel.org, sakari.ailus@linux.intel.com,
airlied@linux.ie, dri-devel@lists.freedesktop.org,
robh+dt@kernel.org, hans.verkuil@cisco.com, mchehab@kernel.org,
kernel@pengutronix.de, linux-media@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: connector: analog: add tv norms property
Date: Mon, 25 Feb 2019 14:11:59 -0600 [thread overview]
Message-ID: <20190225201159.GA9207@bogus> (raw)
In-Reply-To: <20190202121004.9014-2-m.felsch@pengutronix.de>
On Sat, 2 Feb 2019 13:10:00 +0100, Marco Felsch wrote:
> Some connectors no matter if in- or output supports only a limited
> range of tv norms. It doesn't matter if the hardware behind that
> connector supports more than the listed formats since the users are
> restriced by a label e.g. to plug only a camera into this connector
> which uses the PAL format.
>
> This patch adds the capability to describe such limitation within the
> firmware. There are no format restrictions if the property isn't
> present, so it's completely backward compatible.
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
> .../display/connector/analog-tv-connector.txt | 4 ++
> include/dt-bindings/media/tvnorms.h | 42 +++++++++++++++++++
> 2 files changed, 46 insertions(+)
> create mode 100644 include/dt-bindings/media/tvnorms.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-02-25 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 12:09 [PATCH 0/5] TV norms limit and TVP5150 implementation Marco Felsch
2019-02-02 12:10 ` [PATCH 1/5] dt-bindings: connector: analog: add tv norms property Marco Felsch
2019-02-25 20:11 ` Rob Herring [this message]
2019-02-02 12:10 ` [PATCH 2/5] media: v4l2-fwnode: add v4l2_fwnode_connector Marco Felsch
2019-02-02 12:10 ` [PATCH 3/5] media: v4l2-fwnode: add initial connector parsing support Marco Felsch
2019-02-02 12:10 ` [PATCH 4/5] media: tvp5150: make use of generic connector parsing Marco Felsch
2019-02-02 12:10 ` [PATCH 5/5] media: tvp5150: add support to limit tv norms on connector Marco Felsch
2019-03-20 14:18 ` Mauro Carvalho Chehab
2019-03-20 16:36 ` Marco Felsch
2019-03-20 17:29 ` Mauro Carvalho Chehab
2019-03-21 9:53 ` Marco Felsch
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=20190225201159.GA9207@bogus \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hans.verkuil@cisco.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=mchehab@kernel.org \
--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 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).