Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1565409
| From | Steve Longerbeam <steve_longerbeam@mentor.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v3 16/24] media: Add i.MX media core driver |
| Date | 2017-01-24 02:50 +0100 |
| Message-ID | <t2Ypb-63R-9@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <sZFj3-3c7-1@gated-at.bofh.it> <t0fPA-14g-11@gated-at.bofh.it> <t2CI2-wb-3@gated-at.bofh.it> <t2KPf-5Ks-13@gated-at.bofh.it> <t2Yfv-5Zm-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 01/23/2017 05:38 PM, Steve Longerbeam wrote: > >> >>> Second, ignoring the above locking issue for a moment, >>> v4l2_pipeline_pm_use() >>> will call s_power on the sensor _first_, then the mipi csi-2 s_power, >>> when executing >>> media-ctl -l '"ov5640 1-003c":0 -> "imx6-mipi-csi2":0[1]'. Which is the >>> wrong order. >>> In my version which enforces the correct power on order, the mipi csi-2 >>> s_power >>> is called first in that link setup, followed by the sensor. >> I don't understand why you want to power up subdevs as soon as the links >> are established. > > Because that is the precedence, all other media drivers do pipeline > power on/off at link_notify. And v4l2_pipeline_link_notify() was written > as a link_notify method. > >> Shouldn't that rather be done for all subdevices in the >> pipeline when the corresponding capture device is opened? > > that won't work. There's no guarantee the links will be established > at capture device open time. ugh, maybe v4l2_pipeline_pm_use() would work at open/release. If there are no links yet, it would basically be a no-op. And stream on requires opening the device, and the pipeline links should be established by then, so this might be fine, looking into this too. Steve > >> It seems to me that powering up the pipeline should be the last step >> before userspace actually starts the capture. > > Well, I'm ok with moving pipeline power on/off to start/stop streaming. > I would actually prefer to do it then, I only chose at link_notify > because > of precedence. I'll look into it.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v3 16/24] media: Add i.MX media core driver Steve Longerbeam <slongerbeam@gmail.com> - 2017-01-23 03:40 +0100
Re: [PATCH v3 16/24] media: Add i.MX media core driver Philipp Zabel <p.zabel@pengutronix.de> - 2017-01-23 12:20 +0100
Re: [PATCH v3 16/24] media: Add i.MX media core driver Steve Longerbeam <slongerbeam@gmail.com> - 2017-01-24 02:40 +0100
Re: [PATCH v3 16/24] media: Add i.MX media core driver Steve Longerbeam <steve_longerbeam@mentor.com> - 2017-01-24 02:50 +0100
Re: [PATCH v3 16/24] media: Add i.MX media core driver Philipp Zabel <p.zabel@pengutronix.de> - 2017-01-24 12:40 +0100
Re: [PATCH v3 16/24] media: Add i.MX media core driver Russell King - ARM Linux <linux@armlinux.org.uk> - 2017-01-30 16:40 +0100
csiph-web