From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-media@vger.kernel.org, a.hajda@samsung.com,
hj210.choi@samsung.com, sw0312.kim@samsung.com,
devicetree-discuss@lists.ozlabs.org,
Andrzej Pietrasiewicz <andrzej.p@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
George Joseph <george.jp@samsung.com>,
"aditya.ps" <aditya.ps@samsung.com>,
sunil joshi <joshi@samsung.com>
Subject: Re: [PATCH] s5p-jpeg: Enable instantiation from device tree
Date: Thu, 09 May 2013 17:51:58 +0200 [thread overview]
Message-ID: <518BC61E.3040202@samsung.com> (raw)
In-Reply-To: <CAK9yfHx-o-3oYj8hMKzQK7N3CD7=tUwbxcHG-9gA25yfRjky2Q@mail.gmail.com>
Hi Sachin,
On 05/09/2013 04:50 PM, Sachin Kamat wrote:
> George from my team is working on adding JPEG IP support for 4412 and
> 5250 SoCs which is quite different from 4210.
> In this regard he has refactored the driver to accomodate the changes
> required for the new IP and also added DT support.
> The patches are almost ready and would be submitted in the next couple
> of days. This is FYI :)
That's greats news, since on our side currently nobody has been working
on the Exynos4x12+ JPEG codec support. I just prepared a patch adding
DT matching table and checked the driver gets initialized on Exynos4x12.
So it is at least usable on Exynos4210 in 3.11. I should not have listed
"samsung,exynos4212-jpeg" in the driver, since it is missing adaptations
for Exynos4x12 SoCs.
We have plenty time to add proper support for the JPEG IP in 3.11. I'm
looking forward to review and test your patches. Can you use the $subject
patch as a base of your work ? ;-) Or is it rather useless ?
FYI, I will be mostly offline for next 2 weeks.
Thanks,
Sylwester
next prev parent reply other threads:[~2013-05-09 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 12:39 [PATCH] s5p-jpeg: Enable instantiation from device tree Sylwester Nawrocki
2013-05-09 14:50 ` Sachin Kamat
2013-05-09 15:51 ` Sylwester Nawrocki [this message]
2013-05-10 3:43 ` Sachin Kamat
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=518BC61E.3040202@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=a.hajda@samsung.com \
--cc=aditya.ps@samsung.com \
--cc=andrzej.p@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=george.jp@samsung.com \
--cc=hj210.choi@samsung.com \
--cc=joshi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=sw0312.kim@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;
as well as URLs for NNTP newsgroup(s).