public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, b-cousson@ti.com,
	khilman@deeprootsystems.com
Subject: Re: [PATCH 5/6] OMAP: powerdomain: Arch specific funcs for mem control
Date: Tue, 16 Nov 2010 17:09:38 +0100	[thread overview]
Message-ID: <20101116170938.0d83e1e4@surf> (raw)
In-Reply-To: <1289921886-5139-6-git-send-email-rnayak@ti.com>

Hello,

On Tue, 16 Nov 2010 21:08:05 +0530
Rajendra Nayak <rnayak@ti.com> wrote:

> Define the following architecture specific funtions for omap2/3/4

funtions -> functions.

> +/* Common Internal functions used across OMAP rev's*/
> +int _get_mem_bank_onstate_mask(u8 bank)
> +{
> +	switch (bank) {
> +	case 0:
> +		return OMAP_MEM0_ONSTATE_MASK;
> +	case 1:
> +		return OMAP_MEM1_ONSTATE_MASK;
> +	case 2:
> +		return OMAP_MEM2_ONSTATE_MASK;
> +	case 3:
> +		return OMAP_MEM3_ONSTATE_MASK;
> +	case 4:
> +		return OMAP_MEM4_ONSTATE_MASK;
> +	default:
> +		WARN_ON(1); /* should never happen */
> +		return -EEXIST;

EEXIST is the error code for "File exists", so here I would rather
expect something like ENOENT. But I understand that it was already
-EEXIST in the existing code.

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2010-11-16 16:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 15:38 [PATCH 0/6] Split powerdomain framework into plat specific/independent Rajendra Nayak
2010-11-16 15:38 ` [PATCH 1/6] OMAP: powerdomain: Move powerdomain.c from mach-omap2 to plat-omap Rajendra Nayak
2010-11-16 15:38   ` [PATCH 2/6] OMAP: powerdomain: Infrastructure to put arch specific code Rajendra Nayak
2010-11-16 15:38     ` [PATCH 3/6] OMAP: powerdomain: Arch specific funcs for state control Rajendra Nayak
2010-11-16 15:38       ` [PATCH 4/6] OMAP: powerdomain: Arch specific funcs for logic control Rajendra Nayak
2010-11-16 15:38         ` [PATCH 5/6] OMAP: powerdomain: Arch specific funcs for mem control Rajendra Nayak
2010-11-16 15:38           ` [PATCH 6/6] OMAP4: powerdomain: Add pwrdm_clear_all_prev_pwrst Rajendra Nayak
2010-11-29  0:31             ` Paul Walmsley
2010-11-16 16:09           ` Thomas Petazzoni [this message]
2010-11-29  0:28           ` [PATCH 5/6] OMAP: powerdomain: Arch specific funcs for mem control Paul Walmsley
2010-11-29  0:17         ` [PATCH 4/6] OMAP: powerdomain: Arch specific funcs for logic control Paul Walmsley
2010-11-29  0:14       ` [PATCH 3/6] OMAP: powerdomain: Arch specific funcs for state control Paul Walmsley
2010-11-30 15:47         ` Rajendra Nayak
2010-11-16 16:11     ` [PATCH 2/6] OMAP: powerdomain: Infrastructure to put arch specific code Thomas Petazzoni
2010-11-22  6:21       ` Rajendra Nayak
2010-11-29  0:07     ` Paul Walmsley
2010-11-29  0:05   ` [PATCH 1/6] OMAP: powerdomain: Move powerdomain.c from mach-omap2 to plat-omap Paul Walmsley
2010-11-29  9:22     ` Rajendra Nayak
2010-11-29  0:33 ` [PATCH 0/6] Split powerdomain framework into plat specific/independent Paul Walmsley
2010-11-29  9:24   ` Rajendra Nayak

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=20101116170938.0d83e1e4@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=b-cousson@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --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