From: Marco Felsch <m.felsch@pengutronix.de>
To: robh+dt@kernel.org, mchehab@kernel.org, hans.verkuil@cisco.com,
sakari.ailus@linux.intel.com
Cc: devicetree@vger.kernel.org, airlied@linux.ie,
dri-devel@lists.freedesktop.org, kernel@pengutronix.de,
linux-media@vger.kernel.org
Subject: [PATCH 0/5] TV norms limit and TVP5150 implementation
Date: Sat, 2 Feb 2019 13:09:59 +0100 [thread overview]
Message-ID: <20190202121004.9014-1-m.felsch@pengutronix.de> (raw)
Hi,
in short this series adds the support to limit the tv norms on an
analog-connector.
I recognized that all drivers dealing with connectors implemented
their own parsing routine due to the lack of a generic one. A generic
parsing routine needs a connector container which contain common
data and connector specific data. This series implements the connector
container struct and the generic parsing routine. At the moment only
analog-connectors are fully supported but adding the others should
be simple.
Finally the TVP5150 driver is converted to the generic connector and
make use of the new 'tv norms limiting' feature.
I'm not sure if the series applies cleanly without [1].
Regards,
Marco
[1] https://www.mail-archive.com/linux-media@vger.kernel.org/msg143925.html
Marco Felsch (5):
dt-bindings: connector: analog: add tv norms property
media: v4l2-fwnode: add v4l2_fwnode_connector
media: v4l2-fwnode: add initial connector parsing support
media: tvp5150: make use of generic connector parsing
media: tvp5150: add support to limit tv norms on connector
.../display/connector/analog-tv-connector.txt | 4 +
drivers/media/i2c/tvp5150.c | 116 +++++++++---------
drivers/media/v4l2-core/v4l2-fwnode.c | 113 +++++++++++++++++
include/dt-bindings/media/tvnorms.h | 42 +++++++
include/media/v4l2-connector.h | 34 +++++
include/media/v4l2-fwnode.h | 49 ++++++++
6 files changed, 302 insertions(+), 56 deletions(-)
create mode 100644 include/dt-bindings/media/tvnorms.h
create mode 100644 include/media/v4l2-connector.h
--
2.20.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-02-02 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 12:09 Marco Felsch [this message]
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
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=20190202121004.9014-1-m.felsch@pengutronix.de \
--to=m.felsch@pengutronix.de \
--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=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).