All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH 3/3] m68k: merge mmu and non-mmu versions of time.c
Date: Tue, 21 Feb 2012 16:37:09 +1000	[thread overview]
Message-ID: <4F433B95.6020604@snapgear.com> (raw)
In-Reply-To: <CAMuHMdU5vcfBc=DSgv=2w-xiFVwoP7_4jG+F04v-J_jE3O31WQ@mail.gmail.com>

Hi Geert,

On 19/02/12 20:10, Geert Uytterhoeven wrote:
> On Tue, Feb 7, 2012 at 04:09,<gerg@snapgear.com>  wrote:
>> +int update_persistent_clock(struct timespec now)
>> +{
>> +	return set_rtc_mmss(now.tv_sec);
>> +}
>
> This adds update_persistent_clock() for MMU, which was not present before.
> It's only called if CONFIG_GENERIC_CMOS_UPDATE is set, but
> arch/m68k/Kconfig has:
>
> config GENERIC_CMOS_UPDATE
>          def_bool !MMU

Yep. Again I was trying to just have fewer #ifdefs.

But looking at this further, I don't think there is any point having
CONFIG_GENERIC_CMOS_UPDATE defined for the non-MMU case. The code for
update_persistent_clock() calls set_rtc_mmss() which relies on the
sub-arch code having set mach_set_clock_mmss to do the real work. But
that is not set for any non-MMU code paths. Seems like we can remove it
for everyone m68k type. Or did I miss something :-)

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

      reply	other threads:[~2012-02-21  6:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07  3:09 [PATCH 1/3] m68knommu: make persistent clock code consistent with m68k gerg
2012-02-07  3:09 ` [PATCH 2/3] m68knommu: modify timer init code to make it consistent with m68k code gerg
2012-02-07  3:09 ` [PATCH 3/3] m68k: merge mmu and non-mmu versions of time.c gerg
2012-02-19 10:10   ` Geert Uytterhoeven
2012-02-21  6:37     ` Greg Ungerer [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=4F433B95.6020604@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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.