From: Rob Herring <robh@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-media@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
James Cameron <quozl@laptop.org>, Pavel Machek <pavel@ucw.cz>,
Libin Yang <lbyang@marvell.com>,
Albert Wang <twang13@marvell.com>,
jacopo mondi <jacopo@jmondi.org>,
Sakari Ailus <sakari.ailus@iki.fi>,
Lubomir Rintel <lkundrak@v3.sk>
Subject: Re: [PATCH v5 01/10] media: dt-bindings: marvell,mmp2-ccic: Add Marvell MMP2 camera
Date: Tue, 7 May 2019 12:09:32 -0500 [thread overview]
Message-ID: <20190507170932.GA6587@bogus> (raw)
In-Reply-To: <20190505140031.9636-2-lkundrak@v3.sk>
On Sun, 5 May 2019 16:00:22 +0200, Lubomir Rintel wrote:
> Add Marvell MMP2 camera host interface.
>
> Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
>
> ---
> Changes since v4:
> - s/Nust/Must/
> - Documented required endpoint properties; bus-type, hsync-active,
> vsync-active and pclk-sample.
>
> Changes since v3:
> - Dropped the video-interfaces.txt reference
> - Clarify "clocks", "clock-names" and "clock-output-names" descriptions
> - Refer to other documentation by full path
>
> Changes since v2:
> - Added #clock-cells, clock-names, port
>
> .../bindings/media/marvell,mmp2-ccic.txt | 50 +++++++++++++++++++
> 1 file changed, 50 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/marvell,mmp2-ccic.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-05-07 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 14:00 [PATCH v5 00/10] media: make Marvell camera work on DT-based OLPC XO-1.75 Lubomir Rintel
2019-05-05 14:00 ` [PATCH v5 01/10] media: dt-bindings: marvell,mmp2-ccic: Add Marvell MMP2 camera Lubomir Rintel
2019-05-07 17:09 ` Rob Herring [this message]
2019-06-14 9:50 ` Jacopo Mondi
2019-05-05 14:00 ` [PATCH v5 02/10] [media] marvell-ccic: fix DMA s/g desc number calculation Lubomir Rintel
2019-06-14 9:41 ` Jacopo Mondi
2019-06-19 8:16 ` Lubomir Rintel
2019-05-05 14:00 ` [PATCH v5 03/10] [media] marvell-ccic: don't generate EOF on parallel bus Lubomir Rintel
2019-06-14 10:01 ` Jacopo Mondi
2019-05-05 14:00 ` [PATCH v5 04/10] Revert "[media] marvell-ccic: reset ccic phy when stop streaming for stability" Lubomir Rintel
2019-05-05 14:00 ` [PATCH v5 05/10] [media] marvell-ccic: drop unused stuff Lubomir Rintel
2019-05-05 14:00 ` [PATCH v5 06/10] [media] marvell-ccic/mmp: enable clock before accessing registers Lubomir Rintel
2019-05-05 14:00 ` [PATCH v5 07/10] [media] marvell-ccic: rename the clocks Lubomir Rintel
2019-05-05 14:00 ` [PATCH v5 08/10] [media] marvell-ccic/mmp: add devicetree support Lubomir Rintel
2019-05-05 14:00 ` [PATCH v5 09/10] [media] marvell-ccic: use async notifier to get the sensor Lubomir Rintel
2019-05-05 14:00 ` [PATCH v5 10/10] [media] marvell-ccic: provide a clock for " Lubomir Rintel
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=20190507170932.GA6587@bogus \
--to=robh@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jacopo@jmondi.org \
--cc=lbyang@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=pavel@ucw.cz \
--cc=quozl@laptop.org \
--cc=sakari.ailus@iki.fi \
--cc=twang13@marvell.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).