All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@linux.intel.com>
To: Paul Bolle <pebolle@tiscali.nl>, zhengxing <zhengxing@rock-chips.com>
Cc: dgreid@chromium.org, dianders@chromium.org, heiko@sntech.de,
	sonnyrao@chromium.org, linux-rockchip@lists.infradead.org,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.de>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ASoC: rockchip: Add machine driver for max98090 codec
Date: Thu, 16 Jul 2015 23:25:18 +0800	[thread overview]
Message-ID: <55A7CCDE.9010701@linux.intel.com> (raw)
In-Reply-To: <1437056383.28351.23.camel@tiscali.nl>

On 2015/7/16 22:19, Paul Bolle wrote:
> Hi,
> 
> On do, 2015-07-16 at 19:59 +0800, zhengxing wrote:
>> I mean that the use of MODALIAS() in this patch, and I refered to
>> tegra_max98090.c(have been upstreamed) that used it like this also. So
>> I didn't care the using.
> 
> And I think the same problem with MODULE_ALIAS() can be found in that
> driver. Ie, where does the platform device that has a "tegra-snd
> -max98090" .name hide? (See the reply I just sent to mark for more
> details.)
May be that is hidden in some device tree files.
MODULE_ALIAS() is used by a driver to announce that it supports
such types of devices. And bus enumerator will create those
devices by probing hardware or parsing some configuration files.
Thanks!
Gerry

WARNING: multiple messages have this Message-ID (diff)
From: jiang.liu@linux.intel.com (Jiang Liu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ASoC: rockchip: Add machine driver for max98090 codec
Date: Thu, 16 Jul 2015 23:25:18 +0800	[thread overview]
Message-ID: <55A7CCDE.9010701@linux.intel.com> (raw)
In-Reply-To: <1437056383.28351.23.camel@tiscali.nl>

On 2015/7/16 22:19, Paul Bolle wrote:
> Hi,
> 
> On do, 2015-07-16 at 19:59 +0800, zhengxing wrote:
>> I mean that the use of MODALIAS() in this patch, and I refered to
>> tegra_max98090.c(have been upstreamed) that used it like this also. So
>> I didn't care the using.
> 
> And I think the same problem with MODULE_ALIAS() can be found in that
> driver. Ie, where does the platform device that has a "tegra-snd
> -max98090" .name hide? (See the reply I just sent to mark for more
> details.)
May be that is hidden in some device tree files.
MODULE_ALIAS() is used by a driver to announce that it supports
such types of devices. And bus enumerator will create those
devices by probing hardware or parsing some configuration files.
Thanks!
Gerry

  reply	other threads:[~2015-07-16 15:25 UTC|newest]

Thread overview: 53+ 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 ` Xing Zheng
2015-07-15  3:15 ` [PATCH 1/2] ASoC: rockchip: Add machine driver for max98090 codec Xing Zheng
2015-07-15  3:15   ` Xing Zheng
2015-07-16  8:05   ` Paul Bolle
2015-07-16  8:05     ` Paul Bolle
2015-07-16  8:05     ` Paul Bolle
2015-07-16 11:00     ` Mark Brown
2015-07-16 11:00       ` Mark Brown
2015-07-16 11:22       ` zhengxing
2015-07-16 11:22         ` zhengxing
2015-07-16 11:22         ` zhengxing
2015-07-16 11:47       ` Paul Bolle
2015-07-16 11:47         ` Paul Bolle
2015-07-16 12:55         ` Mark Brown
2015-07-16 12:55           ` Mark Brown
2015-07-16 14:15           ` Paul Bolle
2015-07-16 14:15             ` Paul Bolle
2015-07-16 15:05             ` Mark Brown
2015-07-16 15:05               ` Mark Brown
2015-07-16 16:22               ` Paul Bolle
2015-07-16 16:22                 ` Paul Bolle
2015-07-16 19:57                 ` Mark Brown
2015-07-16 19:57                   ` Mark Brown
2015-07-17  2:17             ` zhengxing
2015-07-17  2:17               ` zhengxing
2015-07-17  2:17               ` zhengxing
2015-07-16 11:20     ` zhengxing
2015-07-16 11:20       ` zhengxing
2015-07-16 11:20       ` zhengxing
2015-07-16 11:49       ` Paul Bolle
2015-07-16 11:49         ` Paul Bolle
2015-07-16 11:59         ` zhengxing
2015-07-16 11:59           ` zhengxing
2015-07-16 14:19           ` Paul Bolle
2015-07-16 14:19             ` Paul Bolle
2015-07-16 15:25             ` Jiang Liu [this message]
2015-07-16 15:25               ` Jiang Liu
2015-07-16 16:08               ` Paul Bolle
2015-07-16 16:08                 ` Paul Bolle
2015-07-17 18:04   ` Mark Brown
2015-07-17 18:04     ` Mark Brown
2015-07-18  3:51     ` zhengxing
2015-07-18  3:51       ` zhengxing
2015-07-18  4:15       ` zhengxing
2015-07-18  4:15         ` 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-15  3:15   ` Xing Zheng
2015-07-17 18:11   ` Mark Brown
2015-07-17 18:11     ` Mark Brown
2015-07-18  3:52     ` zhengxing
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=55A7CCDE.9010701@linux.intel.com \
    --to=jiang.liu@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=dgreid@chromium.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=pebolle@tiscali.nl \
    --cc=perex@perex.cz \
    --cc=sonnyrao@chromium.org \
    --cc=tiwai@suse.de \
    --cc=zhengxing@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.