From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: sungchun.kang@samsung.com
Cc: 'Shaik Ameer Basha' <shaik.ameer@samsung.com>,
linux-media@vger.kernel.org, khw0178.kim@samsung.com,
mchehab@infradead.org, laurent.pinchart@ideasonboard.com,
sy0816.kang@samsung.com, posciak@google.com, hverkuil@xs4all.nl,
alim.akhtar@gmail.com, prashanth.g@samsung.com,
joshi@samsung.com, shaik.samsung@gmail.com
Subject: Re: [PATCH v5 0/5] Add new driver for generic scaler
Date: Wed, 01 Aug 2012 10:28:37 +0200 [thread overview]
Message-ID: <5018E8B5.4050708@samsung.com> (raw)
In-Reply-To: <008301cd6fb8$38f1f8e0$aad5eaa0$%kang@samsung.com>
On 08/01/2012 09:35 AM, Sungchun Kang wrote:
> I'm sorry to be so late.
> Basically, I wonder important one thing.
> What would you implement a device driver connected with gscaler.
> For example, fimc-lite, mipi-csis.
> As you know Exynos5 has local-path with gscaler
> MIPI-CSIS => Fimc-lite => Gscaler
> And, you should use media control framework.
> So, We made exynos folder, and implement drivers with mc.
> We use mdev that is virtual device driver for connecting gscaler, fimc-lite, mipi-csis with MC.
> This is camera path.
> There are not only camera path but also rendering path.
> Gscaler => FIMD or TV
> Rendering path use mdev-0,
> Camera path use mdev-1.
> In conclusion, because we use to connect each other devices with MC, we made exynos folder.
>
> And how you make to implement devices with MC?
As you may know, these patches only add mem-to-mem functionality,
which can be used together with the Exynos multi-format video codec.
Remaining features, as you listed, are planned to be added later,
in subsequent steps, after discussing it here on the mailing list.
I think it's much better approach, than coming up with a complete huge
driver with many API compliance issues. Especially that some drivers,
like MIPI-CSIS or FIMC-LITE are already in the mainline kernel.
As for the driver directory name, IMHO drivers/media/exynos is too
generic, s5p-fimc, s5p-jpeg, s5p-tv also cover some Exynos SoCs.
I don't think having drivers/media/exynos directory would be helpful
in anything.
Regards,
Sylwester
prev parent reply other threads:[~2012-08-01 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 13:44 [PATCH v5 0/5] Add new driver for generic scaler Shaik Ameer Basha
2012-07-31 13:44 ` [PATCH v5 1/5] v4l: Add new YVU420 multi planar fourcc definition Shaik Ameer Basha
2012-07-31 13:44 ` [PATCH v5 2/5] media: gscaler: Add new driver for generic scaler Shaik Ameer Basha
2012-07-31 13:44 ` [PATCH v5 3/5] media: gscaler: Add core functionality for the G-Scaler driver Shaik Ameer Basha
2012-07-31 13:44 ` [PATCH v5 4/5] media: gscaler: Add m2m " Shaik Ameer Basha
2012-07-31 13:44 ` [PATCH v5 5/5] media: gscaler: Add Makefile for G-Scaler Driver Shaik Ameer Basha
2012-07-31 13:55 ` [PATCH v5 0/5] Add new driver for generic scaler Sylwester Nawrocki
2012-08-01 7:35 ` Sungchun Kang
2012-08-01 8:28 ` Sylwester Nawrocki [this message]
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=5018E8B5.4050708@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=alim.akhtar@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=joshi@samsung.com \
--cc=khw0178.kim@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=posciak@google.com \
--cc=prashanth.g@samsung.com \
--cc=shaik.ameer@samsung.com \
--cc=shaik.samsung@gmail.com \
--cc=sungchun.kang@samsung.com \
--cc=sy0816.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 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.