From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Shaik Ameer Basha <shaik.ameer@samsung.com>
Cc: linux-media@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-samsung-soc@vger.kernel.org, s.nawrocki@samsung.com,
shaik.samsung@gmail.com
Subject: Re: [RFC 02/12] fimc-lite: Adding Exynos5 compatibility to fimc-lite driver
Date: Sun, 10 Mar 2013 21:36:47 +0100 [thread overview]
Message-ID: <513CEEDF.4010304@gmail.com> (raw)
In-Reply-To: <1362570838-4737-3-git-send-email-shaik.ameer@samsung.com>
On 03/06/2013 12:53 PM, Shaik Ameer Basha wrote:
> This patch adds the Exynos5 soc compatibility to the fimc-lite driver.
> It also adds a version checking to deal with the changes between
> different fimc-lite hardware versions.
Is there really anything different between the Exynos4 and Exynos5
FIMC-LITE IPs except the maximum number of buffer descriptors in
the output DMA queue ?
> Signed-off-by: Shaik Ameer Basha<shaik.ameer@samsung.com>
> ---
> drivers/media/platform/s5p-fimc/fimc-lite.c | 23 +++++++++++++++++++++++
> drivers/media/platform/s5p-fimc/fimc-lite.h | 7 ++++++-
> 2 files changed, 29 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/s5p-fimc/fimc-lite.c b/drivers/media/platform/s5p-fimc/fimc-lite.c
> index 122cf95..eb64f87 100644
> --- a/drivers/media/platform/s5p-fimc/fimc-lite.c
> +++ b/drivers/media/platform/s5p-fimc/fimc-lite.c
> @@ -1653,6 +1653,16 @@ static struct flite_variant fimc_lite0_variant_exynos4 = {
> .out_width_align = 8,
> .win_hor_offs_align = 2,
> .out_hor_offs_align = 8,
> + .version = FLITE_VER_EXYNOS4,
> +};
> +
> +static struct flite_variant fimc_lite0_variant_exynos5 = {
> + .max_width = 8192,
> + .max_height = 8192,
> + .out_width_align = 8,
> + .win_hor_offs_align = 2,
> + .out_hor_offs_align = 8,
Please see my comment to patch 03/12.
> + .version = FLITE_VER_EXYNOS5,
> };
>
> /* EXYNOS4212, EXYNOS4412 */
> @@ -1663,6 +1673,15 @@ static struct flite_drvdata fimc_lite_drvdata_exynos4 = {
> },
> };
>
> +/* EXYNOS5250 */
> +static struct flite_drvdata fimc_lite_drvdata_exynos5 = {
> + .variant = {
> + [0] =&fimc_lite0_variant_exynos5,
> + [1] =&fimc_lite0_variant_exynos5,
> + [2] =&fimc_lite0_variant_exynos5,
> + },
> +};
> +
> static struct platform_device_id fimc_lite_driver_ids[] = {
> {
> .name = "exynos-fimc-lite",
> @@ -1677,6 +1696,10 @@ static const struct of_device_id flite_of_match[] = {
> .compatible = "samsung,exynos4212-fimc-lite",
> .data =&fimc_lite_drvdata_exynos4,
> },
> + {
> + .compatible = "samsung,exynos5250-fimc-lite",
> + .data =&fimc_lite_drvdata_exynos5,
> + },
> { /* sentinel */ },
> };
> MODULE_DEVICE_TABLE(of, flite_of_match);
> diff --git a/drivers/media/platform/s5p-fimc/fimc-lite.h b/drivers/media/platform/s5p-fimc/fimc-lite.h
> index 66d6eeb..ef43fe0 100644
> --- a/drivers/media/platform/s5p-fimc/fimc-lite.h
> +++ b/drivers/media/platform/s5p-fimc/fimc-lite.h
> @@ -28,7 +28,7 @@
>
> #define FIMC_LITE_DRV_NAME "exynos-fimc-lite"
> #define FLITE_CLK_NAME "flite"
> -#define FIMC_LITE_MAX_DEVS 2
> +#define FIMC_LITE_MAX_DEVS 3
> #define FLITE_REQ_BUFS_MIN 2
>
> /* Bit index definitions for struct fimc_lite::state */
> @@ -49,12 +49,17 @@ enum {
> #define FLITE_SD_PAD_SOURCE_ISP 2
> #define FLITE_SD_PADS_NUM 3
>
> +#define FLITE_VER_EXYNOS4 0
> +#define FLITE_VER_EXYNOS5 1
I would prefer not using explicit version and rather put each
quirk in the driver data structure, so we can avoid those
multiple if (version == ...) checks all over in the code, should
more revision of this IP come in future SoCs.
next prev parent reply other threads:[~2013-03-10 20:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 11:53 [RFC 00/12] Adding media device driver for Exynos imaging subsystem Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 01/12] media: s5p-fimc: modify existing mdev to use common pipeline Shaik Ameer Basha
2013-03-10 22:00 ` Sylwester Nawrocki
2013-03-11 6:41 ` Shaik Ameer Basha
2013-03-14 0:01 ` Sylwester Nawrocki
2013-03-06 11:53 ` [RFC 02/12] fimc-lite: Adding Exynos5 compatibility to fimc-lite driver Shaik Ameer Basha
2013-03-10 20:36 ` Sylwester Nawrocki [this message]
2013-03-11 6:41 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 03/12] media: fimc-lite: Adding support for Exynos5 Shaik Ameer Basha
2013-03-10 20:39 ` Sylwester Nawrocki
2013-03-11 6:43 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 04/12] s5p-csis: Adding Exynos5250 compatibility Shaik Ameer Basha
2013-03-10 20:40 ` Sylwester Nawrocki
2013-03-11 6:58 ` Shaik Ameer Basha
2013-03-12 13:52 ` Sylwester Nawrocki
2013-03-06 11:53 ` [RFC 05/12] ARM: EXYNOS: Add devicetree node for mipi-csis driver for exynos5 Shaik Ameer Basha
2013-03-10 20:54 ` Sylwester Nawrocki
2013-03-11 6:58 ` Shaik Ameer Basha
2013-03-10 20:57 ` Sylwester Nawrocki
2013-03-11 6:58 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 06/12] ARM: EXYNOS: Add devicetree node for FIMC-LITE " Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 07/12] media: exynos5-is: Adding media device " Shaik Ameer Basha
2013-03-10 22:28 ` Sylwester Nawrocki
2013-03-11 6:59 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 08/12] ARM: dts: add camera specific pinctrl nodes for Exynos5250 SoC Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 09/12] ARM: dts: Adding pinctrl support to Exynos5250 i2c nodes Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 10/12] ARM: dts: Adding media device nodes to Exynos5 SoCs Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 11/12] media: m5mols: Adding dt support to m5mols driver Shaik Ameer Basha
2013-03-23 11:56 ` Sylwester Nawrocki
2013-03-25 5:39 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 12/12] ARM: dts: Add camera node to exynos5250-smdk5250.dts Shaik Ameer Basha
[not found] ` <1362570838-4737-13-git-send-email-shaik.ameer-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-03-23 12:18 ` Sylwester Nawrocki
2013-03-10 20:36 ` [RFC 00/12] Adding media device driver for Exynos imaging subsystem 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=513CEEDF.4010304@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=shaik.ameer@samsung.com \
--cc=shaik.samsung@gmail.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).