All of lore.kernel.org
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: PXA27x: Zipit Z2: disable wake on GPIO0
Date: Sun, 26 Feb 2012 23:21:49 +0100	[thread overview]
Message-ID: <201202262321.50101.marek.vasut@gmail.com> (raw)
In-Reply-To: <CA+E=qVc+kQe1_ThkMiED8Eh8Fv=kAnGT0Djeb09g58rXmhH+AQ@mail.gmail.com>

> 2012/2/26 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> > On Sun, Feb 26, 2012 at 06:11:17PM +0300, Vasily Khoruzhick wrote:
> >> 2012/2/26 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> >> > On Sun, Feb 26, 2012 at 04:47:42PM +0300, Vasily Khoruzhick wrote:
> >> >> We don't want machine to wake up on AC state change
> >> > 
> >> > NAK.  Stop polluting the machine callback methods.  Use the right one.
> >> 
> >> Ok, what's right one?
> > 
> >        void                    (*fixup)(struct tag *, char **,
> >                                         struct meminfo *);
> >        void                    (*reserve)(void);/* reserve mem blocks  */
> >        void                    (*map_io)(void);/* IO mapping function  */
> >        void                    (*init_early)(void);
> >        void                    (*init_irq)(void);
> >        struct sys_timer        *timer;         /* system tick timer    */
> >        void                    (*init_machine)(void);
> > 
> > and chose a more appropriate one from that?  Maybe init_early() if it
> > has to be done early, or preferably the init_machine() if it can wait
> > until arch_initcall() time.
> > 
> > But stuffing it into fixup, reserve, map_io, init_irq or the timer
> > initialization is pure abuse of those callbacks.
> 
> Ok, thanks.
> 

Or this should be patched in the bootloader too. Also, please dont introduce ad-
hoc constants like "1 << 0", ever!

M

  reply	other threads:[~2012-02-26 22:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-26 13:47 [PATCH 1/3] ARM: PXA: Zipit Z2: Fix oops in z2_power_off Vasily Khoruzhick
2012-02-26 13:47 ` [PATCH 2/3] ARM: PXA27x: save/restore PWER on suspend/resume Vasily Khoruzhick
2012-02-26 14:27   ` Russell King - ARM Linux
2012-02-26 14:55     ` Vasily Khoruzhick
2012-02-26 15:26       ` Russell King - ARM Linux
2012-02-26 22:20     ` Marek Vasut
2012-02-26 23:36       ` Russell King - ARM Linux
2012-02-26 23:47         ` Marek Vasut
2012-02-27  0:18           ` Russell King - ARM Linux
2012-02-27  0:40             ` Marek Vasut
2012-02-26 13:47 ` [PATCH 3/3] ARM: PXA27x: Zipit Z2: disable wake on GPIO0 Vasily Khoruzhick
2012-02-26 14:26   ` Russell King - ARM Linux
2012-02-26 15:11     ` Vasily Khoruzhick
2012-02-26 15:29       ` Russell King - ARM Linux
2012-02-26 15:35         ` Vasily Khoruzhick
2012-02-26 22:21           ` Marek Vasut [this message]
2012-02-26 23:35             ` Russell King - ARM Linux
2012-02-26 23:47               ` Marek Vasut

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=201202262321.50101.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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.