From: Pavel Machek <pavel@ucw.cz>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: pali.rohar@gmail.com, sre@kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com,
Sakari Ailus <sakari.ailus@iki.fi>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com
Subject: Nokia N900 camera support in linux-next
Date: Tue, 8 Aug 2017 13:57:52 +0200 [thread overview]
Message-ID: <20170808115752.GA19585@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 2062 bytes --]
Hi!
Most of CSI-1 / N900 camera support is there in linux-next tree:
patches marked "n" are in, unmarked patches are only in Sakari's tree.
Is there something I can do to help merging patches to linux-next? We
are quite close, and it would be nice to have camera support in v4.14...
Thanks,
Pavel
369e74605f768efa74483ab08e706347756e2092 omap3isp: Skip CSI-2 receiver initialisation in CCP2 configuratio$
8f7dc67fed42fa3d36f590fb42769bcf1513e37a omap3isp: Correctly put the last iterated endpoint fwnode always
d3e8774ca1119c264886b84d49ef28da0b459bb4 omap3isp: Always initialise isp and mutex for csiphy1
n 259c3fa06348d8142406796d0e7beb5753d07d31 omap3isp: Return -EPROBE_DEFER if the required regulators can't$
5034d8d8eceec96908c4659be58507177d0a462c omap3isp: Correctly set IO_OUT_SEL and VP_CLK_POL for CCP2 mode
bf54a7459801bde07e3c1bfc7840f30abc296f62 omap3isp: Parse CSI1 configuration from the device tree
n 07120f2667ea1c02d86dce1b3d46e28cb23e3a15 omap3isp: Ignore endpoints with invalid configuration
n 5151d5af4010a2aeeaff1fb05de4661f2fd6d982 omap3isp: add CSI1 support
n 7947670b57539df822cabaaf1d0e8a78fbcd1290 omap3isp: Explicitly set the number of CSI-2 lanes used in lane$
n 7f52779e72e4c14ffdffcf0cebdefde193457a82 omap3isp: Destroy CSI-2 phy mutexes in error and module removal
n dbd6d72970e87f39936bc036a1a9441e59177434 omap3isp: Check for valid port in endpoints
n 8a61b9bf1134d7f57e2bd65aeac0b553ecc7301e smiapp: add CCP2 support
n f71d8a1c3f33b510b379278ea171d3495ac98bb6 v4l: Add support for CSI-1 and CCP2 busses
n 1d2e2bc5f4bf78db9aa63e68dfd44823f9b62237 v4l: fwnode: Obtain data bus type from FW
n 3e4351a7e39775ef13c51950f83c51fb5d98b33c v4l: fwnode: Call CSI2 bus csi2, not csi
n 5e8535c064363713855d975f2c9777bbc739c877 dt: bindings: Add strobe property for CCP2
n 3c736565c543ec97f54f177df295ed729e80d39f dt: bindings: Explicitly specify bus type
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: Nokia N900 camera support in linux-next
Date: Tue, 8 Aug 2017 13:57:52 +0200 [thread overview]
Message-ID: <20170808115752.GA19585@amd> (raw)
Hi!
Most of CSI-1 / N900 camera support is there in linux-next tree:
patches marked "n" are in, unmarked patches are only in Sakari's tree.
Is there something I can do to help merging patches to linux-next? We
are quite close, and it would be nice to have camera support in v4.14...
Thanks,
Pavel
369e74605f768efa74483ab08e706347756e2092 omap3isp: Skip CSI-2 receiver initialisation in CCP2 configuratio$
8f7dc67fed42fa3d36f590fb42769bcf1513e37a omap3isp: Correctly put the last iterated endpoint fwnode always
d3e8774ca1119c264886b84d49ef28da0b459bb4 omap3isp: Always initialise isp and mutex for csiphy1
n 259c3fa06348d8142406796d0e7beb5753d07d31 omap3isp: Return -EPROBE_DEFER if the required regulators can't$
5034d8d8eceec96908c4659be58507177d0a462c omap3isp: Correctly set IO_OUT_SEL and VP_CLK_POL for CCP2 mode
bf54a7459801bde07e3c1bfc7840f30abc296f62 omap3isp: Parse CSI1 configuration from the device tree
n 07120f2667ea1c02d86dce1b3d46e28cb23e3a15 omap3isp: Ignore endpoints with invalid configuration
n 5151d5af4010a2aeeaff1fb05de4661f2fd6d982 omap3isp: add CSI1 support
n 7947670b57539df822cabaaf1d0e8a78fbcd1290 omap3isp: Explicitly set the number of CSI-2 lanes used in lane$
n 7f52779e72e4c14ffdffcf0cebdefde193457a82 omap3isp: Destroy CSI-2 phy mutexes in error and module removal
n dbd6d72970e87f39936bc036a1a9441e59177434 omap3isp: Check for valid port in endpoints
n 8a61b9bf1134d7f57e2bd65aeac0b553ecc7301e smiapp: add CCP2 support
n f71d8a1c3f33b510b379278ea171d3495ac98bb6 v4l: Add support for CSI-1 and CCP2 busses
n 1d2e2bc5f4bf78db9aa63e68dfd44823f9b62237 v4l: fwnode: Obtain data bus type from FW
n 3e4351a7e39775ef13c51950f83c51fb5d98b33c v4l: fwnode: Call CSI2 bus csi2, not csi
n 5e8535c064363713855d975f2c9777bbc739c877 dt: bindings: Add strobe property for CCP2
n 3c736565c543ec97f54f177df295ed729e80d39f dt: bindings: Explicitly specify bus type
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170808/a58ecdeb/attachment.sig>
next reply other threads:[~2017-08-08 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 11:57 Pavel Machek [this message]
2017-08-08 11:57 ` Nokia N900 camera support in linux-next Pavel Machek
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=20170808115752.GA19585@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=abcloriens@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@linux.intel.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.