public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 01/04] OMAP3 SRF: Generic shared resource f/w
Date: Thu, 16 Oct 2008 11:27:40 -0700	[thread overview]
Message-ID: <200810161127.41161.david-b@pacbell.net> (raw)
In-Reply-To: <022301c92f99$24a25550$LocalHost@wipultra1382>

On Thursday 16 October 2008, Rajendra Nayak wrote:
> +       /* Function to change the level of the resource */
> +       int (*change_level)(struct shared_resource *res, u32 target_level);
> +       /* Function to validate the requested level of the resource */
> +       int (*validate_level)(struct shared_resource *res, u32 target_level);

What is a "target_level" supposed to represent?  Are they
even comparable, in the senses that

  (a) "42" for one resource is the same as "42" for another?
  (b) "42" includes "41", "40", etc?

There's no documentation at all on what seems to be a
fairly fundamental concept.  Or on the rest of it either;
the call syntax information is no real help.  What kind
of "resource" is involved, that might need a "level"?

Also, I suspect a flat namespace for all resources will
be a net lose.  Why isn't it scoped by devices, so that
device-relative "logical names" can be used instead of
requiring what have tended to be platform-specific and
very mutable "physical names"?  I notice that the call
to request a resource is already device-scoped ...

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

  reply	other threads:[~2008-10-16 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 14:11 [PATCH 01/04] OMAP3 SRF: Generic shared resource f/w Rajendra Nayak
2008-10-16 18:27 ` David Brownell [this message]
2008-10-17  5:27   ` Rajendra Nayak
2008-10-17  6:16 ` Dasgupta, Romit
2008-10-17  6:29   ` Rajendra Nayak
2008-10-17  7:35     ` Dasgupta, Romit
2008-10-17  7:43       ` Rajendra Nayak
2008-10-17 11:01         ` Dasgupta, Romit
2008-10-17 11:31           ` Dasgupta, Romit

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=200810161127.41161.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox