linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 18:22:45 +0200	[thread overview]
Message-ID: <1437063765.21215.18.camel@tiscali.nl> (raw)
In-Reply-To: <20150716150500.GO4039@sirena.org.uk>

On do, 2015-07-16 at 16:05 +0100, Mark Brown wrote:
> Why would this not be the case - what is the difference you beleive
> this driver has to other platform drivers?

It's my believe that for MODULE_ALIAS("platform:[...]") to be useful
there needs to be corresponding struct platform_device. For this patch
that would be a platform device named "rockchip-snd-max98090". (This is
something that I try to check rather carefully, because these devices
can be generated on the fly.)

I'm happy to drop this believe if someone shows me another way that
MODULE_ALIAS("platform:[...]") can actually be used.

So, in short, the difference between this driver and other platform
drivers is that, as far as I'm aware, this platform driver lacks a
corresponding platform device. Probably because OF support suffices to
get this module autoloaded.

Thanks,


Paul Bolle

  reply	other threads:[~2015-07-16 16:22 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
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 [this message]
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=1437063765.21215.18.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).