From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Arun Kumar K <arunkk.samsung@gmail.com>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
LMML <linux-media@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
devicetree@vger.kernel.org,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Stephen Warren <swarren@wwwdotorg.org>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <Pawel.Moll@arm.com>,
Kumar Gala <galak@codeaurora.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Sachin Kamat <sachin.kamat@linaro.org>,
Shaik Ameer Basha <shaik.ameer@samsung.com>,
kilyeon.im@samsung.com
Subject: Re: [PATCH v7 01/13] [media] exynos5-is: Adding media device driver for exynos5
Date: Tue, 17 Sep 2013 22:50:24 +0200 [thread overview]
Message-ID: <5238C090.6090201@gmail.com> (raw)
In-Reply-To: <CALt3h79YMgdkju17SF8M3NKLkJ+6Gjzy2vwXDYTXc8B-GaecyQ@mail.gmail.com>
Hi Arun,
On 09/17/2013 01:29 PM, Arun Kumar K wrote:
> Wont this make fimc-is to be enabled to use fimc-lite?
Hmm, it would be runtime PM active, yes. But it doesn't mean the
Cortex-A5's firmware would need to be running.
> As such there is no dependency like that in hardware and we can
> use fimc-lite alone in DMA out mode without fimc-is.
If you are sure about it, then fimc-lite nodes could stay at root level.
Still, it would be more appropriate IMO to have the FIMC-IS sub-/peripheral
devices, like I2C or SPI bus controllers, instantiated by the FIMC-IS
driver.
And what about "glue logic" linking FIMC-LITEs with the rest of the
imaging subsystem ? Are you sure the is no some weird inter-dependencies ?
Note that there is no board files any more, where we could hack some
details.
> If its modified as per your suggestion, how will the scenario of
> sensor -> mipi-csis -> fimc-lite -> memory look like without fimc-is?
The exynos5-fimc-is module would need to be loaded for that. If you're
sure the hardware can work independently, we could leave out the fimc-lite
nodes at root level.
Regards,
Sylwester
next prev parent reply other threads:[~2013-09-17 20:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 6:34 [PATCH v7 00/13] Exynos5 IS driver Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 01/13] [media] exynos5-is: Adding media device driver for exynos5 Arun Kumar K
2013-09-05 19:44 ` Sylwester Nawrocki
2013-09-16 21:53 ` Sylwester Nawrocki
2013-09-17 11:29 ` Arun Kumar K
2013-09-17 20:50 ` Sylwester Nawrocki [this message]
2013-09-18 11:48 ` Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 02/13] [media] exynos5-fimc-is: Add Exynos5 FIMC-IS device tree bindings documentation Arun Kumar K
2013-09-05 19:40 ` Sylwester Nawrocki
2013-08-21 6:34 ` [PATCH v7 03/13] [media] exynos5-fimc-is: Add driver core files Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 04/13] [media] exynos5-fimc-is: Add common driver header files Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 05/13] [media] exynos5-fimc-is: Add register definition and context header Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 06/13] [media] exynos5-fimc-is: Add isp subdev Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 07/13] [media] exynos5-fimc-is: Add scaler subdev Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 08/13] [media] exynos5-fimc-is: Add sensor interface Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 09/13] [media] exynos5-fimc-is: Add the hardware pipeline control Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 10/13] [media] exynos5-fimc-is: Add the hardware interface module Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 11/13] [media] exynos5-is: Add Kconfig and Makefile Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 12/13] V4L: s5k6a3: Change sensor min/max resolutions Arun Kumar K
2013-08-21 6:34 ` [PATCH v7 13/13] V4L: Add driver for s5k4e5 image sensor Arun Kumar K
2013-08-21 6:53 ` Hans Verkuil
2013-08-21 7:58 ` Tomasz Figa
2013-08-21 8:24 ` Hans Verkuil
2013-08-21 9:04 ` Arun Kumar K
2013-08-21 9:13 ` Sylwester Nawrocki
2013-08-21 9:28 ` Sylwester Nawrocki
2013-09-05 20:02 ` Sylwester Nawrocki
2013-09-06 4:33 ` Arun Kumar K
2013-09-11 5:10 ` Arun Kumar K
2013-09-11 10:16 ` Sylwester Nawrocki
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=5238C090.6090201@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=Pawel.Moll@arm.com \
--cc=a.hajda@samsung.com \
--cc=arunkk.samsung@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hverkuil@xs4all.nl \
--cc=kilyeon.im@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=s.nawrocki@samsung.com \
--cc=sachin.kamat@linaro.org \
--cc=shaik.ameer@samsung.com \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).