From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: timur@tabi.org, alsa-devel@alsa-project.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rob@landley.net, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.de, grant.likely@linaro.org, shawn.guo@linaro.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] ASoC: fsl_esai: Add ESAI CPU DAI driver
Date: Sat, 11 Jan 2014 00:45:44 +0800 [thread overview]
Message-ID: <20140110164543.GB17609@MrMyself> (raw)
In-Reply-To: <20140110165229.GP29039@sirena.org.uk>
On Fri, Jan 10, 2014 at 04:52:29PM +0000, Mark Brown wrote:
> On Fri, Jan 10, 2014 at 11:48:25PM +0800, Nicolin Chen wrote:
>
> > I think I start to understand the point here: If a user only needs to playback
> > the default case - 44.1KHz for example, the driver can just configure all the
> > dividers once at the beginning, not every time, so that we can save further
> > register overriding operation or even complicated clock selection and divisor
> > calculation, which obviously makes the procedure clean and reduces the system
> > loading even if it might be just in a slight level.
>
> > Is this the reason, or maybe one of the reasons, to the defaults providing?
>
> The main thing is that if the DAI driver does it then it's less code in
> the machine drivers using it - what tends to happen otherwise is that
> quite a few machine drivers end up replicating the same logic. Hardware
> designers tend to do a lot of cut'n'paste with these things so even if
> the CODEC is different the clocking is often very similar.
Point taken. And it also depends on how common the defaults would be.
I think I should try to figure out a comparably generic template for
the clock selection and its rate settings here and also check other
redundant places.
I learned another lesson today. Thank you indeed.
Nicolin
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
alsa-devel@alsa-project.org, shawn.guo@linaro.org,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk, tiwai@suse.de,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
timur@tabi.org, lgirdwood@gmail.com, robh+dt@kernel.org,
rob@landley.net, galak@codeaurora.org, grant.likely@linaro.org,
perex@perex.cz, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] ASoC: fsl_esai: Add ESAI CPU DAI driver
Date: Sat, 11 Jan 2014 00:45:44 +0800 [thread overview]
Message-ID: <20140110164543.GB17609@MrMyself> (raw)
In-Reply-To: <20140110165229.GP29039@sirena.org.uk>
On Fri, Jan 10, 2014 at 04:52:29PM +0000, Mark Brown wrote:
> On Fri, Jan 10, 2014 at 11:48:25PM +0800, Nicolin Chen wrote:
>
> > I think I start to understand the point here: If a user only needs to playback
> > the default case - 44.1KHz for example, the driver can just configure all the
> > dividers once at the beginning, not every time, so that we can save further
> > register overriding operation or even complicated clock selection and divisor
> > calculation, which obviously makes the procedure clean and reduces the system
> > loading even if it might be just in a slight level.
>
> > Is this the reason, or maybe one of the reasons, to the defaults providing?
>
> The main thing is that if the DAI driver does it then it's less code in
> the machine drivers using it - what tends to happen otherwise is that
> quite a few machine drivers end up replicating the same logic. Hardware
> designers tend to do a lot of cut'n'paste with these things so even if
> the CODEC is different the clocking is often very similar.
Point taken. And it also depends on how common the defaults would be.
I think I should try to figure out a comparably generic template for
the clock selection and its rate settings here and also check other
redundant places.
I learned another lesson today. Thank you indeed.
Nicolin
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: <timur@tabi.org>, <alsa-devel@alsa-project.org>,
<robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <rob@landley.net>, <lgirdwood@gmail.com>,
<perex@perex.cz>, <tiwai@suse.de>, <grant.likely@linaro.org>,
<shawn.guo@linaro.org>, <devicetree@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2] ASoC: fsl_esai: Add ESAI CPU DAI driver
Date: Sat, 11 Jan 2014 00:45:44 +0800 [thread overview]
Message-ID: <20140110164543.GB17609@MrMyself> (raw)
In-Reply-To: <20140110165229.GP29039@sirena.org.uk>
On Fri, Jan 10, 2014 at 04:52:29PM +0000, Mark Brown wrote:
> On Fri, Jan 10, 2014 at 11:48:25PM +0800, Nicolin Chen wrote:
>
> > I think I start to understand the point here: If a user only needs to playback
> > the default case - 44.1KHz for example, the driver can just configure all the
> > dividers once at the beginning, not every time, so that we can save further
> > register overriding operation or even complicated clock selection and divisor
> > calculation, which obviously makes the procedure clean and reduces the system
> > loading even if it might be just in a slight level.
>
> > Is this the reason, or maybe one of the reasons, to the defaults providing?
>
> The main thing is that if the DAI driver does it then it's less code in
> the machine drivers using it - what tends to happen otherwise is that
> quite a few machine drivers end up replicating the same logic. Hardware
> designers tend to do a lot of cut'n'paste with these things so even if
> the CODEC is different the clocking is often very similar.
Point taken. And it also depends on how common the defaults would be.
I think I should try to figure out a comparably generic template for
the clock selection and its rate settings here and also check other
redundant places.
I learned another lesson today. Thank you indeed.
Nicolin
next prev parent reply other threads:[~2014-01-10 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 10:57 [PATCH v2] ASoC: fsl_esai: Add ESAI CPU DAI driver Nicolin Chen
2014-01-09 10:57 ` Nicolin Chen
2014-01-09 10:57 ` Nicolin Chen
2014-01-09 18:44 ` Mark Brown
2014-01-09 18:44 ` Mark Brown
2014-01-09 18:44 ` Mark Brown
[not found] ` <20140110023252.GA16467@MrMyself>
2014-01-10 2:35 ` Nicolin Chen
2014-01-10 2:35 ` Nicolin Chen
2014-01-10 2:35 ` Nicolin Chen
2014-01-10 12:04 ` Mark Brown
2014-01-10 12:04 ` Mark Brown
2014-01-10 12:04 ` Mark Brown
2014-01-10 13:03 ` Nicolin Chen
2014-01-10 13:03 ` Nicolin Chen
2014-01-10 13:03 ` Nicolin Chen
2014-01-10 13:26 ` Mark Brown
2014-01-10 13:26 ` Mark Brown
2014-01-10 15:48 ` Nicolin Chen
2014-01-10 15:48 ` Nicolin Chen
2014-01-10 15:48 ` Nicolin Chen
2014-01-10 16:52 ` Mark Brown
2014-01-10 16:52 ` Mark Brown
2014-01-10 16:45 ` Nicolin Chen [this message]
2014-01-10 16:45 ` Nicolin Chen
2014-01-10 16:45 ` Nicolin Chen
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=20140110164543.GB17609@MrMyself \
--to=guangyu.chen@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=perex@perex.cz \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=timur@tabi.org \
--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.