[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140725055447.GC29136@MrMyself>
Date: Fri, 25 Jul 2014 13:54:48 +0800
From: Nicolin Chen <Guangyu.Chen@...escale.com>
To: Varka Bhadram <varkabhadram@...il.com>
CC: Nicolin Chen <nicoleotsuka@...il.com>, <broonie@...nel.org>,
<robh+dt@...nel.org>, <pawel.moll@....com>, <mark.rutland@....com>,
<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
<rdunlap@...radead.org>, <lgirdwood@...il.com>, <perex@...ex.cz>,
<tiwai@...e.de>, <timur@...i.org>, <grant.likely@...aro.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<alsa-devel@...a-project.org>, <linuxppc-dev@...ts.ozlabs.org>,
<shawn.guo@...aro.org>, <b02247@...escale.com>,
<b42378@...escale.com>, <tklauser@...tanz.ch>
Subject: Re: [PATCH v3 2/2] ASoC: fsl_asrc: Add ASRC ASoC CPU DAI and
platform drivers
Hi Varka,
Regarding a point you suggested.
On Fri, Jul 25, 2014 at 09:54:43AM +0530, Varka Bhadram wrote:
> On 07/25/2014 09:33 AM, Nicolin Chen wrote:
> (...)
>
> >+
> >+static const struct platform_device_id fsl_asrc_devtype[] = {
> >+ {
> >+ .name = "imx35-asrc",
> >+ .driver_data = IMX35_ASRC,
> >+ }, {
> >+ .name = "imx53-asrc",
> >+ .driver_data = IMX53_ASRC,
> >+ }, {
> >+ /* sentinel */
> >+ }
> >+};
> >+MODULE_DEVICE_TABLE(platform, fsl_asrc_devtype);
> >+
> >+static const struct of_device_id fsl_asrc_ids[] = {
> >+ {
> >+ .compatible = "fsl,imx35-asrc",
> >+ .data = &fsl_asrc_devtype[IMX35_ASRC],
> >+ }, {
> >+ .compatible = "fsl,imx53-asrc",
> >+ .data = &fsl_asrc_devtype[IMX53_ASRC],
> >+ }, {
> >+ /* sentinel */
> >+ }
> >+};
> >+MODULE_DEVICE_TABLE(of, fsl_asrc_ids);
> >+
>
> move these ids after probe/remove... every driver follows same thing...
Hmm.. fsl_asrc_ids is called in probe(), so it's probably not a good choice
to put them after probe/remove. And actually not every driver does so.
For example drivers/i2c/busses/i2c-s3c2410.c
I think it should be okay to put here if it contains data.
Thank you,
Nicolin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists