public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Komal Shah <komal_shah802003@yahoo.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 2/2] ARM: OMAP: Use read/write_reg functions for PRCM.
Date: Fri, 11 Aug 2006 14:12:48 +0300	[thread overview]
Message-ID: <20060811111247.GN6720@atomide.com> (raw)
In-Reply-To: <1150285041.3056.263790643@webmail.messagingengine.com>

Hi,

* Komal Shah <komal_shah802003@yahoo.com> [060614 14:39]:
> This patch will break the pm.c and pm-domain.c if CONFIG_PM is enabled.

No problem. I'd actually prefer to have a patch that does not touch pm.c
and pm-domain.c. There's another patch coming for PM stuff that already
does not need prcm-regs.h much any longer.
 
> pm.c changes.
> - Use prcm_read/write_reg for preg(...)?? _or_ get function
>   for each of that reg.
> 
> - get/set_reg functions for INTC registers??
> 
> - get_reg functions for SDRC_DLLA/B for using with
>   omap2_sram_suspend ??
> 
> - Adding proc based register information as in OMAP1?
> 
> pm-domain.c
> - Add if (cpu_is_omap2420()) and assigning prcm_base at init.
> - Use prcm_readl/writel for other registers which uses _reg32 
>   based access as of now.

In general looks OK to me, could you please refresh and repost all your
pending patches? Let's plan on starting to integrate this as soon as we
have verified the generic irq stuff has not broken anything.

Regards,

Tony

      reply	other threads:[~2006-08-11 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 11:37 [PATCH 2/2] ARM: OMAP: Use read/write_reg functions for PRCM Komal Shah
2006-08-11 11:12 ` Tony Lindgren [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=20060811111247.GN6720@atomide.com \
    --to=tony@atomide.com \
    --cc=komal_shah802003@yahoo.com \
    --cc=linux-omap-open-source@linux.omap.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