All of lore.kernel.org
 help / color / mirror / Atom feed
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 6/7] ASoC: S3C64XX: Pass I2S base address from platform	data
Date: Wed, 9 Dec 2009 11:25:22 +0000	[thread overview]
Message-ID: <20091209112521.GG19851@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1b68c6790912090314v379883deofaf71199e9d1bcb3@mail.gmail.com>

On Wed, Dec 09, 2009 at 08:14:24PM +0900, jassi brar wrote:
> On Wed, Dec 9, 2009 at 8:09 PM, Mark Brown

> >> +     if (!request_mem_region(res->start, resource_size(res),
> >> +                                                     "s3c64xx-i2s")) {
> >> +             dev_err(&pdev->dev, "Unable to request SFR region\n");
> >> +             return -EBUSY;
> >> +     }
> >> +

> > This feels like it should be in the patch that requested the resource
> > rather than here.  Probably ought to have a version that does the
> > request in 2.6.33 too if we can...

> that patch is only for setting DMA channel and dst addresses, so we
> request MEM resource there.

I'm not sure I follow?  In any case the real issue here is that looking
at this change and it's hard to see how it's immediately related to the
subject of the patch; it's not about how the data is passed and somewhat
distant from the code which does do the passing.

> > A comment explaining why we're doing the subtraction wouldn't hurt; the
> > code is OK.

> its just that i didn't want to reorder the code and MEM resource was requested
> into a temporary variable 'res' not immediately before this call. At this point
> res->start should do too though.

Yes, I saw - all I'm saying is that putting a note in the code 

      reply	other threads:[~2009-12-09 11:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09  4:29 [PATCH 6/7] ASoC: S3C64XX: Pass I2S base address from platform data jassisinghbrar
2009-12-09 11:09 ` Mark Brown
2009-12-09 11:14   ` jassi brar
2009-12-09 11:25     ` Mark Brown [this message]

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=20091209112521.GG19851@opensource.wolfsonmicro.com \
    --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.