All of lore.kernel.org
 help / color / mirror / Atom feed
From: jassi brar <jassisinghbrar@gmail.com>
To: Ben Dooks <ben@trinity.fluff.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-samsung-soc@vger.kernel.org,
	Jassi Brar <jassi.brar@samsung.com>
Subject: Re: [PATCH 4/4] S3C64XX DSP: Added the CPU driver for PCM controllers
Date: Tue, 3 Nov 2009 15:59:46 +0900	[thread overview]
Message-ID: <1b68c6790911022259v2e4448eav9459384f164a7236@mail.gmail.com> (raw)
In-Reply-To: <20091102113932.GB23772@trinity.fluff.org>

On Mon, Nov 2, 2009 at 8:39 PM, Ben Dooks <ben@trinity.fluff.org> wrote:
>
>> > +   dai->private_data = dsp;
>> > +
>> > +   if (!base) {
>> > +           struct resource *res = platform_get_resource(pdev,
>> > +                                                        IORESOURCE_MEM,
>> > +                                                        0);
>> > +           if (!res) {
>> > +                   dev_err(dev, "Unable to get register resource\n");
>> > +                   return -ENXIO;
>> > +           }
>> > +
>> > +           if (!request_mem_region(res->start, resource_size(res),
>> > +                                   "s3c64xx-dsp")) {
>> > +                   dev_err(dev, "Unable to request register region\n");
>> > +                   return -EBUSY;
>> > +           }
>> > +
>> > +           base = res->start;
>> > +   }
>
> I would like to see platform_devices with their proper resources being
> mandatory for new drivers. We could do with this lot proplerly following
> the device driver model.
sorry, i didn't get it. could u please clarify more?


>> > +/* Module information */
>> > +MODULE_AUTHOR("Jaswinder Singh, <jassi.brar@samsung.com>");
>> > +MODULE_DESCRIPTION("S3C64XX PCM Controller Driver");
>
> no module license.
I missed that, will add. thanks.

>
> --
> Ben
>
> Q:      What's a light-year?
> A:      One-third less calories than a regular year.
>
>

  parent reply	other threads:[~2009-11-03  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  2:09 [PATCH 1/4] S3C64XX DSP: Added base and register defines for PCM controllers jassisinghbrar
2009-11-02  2:09 ` [PATCH 2/4] S3C64XX DSP: Added PCLK clock source for the " jassisinghbrar
2009-11-02  2:09   ` [PATCH 3/4] S3C64XX DSP: Defined PCM controller platform devices jassisinghbrar
2009-11-02  2:09     ` [PATCH 4/4] S3C64XX DSP: Added the CPU driver for PCM controllers jassisinghbrar
2009-11-02 11:17       ` Mark Brown
2009-11-02 11:39         ` Ben Dooks
2009-11-02 11:56           ` Mark Brown
2009-11-03  6:59           ` jassi brar [this message]
2009-11-03  9:54             ` Mark Brown
2009-11-03  2:42         ` jassi brar
2009-11-03  9:52           ` Mark Brown

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=1b68c6790911022259v2e4448eav9459384f164a7236@mail.gmail.com \
    --to=jassisinghbrar@gmail.com \
    --cc=ben@trinity.fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jassi.brar@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.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 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.