From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-omap@vger.kernel.org
Subject: Re: [PATCH 02/16] ARM: OMAP2: Split sleep.S into sleep242x.S and sleep243x.S
Date: Wed, 20 Aug 2008 10:36:18 +0300 [thread overview]
Message-ID: <20080820073617.GC28862@atomide.com> (raw)
In-Reply-To: <20080819170311.GB17034@flint.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [080819 20:03]:
> On Fri, Jun 06, 2008 at 07:12:28PM -0700, Tony Lindgren wrote:
> > Some register offsets are different for 242x and 243x. This
> > will allow compiling sleep code for both chips into the same
> > kernel.
> >
> > Note that some PM patches are still missing. The PM patches will
> > be added later on once the base files are in sync with linux-omap
> > tree.
>
> Please use git diff -M, since it makes the changes across renames more
> obvious.
OK
> > +ENTRY(omap242x_idle_loop_suspend)
> > + stmfd sp!, {r0, lr} @ save registers on stack
> > + mov r0, #0x0 @ clear for mrc call
> > + mcr p15, 0, r0, c7, c0, 4 @ wait for interrupt
> > + ldmfd sp!, {r0, pc} @ restore regs and return
>
> What's been lost because of the lack of git diff -M here is the real
> change:
>
> -ENTRY(omap24xx_idle_loop_suspend)
> +ENTRY(omap242x_idle_loop_suspend)
> stmfd sp!, {r0, lr} @ save registers on stack
> - mov r0, #0 @ clear for mcr setup
> + mov r0, #0x0 @ clear for mrc call
> mcr p15, 0, r0, c7, c0, 4 @ wait for interrupt
> ldmfd sp!, {r0, pc} @ restore regs and return
>
> which makes the problem stand out. That change of the 'mov' line
> along with the comment is completely bogus. In fact, the change to
> the comment is clearly wrong. The same applies to sleep243x.S
Will remove.
> Realistically, the only real difference between the two files are
> these lines:
>
> omap2_ocs_sdrc_power:
> - .word OMAP242X_SDRC_REGADDR(SDRC_POWER)
> + .word OMAP243X_SDRC_REGADDR(SDRC_POWER)
> A_SDRC0:
> .word A_SDRC0_V
> omap2_ocs_sdrc_dlla_ctrl:
> - .word OMAP242X_SDRC_REGADDR(SDRC_DLLA_CTRL)
> + .word OMAP243X_SDRC_REGADDR(SDRC_DLLA_CTRL)
>
> so is doubling the size of this code really justified?
Yes duplication is a problem. We had code that was dynamically
rewriting the addresses but it was not very easy to follow and
hard to debug. This code is only compiled in twice if both 242x
and 243x are both selected though.
> Looking harder at this code:
>
> ENTRY(omap242x_cpu_suspend)
> stmfd sp!, {r0 - r12, lr} @ save registers on stack
> ...
> mov r5, #0x2000 @ set delay (DPLL relock + DLL relock)
> ...
> nop
> mcr p15, 0, r2, c7, c0, 4 @ wait for interrupt
> nop
> loop:
> subs r5, r5, #0x1 @ awake, wait just a bit
> bne loop
>
> ldmfd sp!, {r0 - r12, pc} @ restore regs and return
>
> it's clear that registers are preserved across the wait-for-interrupt
> instruction, so I'm not sure why saving all the registers is really
> necessary, but that's only a side point to my main point, which is...
>
> ... that you could pass the addresses of these registers into the
> function, either directly:
>
> void omap24xx_cpu_suspend(u32 dll_ctrl, u32 cpu_revision,
> void __iomem *sdrc_pwr,
> void __iomem *sdrc_dlla_ctrl);
>
> or via a structure, and thereby avoid this duplication.
The structure would have to be also in SRAM then. I guess in this case
there are only two addresses, so passing them via into the function
should be enough. It's unlikely that this code changes any further
to need more addresses.
Will repost.
Tony
next prev parent reply other threads:[~2008-08-20 7:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 2:12 [PATCH 02/16] ARM: OMAP2: Split sleep.S into sleep242x.S and sleep243x.S Tony Lindgren
2008-06-07 2:12 ` [PATCH 03/16] ARM: OMAP2: Add non-CORE DPLL rate set code and M,N programming Tony Lindgren
2008-06-07 2:12 ` [PATCH 04/16] ARM: OMAP: Fix sparse, checkpatch warnings in OMAP2/3 PRCM/PM code Tony Lindgren
2008-06-07 2:12 ` [PATCH 05/16] ARM: OMAP2: Move sys_clkout2 clk to core_clkdm Tony Lindgren
2008-06-07 2:12 ` [PATCH 06/16] ARM: OMAP2: Add missing SSI L4 interface clock Tony Lindgren
2008-06-07 2:12 ` [PATCH 07/16] ARM: OMAP2: Add clkdm_get_pwrdm() Tony Lindgren
2008-06-07 2:12 ` [PATCH 08/16] ARM: OMAP2: Remove OMAP_PRM_REGADDR Tony Lindgren
2008-06-07 2:12 ` [PATCH 09/16] ARM: OMAP2: Remove OMAP_CM_REGADDR Tony Lindgren
2008-06-07 2:12 ` [PATCH 10/16] ARM: OMAP2: Use omap_globals for CPU detection for multi-omap Tony Lindgren
2008-06-07 2:12 ` [PATCH 11/16] ARM: OMAP2: Implement CPUfreq frequency table based on PRCM table Tony Lindgren
2008-06-07 2:12 ` [PATCH 12/16] ARM: OMAP2: Add pinmux support for omap34xx Tony Lindgren
2008-06-07 2:12 ` [PATCH 13/16] ARM: OMAP2: Fix sparse, checkpatch warnings fro GPMC code Tony Lindgren
2008-06-07 2:12 ` [PATCH 14/16] ARM: OMAP2: Misc updates from linux-omap tree Tony Lindgren
2008-06-07 2:12 ` [PATCH 15/16] ARM: OMAP2: Add minimal omap3430 support Tony Lindgren
2008-06-07 2:12 ` [PATCH 16/16] ARM: OMAP2: Fix sparse, checkpatch warnings in OMAP2/3 IRQ code Tony Lindgren
2008-06-17 9:43 ` [PATCH 15/16] ARM: OMAP2: Add minimal omap3430 support Tony Lindgren
2008-08-19 21:08 ` [PATCH 14/16] ARM: OMAP2: Misc updates from linux-omap tree Russell King - ARM Linux
2008-08-20 7:42 ` Tony Lindgren
2008-08-20 7:46 ` Russell King - ARM Linux
2008-08-20 8:50 ` Tony Lindgren
2008-08-23 22:43 ` Tony Lindgren
2008-08-19 17:29 ` [PATCH 07/16] ARM: OMAP2: Add clkdm_get_pwrdm() Russell King - ARM Linux
2008-08-20 7:37 ` Tony Lindgren
2008-08-23 22:38 ` Tony Lindgren
2008-08-19 17:21 ` [PATCH 04/16] ARM: OMAP: Fix sparse, checkpatch warnings in OMAP2/3 PRCM/PM code Russell King - ARM Linux
2008-08-23 22:36 ` Tony Lindgren
2008-08-19 17:03 ` [PATCH 02/16] ARM: OMAP2: Split sleep.S into sleep242x.S and sleep243x.S Russell King - ARM Linux
2008-08-20 7:36 ` Tony Lindgren [this message]
2008-08-23 22:15 ` Tony Lindgren
2008-08-23 22:23 ` Tony Lindgren
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=20080820073617.GC28862@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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