From: Stefan Riedmueller <s.riedmueller@phytec.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Stefan Riedmueller <s.riedmueller@phytec.de>
Subject: [PATCH v4 0/6] media: mt9p031: Read back the real clock rate
Date: Thu, 8 Jul 2021 11:19:16 +0200 [thread overview]
Message-ID: <20210708091922.5508-1-s.riedmueller@phytec.de> (raw)
Hi,
Changes in v4:
- Add two missing BIT macro conversions
- Switch to dt-bindings yaml schema before applying changes
- Drop explicit pclk-sample property documentation patch since it is
documented in the referenced video-interface schema now. (I hope that
is correct)
Changes in v3:
- Dropped 1/5 media: mt9p031: Add support for 8 bit and 10 bit formats
- Dropped 3/5 media: mt9p031: Implement [gs]_register debug calls
- Added reviewed-by from Laurent Pinchart to
media: mt9p031: Read back the real clock rate
- Dropped unnecessary register reads in
media: mt9p031: Fix corrupted frame after restarting
- Changed sorting of register bits from MSB to LSB
- Added patch to switch to BIT macro
- Added two additional dt-bindings patches to add missing properties
documentation
Christian Hemp (1):
media: mt9p031: Make pixel clock polarity configurable by DT
Dirk Bender (1):
media: mt9p031: Fix corrupted frame after restarting stream
Enrico Scholz (1):
media: mt9p031: Read back the real clock rate
Stefan Riedmueller (3):
media: mt9p031: Use BIT macro
media: dt-bindings: mt9p031: Convert bindings to yaml
media: dt-bindings: mt9p031: Add missing required properties
.../bindings/media/i2c/aptina,mt9p031.yaml | 97 +++++++++++++++++++
.../devicetree/bindings/media/i2c/mt9p031.txt | 40 --------
MAINTAINERS | 1 +
drivers/media/i2c/Kconfig | 1 +
drivers/media/i2c/mt9p031.c | 80 +++++++++++----
include/media/i2c/mt9p031.h | 1 +
6 files changed, 162 insertions(+), 58 deletions(-)
create mode 100644 Documentation/devicetree/bindings/media/i2c/aptina,mt9p031.yaml
delete mode 100644 Documentation/devicetree/bindings/media/i2c/mt9p031.txt
--
2.25.1
next reply other threads:[~2021-07-08 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 9:19 Stefan Riedmueller [this message]
2021-07-08 9:19 ` [PATCH v4 1/6] media: mt9p031: Read back the real clock rate Stefan Riedmueller
2021-07-08 9:19 ` [PATCH v4 2/6] media: mt9p031: Make pixel clock polarity configurable by DT Stefan Riedmueller
2021-07-08 9:19 ` [PATCH v4 3/6] media: mt9p031: Fix corrupted frame after restarting stream Stefan Riedmueller
2021-07-08 9:19 ` [PATCH v4 4/6] media: mt9p031: Use BIT macro Stefan Riedmueller
2021-07-08 9:19 ` [PATCH v4 5/6] media: dt-bindings: mt9p031: Convert bindings to yaml Stefan Riedmueller
2021-07-08 11:23 ` Sakari Ailus
2021-07-08 13:34 ` Stefan Riedmüller
2021-07-08 14:02 ` sakari.ailus
2021-07-12 8:28 ` Stefan Riedmüller
2021-07-08 9:19 ` [PATCH v4 6/6] media: dt-bindings: mt9p031: Add missing required properties Stefan Riedmueller
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=20210708091922.5508-1-s.riedmueller@phytec.de \
--to=s.riedmueller@phytec.de \
--cc=devicetree@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--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).