From: Sylwester Nawrocki <snjw23@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
kyungmin.park@samsung.com, m.szyprowski@samsung.com,
riverful.kim@samsung.com, kgene.kim@samsung.com,
sungchun.kang@samsung.com, jonghun.han@samsung.com,
stern@rowland.harvard.edu, rjw@sisk.pl
Subject: Re: [PATCH 3/3 v5] v4l: Add v4l2 subdev driver for S5P/EXYNOS4 MIPI-CSI receivers
Date: Tue, 17 May 2011 22:06:23 +0200 [thread overview]
Message-ID: <4DD2D53F.8020403@gmail.com> (raw)
In-Reply-To: <201105152310.07178.laurent.pinchart@ideasonboard.com>
Hi Laurent,
On 05/15/2011 11:10 PM, Laurent Pinchart wrote:
> On Sunday 15 May 2011 11:33:14 Sylwester Nawrocki wrote:
>> On 05/14/2011 05:29 PM, Laurent Pinchart wrote:
>>> On Wednesday 11 May 2011 17:17:10 Sylwester Nawrocki wrote:
<snip>
>>
>> I perhaps need to isolate functions out from of s5pcsis_resume/suspend and
>> then call that in s_power op and s5pcsis_resume/suspend. Don't really like
>> this idea though... It would virtually render pm_runtime_* calls unusable
>> in this sub-device driver, those would make sense only in the host driver..
>
> I think using the pm_runtime_* calls make sense, they could replace the subdev
> s_power operation in the long term. We'll need to evaluate that (I'm not sure
> if runtime PM is available on all platforms targeted by V4L2 for instance).
That sounds like a really good direction. It would let us have clear standardized
rules for power handling in V4L2. And with new chips of more complicated
topologies the power handling details could be taken care of by the Runtime PM
subsystem. As the runtime PM becomes more granular it appears a good alternative
for simple subdev s_power call.
Unfortunately still only a few architectures support runtime PM at device bus level
in the mainline. What I identified is:
arm/mach-exynos4
arm/mach-omap1
arm/mach-omap2
arm/mach-shmobile
So very few, no x86 here.
As we have I2C, SPI and platform device v4l subdevs ideally those buses should
support Runtime PM.
>> I just wanted to put all what is needed to control device's power in the PM
>> helpers and then use pm_runtime_* calls where required.
--
Regards,
Sylwester Nawrocki
next prev parent reply other threads:[~2011-05-17 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 15:17 [PATCH v5] Add v4l2 subdev driver for Samsung S5P MIPI-CSI receivers Sylwester Nawrocki
2011-05-11 15:17 ` [PATCH 1/3 v5] v4l: Add V4L2_MBUS_FMT_JPEG_1X8 media bus format Sylwester Nawrocki
2011-05-11 15:17 ` [PATCH 2/3 v5] v4l: Move s5p-fimc driver into Video capture devices Sylwester Nawrocki
2011-05-11 15:17 ` [PATCH 3/3 v5] v4l: Add v4l2 subdev driver for S5P/EXYNOS4 MIPI-CSI receivers Sylwester Nawrocki
2011-05-14 15:29 ` Laurent Pinchart
2011-05-15 9:33 ` Sylwester Nawrocki
2011-05-15 21:10 ` Laurent Pinchart
2011-05-17 20:06 ` Sylwester Nawrocki [this message]
2011-05-17 22:46 ` Mark Brown
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=4DD2D53F.8020403@gmail.com \
--to=snjw23@gmail.com \
--cc=jonghun.han@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=riverful.kim@samsung.com \
--cc=rjw@sisk.pl \
--cc=s.nawrocki@samsung.com \
--cc=stern@rowland.harvard.edu \
--cc=sungchun.kang@samsung.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