From: Martin Kepplinger <martin.kepplinger@puri.sm>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: mchehab@kernel.org, shawnguo@kernel.org, festevam@gmail.com,
slongerbeam@gmail.com, gregkh@linuxfoundation.org,
hverkuil-cisco@xs4all.nl, rmfrfs@gmail.com,
kernel@pengutronix.de, linux-imx@nxp.com, kernel@puri.sm,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: imx: Unstage the imx8mq-mipi-csi2 driver
Date: Tue, 16 May 2023 09:42:18 +0200 [thread overview]
Message-ID: <a4b3cf3be9f105adcbcad688f8745556eec4d9df.camel@puri.sm> (raw)
In-Reply-To: <20230425094346.GA17841@pendragon.ideasonboard.com>
Am Dienstag, dem 25.04.2023 um 12:43 +0300 schrieb Laurent Pinchart:
> Hi Martin,
>
> Thank you for the patch.
>
> On Tue, Apr 25, 2023 at 11:08:04AM +0200, Martin Kepplinger wrote:
> > The imx8mq-mipi-csi2 MIPI CSI-2 receiver driver is used and
> > maintained.
> > There is no reason to keep it in staging. The accompanying CSI
> > bridge
> > driver that uses it is in drivers/media/platform/nxp as well.
> >
> > One TODO is to get rid of csi_state's "state" and "lock" variables.
> > Especially make sure suspend/resume is working without them. That
> > can
> > very well be worked on from the new location.
> >
> > Also add a MAINTAINERS section for the imx8mq-mipi-csi2 mipi
> > receiver
> > driver.
> >
> > Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Thanks for reviewing Laurent,
Are there any second thoughts to this? If not: It still applies to
todays' next kernel. Who would be able to queue this up?
(This enables Debian and other distributions to use cameras on imx8mq.)
thanks,
martin
next prev parent reply other threads:[~2023-05-16 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 9:08 Martin Kepplinger
2023-04-25 9:43 ` Laurent Pinchart
2023-05-16 7:42 ` Martin Kepplinger [this message]
2023-07-17 11:00 ` Martin Kepplinger
2023-07-18 10:33 ` Hans Verkuil
2023-07-21 8:49 ` Martin Kepplinger
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=a4b3cf3be9f105adcbcad688f8745556eec4d9df.camel@puri.sm \
--to=martin.kepplinger@puri.sm \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--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=mchehab@kernel.org \
--cc=rmfrfs@gmail.com \
--cc=shawnguo@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
all inboxes | Powered by JetHome®