From: Jan Kotas <jank@cadence.com>
To: Maxime Ripard <maxime.ripard@bootlin.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Rafal Ciepiela <rafalc@cadence.com>,
linux-media <linux-media@vger.kernel.org>,
linux-devicetree <devicetree@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jan Kotas <jank@cadence.com>
Subject: Re: [PATCH 0/3] media: Add support for Cadence CSI2RX version 2.1
Date: Thu, 1 Aug 2019 07:36:59 +0000 [thread overview]
Message-ID: <A00C1136-41F2-4EB9-8694-E33608EF82E9@global.cadence.com> (raw)
In-Reply-To: <20190725102648.13445-1-jank@cadence.com>
> On 25 Jul 2019, at 12:26, Jan Kotas <jank@cadence.com> wrote:
>
> This patchset adds support for Cadence CSI2RX controller version 2.1.
> It currently limits maximum amount of data lanes to 4.
> Existing compatibility with v1.3 is maintained.
>
> Jan Kotas (3):
> media: dt-bindings: Update bindings for Cadence CSI2RX version 2.1
> media: Add lane checks for Cadence CSI2RX
> media: Add support for Cadence CSI2RX 2.1
>
> .../devicetree/bindings/media/cdns,csi2rx.txt | 4 +-
> drivers/media/platform/cadence/cdns-csi2rx.c | 150 +++++++++++++++++----
> 2 files changed, 129 insertions(+), 25 deletions(-)
>
> --
> 2.15.0
>
Gentle ping.
Regards,
Jan
prev parent reply other threads:[~2019-08-01 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 10:26 [PATCH 0/3] media: Add support for Cadence CSI2RX version 2.1 Jan Kotas
2019-07-25 10:26 ` [PATCH 1/3] media: dt-bindings: Update bindings " Jan Kotas
2019-08-16 21:18 ` Rob Herring
2019-08-19 7:16 ` Jan Kotas
2019-07-25 10:26 ` [PATCH 2/3] media: Add lane checks for Cadence CSI2RX Jan Kotas
2019-07-25 10:26 ` [PATCH 3/3] media: Add support for Cadence CSI2RX 2.1 Jan Kotas
2019-08-01 7:36 ` Jan Kotas [this message]
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=A00C1136-41F2-4EB9-8694-E33608EF82E9@global.cadence.com \
--to=jank@cadence.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mchehab@kernel.org \
--cc=rafalc@cadence.com \
--cc=robh+dt@kernel.org \
/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).