All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: ext Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 1/1 - try2] ASoC: add support for multiple cards/codecs in debugfs
Date: Thu, 1 Oct 2009 16:49:17 +0300	[thread overview]
Message-ID: <200910011649.17727.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <20091001110919.GC19998@rakim.wolfsonmicro.main>

On Thursday 01 October 2009 14:09:19 ext Mark Brown wrote:
> On Thu, Oct 01, 2009 at 02:02:04PM +0300, Peter Ujfalusi wrote:
> > On Thursday 01 October 2009 13:51:07 ext Mark Brown wrote:
> > > I'd rather use dev_name() for the CODEC itself if possible, that is
> > > more likely to be stable going forward and one of the immediate aims
> > > with the API refactoring is to remove socdev entirely at runtime.
> >
> > At this point the codec->dev was NULL, that is why I have used the
> > socdev->dev instead.
> 
> Right, your CODEC driver needs updating to current APIs.  Omitting the
> device name is a good fallback here since you won't be able to have more
> than one of the same device anyway if a device isn't provided.

One of the codec to be blamed is the twl4030 codec, but since that does not use 
any _device/_driver method to load, there is no dev to be assigned to codec-
>dev...
I don't know if it would make sense to use platform_driver_register (and 
associates) with it in the future.

The other codec, which I'm preparing for sending is using i2c probing, so I have 
fixed that, so now it has codec->dev initialized correctly.

> your CODEC driver needs updating to current APIs

Hmm, there are quite a bit of inconsistency among the codec drivers, so I'm not 
sure what is the correct way of doing this.
I will use the wm8993 driver for further fine tuning, since that seams to be 
rather new in the tree.

I'll send a patch later to fix this implementation:
if the codec->dev is valid, than it is going to use dev_name(codec->dev), if it 
is NULL, than it will use either the codec->name or provide the same string as 
the current implementation does ( {dev_name(socdev->dev)}-{codec->name} ), 
whichever is the preferred.

Thanks,
Péter

  reply	other threads:[~2009-10-01 13:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01  7:32 [PATCH 0/1 - try2] ASoC: debugfs support improvement Peter Ujfalusi
2009-10-01  7:32 ` [PATCH 1/1 - try2] ASoC: add support for multiple cards/codecs in debugfs Peter Ujfalusi
2009-10-01 10:51   ` Mark Brown
2009-10-01 11:02     ` Peter Ujfalusi
2009-10-01 11:09       ` Mark Brown
2009-10-01 13:49         ` Peter Ujfalusi [this message]
2009-10-01 14:06           ` Mark Brown
2009-10-01 11:19       ` Mark Brown
2009-10-01 13:06         ` Peter Ujfalusi

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=200910011649.17727.peter.ujfalusi@nokia.com \
    --to=peter.ujfalusi@nokia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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.