From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Jeremy Kerr <jk@ozlabs.org>,
linux-mtd@lists.infradead.org, linuxppc-dev@lists.ozlabs.org
Cc: Cyril Bur <cyrilbur@gmail.com>, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH 1/2] powerpc/powernv: Add interfaces for flash device access
Date: Thu, 02 Apr 2015 13:16:14 +1100 [thread overview]
Message-ID: <m31tk32s29.fsf@oc8180480414.ibm.com> (raw)
In-Reply-To: <1427868330.742068.357457598273.1.gpush@pablo>
Jeremy Kerr <jk@ozlabs.org> writes:
> From: Cyril Bur <cyrilbur@gmail.com>
>
> This change adds the OPAL interface definitions to allow Linux to read,
> write and erase from system flash devices. We register platform devices
> for the flash devices exported by firmware.
>
> We clash with the existing opal_flash_init function, which is really for
> the FSP flash update functionality, so we rename that initcall to
> opal_flash_update_init().
>
> A future change will add an mtd driver that uses this interface.
>
> Changes from Joel Stanley and Jeremy Kerr.
>
> Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
> Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
Acking that firmware calls are merged into skiboot.
Acked-by: Stewart Smith <stewart@linux.vnet.ibm.com>
next prev parent reply other threads:[~2015-04-02 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 6:05 [PATCH 0/2] Add a MTD driver for OpenPower PNOR flash Jeremy Kerr
2015-04-01 6:05 ` [PATCH 1/2] powerpc/powernv: Add interfaces for flash device access Jeremy Kerr
2015-04-02 2:16 ` Stewart Smith [this message]
2015-04-01 6:05 ` [PATCH 2/2] drivers/mtd: add powernv flash MTD abstraction driver Jeremy Kerr
2015-04-03 8:50 ` [PATCH 0/2] Add a MTD driver for OpenPower PNOR flash Michael Ellerman
2015-04-07 2:55 ` Jeremy Kerr
2015-04-13 4:22 ` Cyril Bur
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=m31tk32s29.fsf@oc8180480414.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=cyrilbur@gmail.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.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.