All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Colin Cross <ccross@android.com>
Cc: NeilBrown <neilb@suse.de>, Andrew Boie <andrew.p.boie@intel.com>,
	arve@android.com, rebecca@android.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcb: Android bootloader control block driver
Date: Sat, 7 Jul 2012 16:05:55 -0700	[thread overview]
Message-ID: <20120707230555.GA29514@kroah.com> (raw)
In-Reply-To: <CAMbhsRSQhBTxA9g1b4Pc6px4gYcOzn4miOrS6ecdJmOQ+RNSGA@mail.gmail.com>

On Sat, Jul 07, 2012 at 03:39:09PM -0700, Colin Cross wrote:
> On many (most?) ARM SoCs, the reboot flag is not stored on disk, or
> anywhere else userspace can access.  It is stored in a power
> management controller scratch register that survives resets, or a
> register in an external I2C PMIC, or in internal SoC RAM (I've seen
> all of these).  For your proposal, every SoC would need a custom API
> to save the reboot flag somewhere.  For these devices, it clearly
> makes more sense to use something like the REBOOT2 API, and if we have
> to use it on some devices, it makes no sense to me to not use it on
> other devices just because userspace could theoretically handle it.

That's fine, but that is not what this patch did at all.

Propose a patch that handles writing to those types of registers and we
will be glad to review it.

thanks,

greg k-h

  reply	other threads:[~2012-07-07 23:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 19:36 [PATCH] bcb: Android bootloader control block driver Andrew Boie
2012-06-29 21:25 ` NeilBrown
2012-06-29 21:56   ` Boie, Andrew P
2012-06-30  3:08     ` gregkh
2012-06-30  3:23 ` Greg KH
2012-06-30  3:43   ` Colin Cross
2012-06-30  4:19     ` Greg KH
2012-06-30  4:37       ` Colin Cross
2012-07-02  0:10         ` NeilBrown
2012-07-07 22:39           ` Colin Cross
2012-07-07 23:05             ` Greg KH [this message]
2012-07-08  0:25               ` Colin Cross
2012-07-08  0:35                 ` Boie, Andrew P

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=20120707230555.GA29514@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andrew.p.boie@intel.com \
    --cc=arve@android.com \
    --cc=ccross@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=rebecca@android.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 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.