From: Shawn Guo <shawnguo@kernel.org>
To: Martin Kepplinger <martin.kepplinger@puri.sm>
Cc: laurent.pinchart@ideasonboard.com, devicetree@vger.kernel.org,
festevam@gmail.com, kernel@pengutronix.de, kernel@puri.sm,
krzk@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-imx@nxp.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
m.felsch@pengutronix.de, mchehab@kernel.org,
phone-devel@vger.kernel.org, robh@kernel.org,
slongerbeam@gmail.com
Subject: Re: [PATCH v9 3/3] arm64: dts: imx8mq: add mipi csi phy and csi bridge descriptions
Date: Wed, 4 Aug 2021 17:08:24 +0800 [thread overview]
Message-ID: <20210804090823.GB30984@dragon> (raw)
In-Reply-To: <20210726082117.2423597-4-martin.kepplinger@puri.sm>
On Mon, Jul 26, 2021 at 10:21:17AM +0200, Martin Kepplinger wrote:
> Describe the 2 available CSI interfaces on the i.MX8MQ with the MIPI-CSI2
> receiver (new driver) and the CSI Bridge that provides the user buffers
> (existing driver).
>
> An image sensor is to be connected to the MIPIs' second port, to be described
> in board files.
>
> Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
Applied, thanks!
next prev parent reply other threads:[~2021-08-04 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 8:21 [PATCH v9 0/3] media: imx: add support for imx8mq MIPI RX Martin Kepplinger
2021-07-26 8:21 ` [PATCH v9 1/3] dt-bindings: media: document the nxp,imx8mq-mipi-csi2 receiver phy and controller Martin Kepplinger
2021-07-26 8:21 ` [PATCH v9 2/3] media: imx: add a driver for i.MX8MQ mipi csi rx " Martin Kepplinger
2021-07-28 5:02 ` Dafna Hirschfeld
2021-07-28 5:51 ` Laurent Pinchart
2021-07-26 8:21 ` [PATCH v9 3/3] arm64: dts: imx8mq: add mipi csi phy and csi bridge descriptions Martin Kepplinger
2021-08-04 9:08 ` Shawn Guo [this message]
2021-07-27 1:00 ` [PATCH v9 0/3] media: imx: add support for imx8mq MIPI RX Laurent Pinchart
2021-08-04 9:09 ` Shawn Guo
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=20210804090823.GB30984@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=krzk@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=m.felsch@pengutronix.de \
--cc=martin.kepplinger@puri.sm \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=slongerbeam@gmail.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).