devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Brian Austin <brian.austin-jGc1dHjMKG3QT0dZR+AlfA@public.gmane.org>
Cc: alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
	mark.rutland-5wv7dgnIgG8@public.gmane.org
Subject: Re: [PATCH v2 2/2] dt: binding: sound cs42l52 driver
Date: Wed, 13 Nov 2013 20:29:04 +0100	[thread overview]
Message-ID: <4248019.0NvEHjb6IO@flatron> (raw)
In-Reply-To: <alpine.DEB.2.10.1311131306150.28828-QCF2GsvuTPME07tKKVU2gpqQE7yCjDx5@public.gmane.org>

On Wednesday 13 of November 2013 13:10:51 Brian Austin wrote:
> On Wed, 13 Nov 2013, Tomasz Figa wrote:
> 
> >>>> +		 0x00 through 0x0F.
> >>>> +		 Frequency = (64xFs)/(N+2)
> >>>
> >>> I suppose N means the value of chgfreq property here, but this should be
> >>> clearly stated. Same for Fs - I suppose it is sampling frequency, but
> >>> is it default, minimum, maximum or maybe something else?
> >>>
> >> Frequency = (64xFs)/(N+2)
> >> N = chgfreq value
> >> Fs = sample rate
> >
> > As I mentioned in second part of my comment, is it default, minimum,
> > maximum or what kind of sample rate? Or is the sample rate fixed?
> >
> ah! Sorry, the rate is fixed for the stream. So it varies for what rate is 
> being used.
> 

OK, so the charge pump frequency varies with sampling rate. Well, I guess
that's fine to provide a raw register value then. The name is still a bit
misleading, though.

Maybe calling it cirrus,chgfreq-divisor would be better instead? Also the
description in binding documentation should explicitly state that it's the
raw value that needs to be written to the CHGFREQ register.

> >>>> +  - mica-sel   : MIC A single ended input select.  For Single-Ended
> >>>> +		 configuration, select which MIC to use.
> >>>> +		 0x00 = MIC1
> >>>> +		 0x01 = MIC2
> >>>> +  - micb-sel   : MIC B single ended input select.  For Single-Ended
> >>>> +		 configuration, select which MIC to use.
> >>>> +		 0x00 = MIC1
> >>>> +		 0x01 = MIC2
> >>>
> >>> Could you explain what are MIC A, MIC B, MIC1 and MIC2?
> >>>
> >> I can add a little more but it is best explained in the datasheet. I can
> >> add a little more explaination and reference the datasheet section. I feel
> >> this file might be the wrong place to go into too much depth of the pieces
> >> of the device when the datasheet could be referenced. Would a reference be
> >> OK?
> >>
> >
> > I meant just explaining to me, for the purpose of this review. However it
> > seems like the datasheet is publicly available, so let me just check this
> > there.
> >
> Sorry about that.
> 
> The CS42L52 has multiple input selections for microphones. Single-ended 
> and differential inputs are allowed for both Left Channel (MICA) and Right 
> Channel (MICB). The +- pins can be used for stereo or mono mics.

OK. After looking at the datasheet for a bit, I'm pretty much convinced
that these two properties should be rather represented as mixer controls
instead, for the purpose of channel mixing.

Whether the "Mic X Sel" control would be present in the mixer or not would
be implied by mic-X-differential property in DT.

Best regards,
Tomasz

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-11-13 19:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 15:44 [PATCH v2 1/2] ASoC: cs42l52: Add DeviceTree Support for CS42L52 Brian Austin
     [not found] ` <1384357474-28653-1-git-send-email-brian.austin-jGc1dHjMKG3QT0dZR+AlfA@public.gmane.org>
2013-11-13 15:44   ` [PATCH v2 2/2] dt: binding: sound cs42l52 driver Brian Austin
     [not found]     ` <1384357474-28653-2-git-send-email-brian.austin-jGc1dHjMKG3QT0dZR+AlfA@public.gmane.org>
2013-11-13 15:53       ` Kumar Gala
     [not found]         ` <9097292C-9233-49B3-995D-27574D544237-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2013-11-13 16:21           ` Brian Austin
2013-11-13 16:33       ` Tomasz Figa
2013-11-13 16:43         ` Mark Brown
     [not found]           ` <20131113164328.GW878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 16:47             ` Tomasz Figa
2013-11-13 18:16               ` Mark Brown
     [not found]                 ` <20131113181622.GZ878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 18:24                   ` Tomasz Figa
2013-11-13 19:49                     ` Mark Brown
     [not found]                       ` <20131113194915.GF878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 20:13                         ` Tomasz Figa
2013-11-13 18:58         ` Brian Austin
     [not found]           ` <alpine.DEB.2.10.1311131248290.28828-QCF2GsvuTPME07tKKVU2gpqQE7yCjDx5@public.gmane.org>
2013-11-13 19:01             ` Tomasz Figa
2013-11-13 19:10               ` Brian Austin
     [not found]                 ` <alpine.DEB.2.10.1311131306150.28828-QCF2GsvuTPME07tKKVU2gpqQE7yCjDx5@public.gmane.org>
2013-11-13 19:29                   ` Tomasz Figa [this message]
2013-11-13 20:24                     ` Brian Austin

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=4248019.0NvEHjb6IO@flatron \
    --to=tomasz.figa-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
    --cc=brian.austin-jGc1dHjMKG3QT0dZR+AlfA@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.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).