From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: alsa-devel@alsa-project.org, Jassi Brar <jassi.brar@samsung.com>,
ben-linux@fluff.org
Subject: Re: [PATCH 7/7] S3C PCM: Added the CPU driver for PCM controllers
Date: Sat, 7 Nov 2009 12:27:37 +0000 [thread overview]
Message-ID: <20091107122737.GC3228@sirena.org.uk> (raw)
In-Reply-To: <1b68c6790911061918m339d6fe3tfba5ab3cebdfa00c@mail.gmail.com>
On Sat, Nov 07, 2009 at 12:18:10PM +0900, jassi brar wrote:
> On Sat, Nov 7, 2009 at 2:50 AM, Mark Brown
> > May as well just clk_set_rate() unconditionally, it'll do no harm to do
> > a null change.
> I believe the clock sources should be touched only when we can't do without it.
> clk_get_rate doesn't touch any register, but clk_set_rate does even if overwrite
> the same value.
I can see your point but if this is required it feels like something
that the clock API ought to be handling it - the same code should be
added pretty much every time the clock might be set.
> >> + /* Check for valid device index */
> >> + if (pdev->id >= ARRAY_SIZE(s3c_pcm)) {
> >> + dev_err(&pdev->dev, "id %d out of range\n", pdev->id);
> >> + return -EINVAL;
> >> + }
> >
> > id could be less than zero too.
> okay. Though i wonder how did it pass review in s3c64xx-i2s.c
When the drivers were originally merged there were quite a few issues
that needed fixing up but it was felt that it was better to get the code
into mainline where it could be worked on more readily. Ben didn't
really have any time to do much work on the drivers at the time and this
way it's easier for others to pitch in and fix up problems.
next prev parent reply other threads:[~2009-11-07 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 1:35 [PATCH 7/7] S3C PCM: Added the CPU driver for PCM controllers Jassi Brar
2009-11-06 17:50 ` Mark Brown
2009-11-07 3:18 ` jassi brar
2009-11-07 12:27 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-11 4:45 Jassi Brar
2009-11-04 8:29 [PATCH 1/7] S3C AUDIO: Rename s3c24xx_pcm prefix to generic s3c_audio jassisinghbrar
2009-11-04 8:29 ` [PATCH 2/7] S3C AUDIO: Rename s3c24xx-pcm driver " jassisinghbrar
2009-11-04 8:29 ` [PATCH 3/7] S3C64XX PCM: Define PCM Controller base registers jassisinghbrar
2009-11-04 8:29 ` [PATCH 4/7] S3C64XX PCM: Added PCLK clock source for the PCM controllers jassisinghbrar
2009-11-04 8:29 ` [PATCH 5/7] S3C AUDIO: Add header to pass platform data to device drivers jassisinghbrar
2009-11-04 8:29 ` [PATCH 6/7] S3C64XX PCM: Defined PCM controller platform devices jassisinghbrar
2009-11-04 8:29 ` [PATCH 7/7] S3C PCM: Added the CPU driver for PCM controllers jassisinghbrar
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=20091107122737.GC3228@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=jassi.brar@samsung.com \
--cc=jassisinghbrar@gmail.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.