From: Pavel Machek <pavel@ucw.cz>
To: Sakari <sakari.ailus@iki.fi>
Cc: sre@kernel.org, pali.rohar@gmail.com,
linux-media@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] smiapp: add CCP2 support
Date: Wed, 15 Feb 2017 11:48:19 +0100 [thread overview]
Message-ID: <20170215104819.GC29330@amd> (raw)
In-Reply-To: <20170212221042.GA16975@valkosipuli.retiisi.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]
Hi!
> > > I pushed the two DT patches here:
> > >
> > > <URL:https://git.linuxtv.org/sailus/media_tree.git/commit/?h=ccp2>
> >
> > Thanks for a branch. If you could the two patches that look ok there,
> > it would mean less work for me, I could just mark those two as applied
> > here.
>
> I think a verb could be missing from the sentence. :-) I'll send a pull
> request for the entire set, containing more than just the DT changes. Feel
> free to base yours on top of this.
>
> A word of warning: I have patches to replace the V4L2 OF framework by V4L2
> fwnode. The preliminary set (which is still missing V4L2 OF removal) is
> here, I'll post a refresh soon:
>
> <URL:http://www.spinics.net/lists/linux-media/msg106160.html>
>
> Let's see what the order ends up to be in the end. If the fwnode set is
> applicable first, then I'd like to rebase the lane parsing changes on top of
> that rather than the other way around --- it's easier that way.
>
> >
> > Core changes for CSI2 support are needed.
>
> CCP2? We could get these and the smiapp and possibly also the omap3isp
> patches in first, to avoid having to manage a large patchset. What do you
> think?
Well... anything that reduces the ammount of patches I need to
maintain to keep camera working is welcome.
> > There are core changes in notifier locking, and subdev support.
> >
> > I need video-bus-switch, at least for testing.
> >
> > I need subdev support for omap3isp, so that we can attach flash and
> > focus devices.
> >
> > Finally dts support on N900 can be enabled.
>
> Yes! 8-)
>
> I don't know if any euros were saved by using that video bus switch but it
> sure has caused a lot of hassle (and perhaps some gray hair) for software
> engineers. X-)
Yes, switch is one of the problems. OTOH... Nokia did a great thing by
creating phone with reasonable design...
Pavel
--
(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 --]
next prev parent reply other threads:[~2017-02-15 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 13:11 [PATCH] smiapp: add CCP2 support Pavel Machek
2017-02-11 22:07 ` Sakari
2017-02-11 23:22 ` Pavel Machek
2017-02-12 22:10 ` Sakari
2017-02-15 10:48 ` Pavel Machek [this message]
2017-02-12 14:43 ` kbuild test robot
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=20170215104819.GC29330@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sakari.ailus@iki.fi \
--cc=sre@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