From: Tomasz Figa <t.figa@samsung.com>
To: Leela Krishna Amudala <l.krishna@samsung.com>
Cc: kgene.kim@samsung.com, devicetree-discuss@lists.ozlabs.org,
dri-devel@lists.freedesktop.org,
laurent.pinchart@ideasonboard.com, m.szyprowski@samsung.com
Subject: Re: [PATCH V3 1/2] drm/exynos: add platform_device_id table and driver data for exynos5 drm fimd
Date: Wed, 05 Sep 2012 09:52:54 +0200 [thread overview]
Message-ID: <1560378.upcWAQYQSz@amdc1227> (raw)
In-Reply-To: <1345111689-14601-2-git-send-email-l.krishna@samsung.com>
Hi Leela,
See my comments inline.
On Thursday 16 of August 2012 12:08:08 Leela Krishna Amudala wrote:
> +enum fimd_version_type {
> + VERSION_8, /* FIMD_VERSION8 */
> +};
> +
> +struct drm_fimd_driver_data {
> + enum fimd_version_type fimd_ver;
> +};
> +
> +struct drm_fimd_driver_data exynos5_drm_fimd_driver_data = {
> + .fimd_ver = VERSION_8,
> +};
I think that the approach with timing_base, as suggested by Joonyoung Shim,
would be much cleaner.
> +static struct platform_device_id exynos_drm_fimd_driver_ids[] = {
> + {
> + .name = "exynos4-fb",
> + }, {
> + .name = "exynos5-drm-fimd",
> + .driver_data = (unsigned long)&exynos5_drm_fimd_driver_data,
> + },
> + {},
> +};
> +MODULE_DEVICE_TABLE(platform, exynos_drm_fimd_driver_ids);
If I see correctly, this will crash on a null pointer dereference on
Exynos4 without DT, because of NULL driver_data.
P.S. I think you should CC linux-arm-kernel and linux-samsung-soc lists
when submitting patches related to ARM and Samsung SoCs.
Best regards,
--
Tomasz Figa
Samsung Poland R&D Center
next prev parent reply other threads:[~2012-09-05 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 10:08 [PATCH V3 0/2] video: drm: Add Device tree support to DRM-FIMD Leela Krishna Amudala
[not found] ` <1345111689-14601-1-git-send-email-l.krishna-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-08-16 10:08 ` [PATCH V3 1/2] drm/exynos: add platform_device_id table and driver data for exynos5 drm fimd Leela Krishna Amudala
[not found] ` <1345111689-14601-2-git-send-email-l.krishna-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-08-17 0:48 ` Joonyoung Shim
[not found] ` <CAPLVkLt8QTahTK6GU35-hM6nb27TVxM8Cief2qixntMT6yGECQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-17 9:37 ` Leela Krishna Amudala
2012-09-04 14:15 ` InKi Dae
[not found] ` <CAAQKjZM_xrosDeBytOySJBagNyzNz5t6fk7uAepTq64C0kcejw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-09-04 16:51 ` Leela Krishna Amudala
2012-09-05 7:52 ` Tomasz Figa [this message]
2012-08-16 10:08 ` [PATCH V3 2/2] video: drm: exynos: Add device tree support Leela Krishna Amudala
[not found] ` <1345111689-14601-3-git-send-email-l.krishna-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-08-17 1:25 ` Joonyoung Shim
[not found] ` <CAPLVkLsoxUO6B3UyxYxYiWqmY=F9JUL2PSS3v-1JjT1rHgRODA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-17 9:37 ` Leela Krishna Amudala
2012-08-20 1:44 ` Joonyoung Shim
2012-08-27 8:04 ` Sascha Hauer
2012-09-04 14:12 ` InKi Dae
[not found] ` <CAAQKjZPq2o6s_bxmFePA89Xw67gupAhE=bDp22Lfa6bd5dAYWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-09-04 16:44 ` Leela Krishna Amudala
2012-08-27 9:50 ` [PATCH V3 0/2] video: drm: Add Device tree support to DRM-FIMD Leela Krishna Amudala
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=1560378.upcWAQYQSz@amdc1227 \
--to=t.figa@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kgene.kim@samsung.com \
--cc=l.krishna@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=m.szyprowski@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