All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: imx-spdif: Use module_init() to handle platform_device_register()
Date: Fri, 20 Dec 2013 15:02:06 +0800	[thread overview]
Message-ID: <20131220070204.GA15246@MrMyself> (raw)
In-Reply-To: <20131218130415.GO28455@sirena.org.uk>

On Wed, Dec 18, 2013 at 01:04:15PM +0000, Mark Brown wrote:
> > Although I'll continue finding another way to register it tomorrow, I think
> > it's better to make a simple report for this solution.
> 
> > And if you have any idea, please guide me.
> 
> There's still the options of either registering the dummy devices in the
> core (rather than in a specific module where two modules could conflict
> with each other) or registering a subdevice for the card that I
> mentioned the other day.  Of those two registering in the core seems
> better - it's basically the same as your current idea but means that two
> card drivers that need this won't conflict with each other.

I'd love to try these two even though it should be a bit tougher.

Thank you for the ideas.
Nicolin Chen

      reply	other threads:[~2013-12-20  7:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 10:36 [PATCH] ASoC: imx-spdif: Use module_init() to handle platform_device_register() Nicolin Chen
2013-12-16 19:47 ` Mark Brown
2013-12-16 21:19   ` Russell King - ARM Linux
2013-12-16 22:17     ` Mark Brown
2013-12-17  3:05       ` Nicolin Chen
2013-12-17 10:31       ` Nicolin Chen
2013-12-18 13:04         ` Mark Brown
2013-12-20  7:02           ` Nicolin Chen [this message]

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=20131220070204.GA15246@MrMyself \
    --to=guangyu.chen@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux@arm.linux.org.uk \
    --cc=tiwai@suse.de \
    /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.