From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ASoC: rockchip: Add machine driver for max98090 codec
Date: Thu, 16 Jul 2015 10:05:44 +0200 [thread overview]
Message-ID: <1437033944.27428.11.camel@tiscali.nl> (raw)
In-Reply-To: <1436930143-31361-2-git-send-email-zhengxing@rock-chips.com>
On wo, 2015-07-15 at 11:15 +0800, Xing Zheng wrote:
> --- /dev/null
> +++ b/sound/soc/rockchip/rockchip_max98090.c
> +#define DRV_NAME "rockchip-snd-max98090"
> +static const struct of_device_id rockchip_max98090_of_match[] = {
> + { .compatible = "rockchip,rockchip-audio-max98090", },
> + {},
> +};
> +
> +static struct platform_driver snd_rk_mc_driver = {
> + .probe = snd_rk_mc_probe,
> + .remove = snd_rk_mc_remove,
> + .driver = {
> + .name = DRV_NAME,
> + .owner = THIS_MODULE,
> + .pm = &snd_soc_pm_ops,
> + .of_match_table = rockchip_max98090_of_match,
> + },
> +};
> +
> +module_platform_driver(snd_rk_mc_driver);
Nit: empty line here.
> +MODULE_AUTHOR("jianqun <jay.xu@rock-chips.com>");
> +MODULE_DESCRIPTION("Rockchip max98090 machine ASoC driver");
> +MODULE_LICENSE("GPL v2");
> +MODULE_ALIAS("platform:" DRV_NAME);
This seems only useful if there's a corresponding struct
platform_device. Ie, a platform_device with a "rockchip-snd-max98090"
.name, which will trigger a "MODALIAS=platform:rockchip-snd-max98090"
uevent when it's created. But I couldn't find where such a
platform_device is created.
Did I miss something? Or is there another way this alias is useful here?
> +MODULE_DEVICE_TABLE(of, rockchip_max98090_of_match);
The common pattern is to put MODULE_DEVICE_TABLE() directly after the
table it exports.
Likewise for 2/2 (except the empty line nit, that is).
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-07-16 8:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 3:15 [PATCH 0/2] Add codec machine driver for rockchip platform Xing Zheng
2015-07-15 3:15 ` [PATCH 1/2] ASoC: rockchip: Add machine driver for max98090 codec Xing Zheng
2015-07-16 8:05 ` Paul Bolle [this message]
2015-07-16 11:00 ` Mark Brown
2015-07-16 11:22 ` zhengxing
2015-07-16 11:47 ` Paul Bolle
2015-07-16 12:55 ` Mark Brown
2015-07-16 14:15 ` Paul Bolle
2015-07-16 15:05 ` Mark Brown
2015-07-16 16:22 ` Paul Bolle
2015-07-16 19:57 ` Mark Brown
2015-07-17 2:17 ` zhengxing
2015-07-16 11:20 ` zhengxing
2015-07-16 11:49 ` Paul Bolle
2015-07-16 11:59 ` zhengxing
2015-07-16 14:19 ` Paul Bolle
2015-07-16 15:25 ` Jiang Liu
2015-07-16 16:08 ` Paul Bolle
2015-07-17 18:04 ` Mark Brown
2015-07-18 3:51 ` zhengxing
2015-07-18 4:15 ` zhengxing
2015-07-15 3:15 ` [PATCH 2/2] ASoC: rockchip: Add machine driver for rt5645/rt5650 codec Xing Zheng
2015-07-17 18:11 ` Mark Brown
2015-07-18 3:52 ` zhengxing
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=1437033944.27428.11.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.org \
/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).