From: liaoweixiong <liaoweixiong@allwinnertech.com>
To: Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
liaoweixiong <liaoweixiong@allwinnertech.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [RFC v9 2/5] dt-bindings: pstore-block: new support for blkoops
Date: Tue, 19 Feb 2019 19:52:47 +0800 [thread overview]
Message-ID: <1550577170-18761-3-git-send-email-liaoweixiong@allwinnertech.com> (raw)
In-Reply-To: <1550577170-18761-1-git-send-email-liaoweixiong@allwinnertech.com>
Create DT binding document for blkoops.
Signed-off-by: liaoweixiong <liaoweixiong@allwinnertech.com>
---
.../devicetree/bindings/pstore/blkoops.txt | 53 ++++++++++++++++++++++
MAINTAINERS | 1 +
2 files changed, 54 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pstore/blkoops.txt
diff --git a/Documentation/devicetree/bindings/pstore/blkoops.txt b/Documentation/devicetree/bindings/pstore/blkoops.txt
new file mode 100644
index 0000000..5462915
--- /dev/null
+++ b/Documentation/devicetree/bindings/pstore/blkoops.txt
@@ -0,0 +1,53 @@
+Blkoops oops logger
+===================
+
+Blkoops provides a block partition for oops, excluding panics now, so they can
+be recovered after a reboot.
+
+Any space of block device will be used for a circular buffer of oops records.
+These records have a configurable size, with a size of 0 indicating that they
+should be disabled.
+
+At least one of "block-device" and "total_size" must be set.
+
+At least one of "dmesg-size" or "pmsg-size" must be set non-zero.
+
+Required properties:
+
+- compatible: must be "blkoops".
+
+Optional properties:
+
+- block-device: The block device to use. Most of the time, it is a partition of
+ device. If block-device is NULL, no block device is effective
+ and the data will be lost after rebooting.
+ It accept the following variants:
+ 1) <hex_major><hex_minor> device number in hexadecimal
+ represents itself no leading 0x, for example b302.
+ 2) /dev/<disk_name> represents the device number of disk
+ 3) /dev/<disk_name><decimal> represents the device number of
+ partition - device number of disk plus the partition number
+ 4) /dev/<disk_name>p<decimal> - same as the above, that form is
+ used when disk name of partitioned disk ends on a digit.
+ 5) PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF representing
+ the unique id of a partition if the partition table provides
+ it. The UUID may be either an EFI/GPT UUID, or refer to an
+ MSDOS partition using the format SSSSSSSS-PP, where SSSSSSSS
+ is a zero-filled hex representation of the 32-bit
+ "NT disk signature", and PP is a zero-filled hex
+ representation of the 1-based partition number.
+ 6) PARTUUID=<UUID>/PARTNROFF=<int> to select a partition in
+ relation to a partition with a known unique id.
+ 7) <major>:<minor> major and minor number of the device
+ separated by a colon.
+
+- total-size: The total size in kbytes pstore/blk can use. It must be a multiple
+ of 4. It must be less than or equal to size of block-device. If
+ total-size is zero with block-devce valid, it will be set to equal
+ to size of block-device.
+
+- dmesg-size: maximum size in kbytes of each dump done on oops, which must be a
+ multiple of 4.
+
+- pmsg-size: maximum size in kbytes for userspace messages, which must be a
+ multiple of 4.
diff --git a/MAINTAINERS b/MAINTAINERS
index 51029a4..f49dd37 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12318,6 +12318,7 @@ F: drivers/firmware/efi/efi-pstore.c
F: drivers/acpi/apei/erst.c
F: Documentation/admin-guide/ramoops.rst
F: Documentation/devicetree/bindings/reserved-memory/ramoops.txt
+F: Documentation/devicetree/bindings/pstore-block/
K: \b(pstore|ramoops)
PTP HARDWARE CLOCK SUPPORT
--
1.9.1
next prev parent reply other threads:[~2019-02-19 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 11:52 [RFC v9 0/5] pstore/block: new support logger for block devices liaoweixiong
2019-02-19 11:52 ` [RFC v9 1/5] pstore/blk: " liaoweixiong
2019-02-19 11:52 ` liaoweixiong [this message]
2019-02-22 15:36 ` [RFC v9 2/5] dt-bindings: pstore-block: new support for blkoops Rob Herring
2019-02-25 14:20 ` liaoweixiong
2019-02-19 11:52 ` [RFC v9 3/5] pstore/blk: add blkoops for pstore_blk liaoweixiong
2019-02-19 11:52 ` [RFC v9 4/5] pstore/blk: support pmsg for pstore block liaoweixiong
2019-02-19 11:52 ` [RFC v9 5/5] Documentation: pstore/blk: create document for pstore_blk liaoweixiong
2019-02-28 5:15 ` Randy Dunlap
2019-02-28 6:40 ` liaoweixiong
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=1550577170-18761-3-git-send-email-liaoweixiong@allwinnertech.com \
--to=liaoweixiong@allwinnertech.com \
--cc=anton@enomsg.org \
--cc=arnd@arndb.de \
--cc=ccross@android.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).