All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH 1/2] ASoC: Add support for Conexant CX2072X CODEC
Date: Mon, 06 May 2019 17:26:51 +0200	[thread overview]
Message-ID: <s5h4l674n9g.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190506140506.GQ14916@sirena.org.uk>

On Mon, 06 May 2019 16:05:06 +0200,
Mark Brown wrote:
> 
> > This is rather a question how generic the codec driver should be
> > written.  I changed the code in v5 patchset to embed the jack_gpio
> > stuff inside the codec driver side rather than the machine driver, so
> > the whole exported functions can be reduced now.  But, of course, it
> > slightly gives more implicit assumption about the hardware
> > implementations, too.  Though, the existing code seems to have already
> > fixed gpio / pin setups, so the other setups wouldn't have worked, in
> > anyway.
> 
> Like I say if the device is using the fact that the pin is a GPIO
> there's quite likely something wrong - that shouldn't be something that
> the user of an interrupt should need to see.

Yeah, unfortunately we have no reference, so the only chance would be
to test with another board that has a different setup.

> > > It's unlikely there are *no* default values - you'd kind of have to try
> > > to have a specific register range like this with genuinely floating
> > > values.  Given that the code for configuring the EQ was broken to IIRC
> > > never take effect I'd not be 100% surprisd if someone couldn't figure
> > > out why their settings weren't taking effect and just bodged something
> > > directly in the driver.
> 
> > Actually I'm fine to drop the whole EQ stuff that brings lots of black
> > magic.  Certainly it'll benefit us for code simplification.  Let's
> > see.
> 
> Probably worth checking to make sure the default EQ setup isn't too
> awful (though I guess the EQ is just turned off by default so it'll just
> be an uncorrected speaker/headphone which should be fine if not ideal).

A good point.  I checked the status now, and found that actually the
EQ and others won't appear in the normal playback / capture via HiFi
route, but only through DSP.  Since the normal usages with UCM profile
goes only via HiFi, EQ/DRC don't play any role.  So it's OK to remove
them, at least, for normal PC usages, as well as RPi HiFi extensions,
as it seems.


thanks,

Takashi

  reply	other threads:[~2019-05-06 15:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 14:13 [PATCH 0/2] ASoC: CX2072X codec support (revised) Takashi Iwai
2019-04-23 14:13 ` [PATCH 1/2] ASoC: Add support for Conexant CX2072X CODEC Takashi Iwai
2019-04-27 17:59   ` Mark Brown
2019-05-02  7:04     ` Takashi Iwai
2019-05-02  7:52       ` Takashi Iwai
2019-05-03  6:52         ` Mark Brown
     [not found]       ` <20190503064729.GF14916@sirena.org.uk>
2019-05-03  7:18         ` Takashi Iwai
     [not found]           ` <20190506042625.GK14916@sirena.org.uk>
2019-05-06  9:55             ` Takashi Iwai
2019-05-06 14:05               ` Mark Brown
2019-05-06 15:26                 ` Takashi Iwai [this message]
2019-05-08  8:10                   ` Mark Brown
2019-05-08  8:16                     ` Takashi Iwai
2019-05-08  8:59                       ` Mark Brown
2019-05-08  9:16                         ` Takashi Iwai
2019-05-08 10:10                           ` Mark Brown
2019-05-03  8:05         ` Takashi Iwai
2019-04-23 14:13 ` [PATCH 2/2] ASoC: Intel: Add machine driver for CX2072X on BYT/CHT platforms Takashi Iwai
2019-04-23 19:20   ` Pierre-Louis Bossart
2019-04-23 19:39     ` Takashi Iwai
2019-04-24 13:08       ` Takashi Iwai

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=s5h4l674n9g.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.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.