mirror of
https://github.com/torvalds/linux.git
synced 2024-11-22 04:02:20 +00:00
docs: move powerpc under arch
and fix all in-tree references. Architecture-specific documentation is being moved into Documentation/arch/ as a way of cleaning up the top-level documentation directory and making the docs hierarchy more closely match the source hierarchy. Signed-off-by: Costa Shulyupin <costa.shul@redhat.com> Acked-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20230826165737.2101199-1-costa.shul@redhat.com
This commit is contained in:
parent
2087f270be
commit
17e02586ed
@ -8,7 +8,7 @@ Description:
|
||||
more bits set in the dimm-health-bitmap retrieved in
|
||||
response to H_SCM_HEALTH hcall. The details of the bit
|
||||
flags returned in response to this hcall is available
|
||||
at 'Documentation/powerpc/papr_hcalls.rst' . Below are
|
||||
at 'Documentation/arch/powerpc/papr_hcalls.rst' . Below are
|
||||
the flags reported in this sysfs file:
|
||||
|
||||
* "not_armed"
|
||||
|
@ -364,7 +364,7 @@ Note, however, not all failures are truly "permanent". Some are
|
||||
caused by over-heating, some by a poorly seated card. Many
|
||||
PCI error events are caused by software bugs, e.g. DMAs to
|
||||
wild addresses or bogus split transactions due to programming
|
||||
errors. See the discussion in Documentation/powerpc/eeh-pci-error-recovery.rst
|
||||
errors. See the discussion in Documentation/arch/powerpc/eeh-pci-error-recovery.rst
|
||||
for additional detail on real-life experience of the causes of
|
||||
software errors.
|
||||
|
||||
@ -404,7 +404,7 @@ That is, the recovery API only requires that:
|
||||
.. note::
|
||||
|
||||
Implementation details for the powerpc platform are discussed in
|
||||
the file Documentation/powerpc/eeh-pci-error-recovery.rst
|
||||
the file Documentation/arch/powerpc/eeh-pci-error-recovery.rst
|
||||
|
||||
As of this writing, there is a growing list of device drivers with
|
||||
patches implementing error recovery. Not all of these patches are in
|
||||
|
@ -19,7 +19,7 @@ implementation.
|
||||
nios2/index
|
||||
openrisc/index
|
||||
parisc/index
|
||||
../powerpc/index
|
||||
powerpc/index
|
||||
../riscv/index
|
||||
s390/index
|
||||
sh/index
|
||||
|
@ -32,7 +32,7 @@ Introduction
|
||||
responsible for the initialization of the adapter, setting up the
|
||||
special path for user space access, and performing error recovery. It
|
||||
communicates directly the Flash Accelerator Functional Unit (AFU)
|
||||
as described in Documentation/powerpc/cxl.rst.
|
||||
as described in Documentation/arch/powerpc/cxl.rst.
|
||||
|
||||
The cxlflash driver supports two, mutually exclusive, modes of
|
||||
operation at the device (LUN) level:
|
@ -202,7 +202,7 @@ PPC_FEATURE2_VEC_CRYPTO
|
||||
|
||||
PPC_FEATURE2_HTM_NOSC
|
||||
System calls fail if called in a transactional state, see
|
||||
Documentation/powerpc/syscall64-abi.rst
|
||||
Documentation/arch/powerpc/syscall64-abi.rst
|
||||
|
||||
PPC_FEATURE2_ARCH_3_00
|
||||
The processor supports the v3.0B / v3.0C userlevel architecture. Processors
|
||||
@ -217,11 +217,11 @@ PPC_FEATURE2_DARN
|
||||
|
||||
PPC_FEATURE2_SCV
|
||||
The scv 0 instruction may be used for system calls, see
|
||||
Documentation/powerpc/syscall64-abi.rst.
|
||||
Documentation/arch/powerpc/syscall64-abi.rst.
|
||||
|
||||
PPC_FEATURE2_HTM_NO_SUSPEND
|
||||
A limited Transactional Memory facility that does not support suspend is
|
||||
available, see Documentation/powerpc/transactional_memory.rst.
|
||||
available, see Documentation/arch/powerpc/transactional_memory.rst.
|
||||
|
||||
PPC_FEATURE2_ARCH_3_1
|
||||
The processor supports the v3.1 userlevel architecture. Processors
|
@ -5605,7 +5605,7 @@ M: Andrew Donnellan <ajd@linux.ibm.com>
|
||||
L: linuxppc-dev@lists.ozlabs.org
|
||||
S: Supported
|
||||
F: Documentation/ABI/testing/sysfs-class-cxl
|
||||
F: Documentation/powerpc/cxl.rst
|
||||
F: Documentation/arch/powerpc/cxl.rst
|
||||
F: arch/powerpc/platforms/powernv/pci-cxl.c
|
||||
F: drivers/misc/cxl/
|
||||
F: include/misc/cxl*
|
||||
@ -5617,7 +5617,7 @@ M: Matthew R. Ochs <mrochs@linux.ibm.com>
|
||||
M: Uma Krishnan <ukrishn@linux.ibm.com>
|
||||
L: linux-scsi@vger.kernel.org
|
||||
S: Supported
|
||||
F: Documentation/powerpc/cxlflash.rst
|
||||
F: Documentation/arch/powerpc/cxlflash.rst
|
||||
F: drivers/scsi/cxlflash/
|
||||
F: include/uapi/scsi/cxlflash_ioctl.h
|
||||
|
||||
@ -12103,7 +12103,7 @@ F: Documentation/ABI/stable/sysfs-firmware-opal-*
|
||||
F: Documentation/devicetree/bindings/i2c/i2c-opal.txt
|
||||
F: Documentation/devicetree/bindings/powerpc/
|
||||
F: Documentation/devicetree/bindings/rtc/rtc-opal.txt
|
||||
F: Documentation/powerpc/
|
||||
F: Documentation/arch/powerpc/
|
||||
F: arch/powerpc/
|
||||
F: drivers/*/*/*pasemi*
|
||||
F: drivers/*/*pasemi*
|
||||
@ -16497,7 +16497,7 @@ R: Oliver O'Halloran <oohall@gmail.com>
|
||||
L: linuxppc-dev@lists.ozlabs.org
|
||||
S: Supported
|
||||
F: Documentation/PCI/pci-error-recovery.rst
|
||||
F: Documentation/powerpc/eeh-pci-error-recovery.rst
|
||||
F: Documentation/arch/powerpc/eeh-pci-error-recovery.rst
|
||||
F: arch/powerpc/include/*/eeh*.h
|
||||
F: arch/powerpc/kernel/eeh*.c
|
||||
F: arch/powerpc/platforms/*/eeh*.c
|
||||
|
@ -893,7 +893,7 @@ __start_interrupts:
|
||||
*
|
||||
* Call convention:
|
||||
*
|
||||
* syscall register convention is in Documentation/powerpc/syscall64-abi.rst
|
||||
* syscall register convention is in Documentation/arch/powerpc/syscall64-abi.rst
|
||||
*/
|
||||
EXC_VIRT_BEGIN(system_call_vectored, 0x3000, 0x1000)
|
||||
/* SCV 0 */
|
||||
@ -1952,8 +1952,8 @@ EXC_VIRT_NONE(0x4b00, 0x100)
|
||||
* Call convention:
|
||||
*
|
||||
* syscall and hypercalls register conventions are documented in
|
||||
* Documentation/powerpc/syscall64-abi.rst and
|
||||
* Documentation/powerpc/papr_hcalls.rst respectively.
|
||||
* Documentation/arch/powerpc/syscall64-abi.rst and
|
||||
* Documentation/arch/powerpc/papr_hcalls.rst respectively.
|
||||
*
|
||||
* The intersection of volatile registers that don't contain possible
|
||||
* inputs is: cr0, xer, ctr. We may use these as scratch regs upon entry
|
||||
|
@ -68,7 +68,7 @@ static void *__init alloc_shared_lppaca(unsigned long size, unsigned long limit,
|
||||
memblock_set_bottom_up(true);
|
||||
|
||||
/*
|
||||
* See Documentation/powerpc/ultravisor.rst for more details.
|
||||
* See Documentation/arch/powerpc/ultravisor.rst for more details.
|
||||
*
|
||||
* UV/HV data sharing is in PAGE_SIZE granularity. In order to
|
||||
* minimize the number of pages shared, align the allocation to
|
||||
|
@ -19,7 +19,7 @@
|
||||
|
||||
/*
|
||||
* This is a hcall, so register convention is as
|
||||
* Documentation/powerpc/papr_hcalls.rst.
|
||||
* Documentation/arch/powerpc/papr_hcalls.rst.
|
||||
*
|
||||
* This may also be a syscall from PR-KVM userspace that is to be
|
||||
* reflected to the PR guest kernel, so registers may be set up for
|
||||
|
@ -430,7 +430,7 @@ static void qe_upload_microcode(const void *base,
|
||||
/*
|
||||
* Upload a microcode to the I-RAM at a specific address.
|
||||
*
|
||||
* See Documentation/powerpc/qe_firmware.rst for information on QE microcode
|
||||
* See Documentation/arch/powerpc/qe_firmware.rst for information on QE microcode
|
||||
* uploading.
|
||||
*
|
||||
* Currently, only version 1 is supported, so the 'version' field must be
|
||||
|
@ -47,7 +47,7 @@
|
||||
* using the 2.6 Linux kernel kref construct.
|
||||
*
|
||||
* For direction on installation and usage of this driver please reference
|
||||
* Documentation/powerpc/hvcs.rst.
|
||||
* Documentation/arch/powerpc/hvcs.rst.
|
||||
*/
|
||||
|
||||
#include <linux/device.h>
|
||||
|
@ -258,7 +258,7 @@ static inline int qe_alive_during_sleep(void)
|
||||
|
||||
/* Structure that defines QE firmware binary files.
|
||||
*
|
||||
* See Documentation/powerpc/qe_firmware.rst for a description of these
|
||||
* See Documentation/arch/powerpc/qe_firmware.rst for a description of these
|
||||
* fields.
|
||||
*/
|
||||
struct qe_firmware {
|
||||
|
Loading…
Reference in New Issue
Block a user