All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Derek [方德義]" <derek.fang@realtek.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Oder Chiou" <oder_chiou@realtek.com>,
	"Jack Yu" <jack.yu@realtek.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"Albert Chen" <albertchen@realtek.com>,
	"bard.liao@intel.com" <bard.liao@intel.com>,
	"Shuming [范書銘]" <shumingf@realtek.com>,
	"Flove(HsinFu)" <flove@realtek.com>
Subject: Re: [PATCH] ASoC: rt1308: Add RT1308 amplifier driver
Date: Tue, 23 Apr 2019 13:39:59 +0000	[thread overview]
Message-ID: <BC6F7617C38F3E4E8CA887E07B35B828011660AC@RTITEXDAG02.realtek.com.tw> (raw)
In-Reply-To: <20190417150518.GB5703@sirena.org.uk>

> 
> On Wed, Apr 17, 2019 at 11:40:28AM +0000, Derek wrote:
> 
> Please fix your mail client to word wrap within paragraphs at something
> substantially less than 80 columns.  Doing this makes your messages much
> easier to read and reply to.
> 
> > > The ones here with comments look an awful lot like they're system
> > > specific config which should be left up to either platform data (or
> > > DT/ACPI configuration) or done at runtime (like gains).  Some of the
> > > others like the pads configuration might also fit into that.
> 
> > We don't open the DA gain setting for user at runtime, so have to set
> > a default level in the init list.
> 
> That's not the way Linux drivers generally work...  is there some technical reason
> for that or is it just some kind of policy decision?

Maybe I could add a gain control for the user and set the gain to safety max level in init list for speaker protection.

> 
> > > > +static void rt1308_reset(struct regmap *regmap) {
> > > > +	regmap_write(regmap, RT1308_RESET, 0); }
> > >
> > > If we do need the init list shouldn't we also do a reninit every time we do a
> reset?
> 
> > The init list is only set at driver probe, not every time after resetting.
> 
> This is what I'm pointing out; if you don't restore these values then why set them
> at all?

OK, I could reinit after every time resetting.

> ------Please consider the environment before printing this e-mail.

  reply	other threads:[~2019-04-23 13:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16  2:22 [PATCH] ASoC: rt1308: Add RT1308 amplifier driver derek.fang
     [not found] ` <20190416153510.GE4834@sirena.org.uk>
     [not found]   ` <BC6F7617C38F3E4E8CA887E07B35B8280116192E@RTITMBSVM07.realtek.com.tw>
2019-04-17 15:05     ` Mark Brown
2019-04-23 13:39       ` Derek [方德義] [this message]
2019-05-08  6:45         ` Mark Brown
2019-05-08 13:17           ` Derek [方德義]
2019-05-12  8:06             ` Mark Brown
2019-05-13 13:54               ` Derek [方德義]
2019-05-13 14:56                 ` Mark Brown
2019-05-14 11:10                   ` Derek [方德義]
2019-05-15 16:14                     ` Mark Brown
2019-05-16 13:46                       ` Derek [方德義]
2019-05-16 16:52                         ` Mark Brown
2019-04-17 12:05 derek.fang

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=BC6F7617C38F3E4E8CA887E07B35B828011660AC@RTITEXDAG02.realtek.com.tw \
    --to=derek.fang@realtek.com \
    --cc=albertchen@realtek.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bard.liao@intel.com \
    --cc=broonie@kernel.org \
    --cc=flove@realtek.com \
    --cc=jack.yu@realtek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=shumingf@realtek.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.