Home
last modified time | relevance | path

Searched full:parity (Results 1 – 25 of 1730) sorted by relevance

12345678910>>...70

/kernel/linux/linux-6.6/drivers/edac/
Dmce_amd.c62 "Parity error during data load from IC",
63 "Parity error for IC valid bit",
64 "Main tag parity error",
65 "Parity error in prediction queue",
66 "PFB data/address parity error",
67 "Parity error in the branch status reg",
70 "Parity error for IC probe tag valid bit",
71 "PFB non-cacheable bit parity error",
72 "PFB valid bit parity error", /* xec = 0xd */
83 "Fill parity error on insn fills",
[all …]
/kernel/linux/linux-5.10/drivers/edac/
Dmce_amd.c62 "Parity error during data load from IC",
63 "Parity error for IC valid bit",
64 "Main tag parity error",
65 "Parity error in prediction queue",
66 "PFB data/address parity error",
67 "Parity error in the branch status reg",
70 "Parity error for IC probe tag valid bit",
71 "PFB non-cacheable bit parity error",
72 "PFB valid bit parity error", /* xec = 0xd */
83 "Fill parity error on insn fills",
[all …]
Dedac_pci_sysfs.c20 static int check_pci_errors; /* default NO check PCI parity */
21 static int edac_pci_panic_on_pe; /* default NO panic on PCI Parity */
22 static int edac_pci_log_pe = 1; /* log PCI parity errors */
23 static int edac_pci_log_npe = 1; /* log PCI non-parity error errors */
237 /* Set of show/store abstract level functions for PCI Parity object */
282 /* PCI Parity control files */
508 /* Clear any PCI parity errors logged by this device. */
523 * PCI Parity polling
525 * Function to retrieve the current parity status
561 "Master Data Parity Error on %s\n", in edac_pci_dev_parity_test()
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/mtd/
Dnand_ecc.rst32 bytes. This is done by calculating several parity bits over the rows and
33 columns. The parity used is even parity which means that the parity bit = 1
34 if the data over which the parity is calculated is 1 and the parity bit = 0
35 if the data over which the parity is calculated is 0. So the total
36 number of bits over the data over which the parity is calculated + the
37 parity bit is even. (see wikipedia if you can't follow this).
38 Parity is often calculated by means of an exclusive or operation,
59 cp is my abbreviation for column parity, rp for row parity.
61 Let's start to explain column parity.
63 - cp0 is the parity that belongs to all bit0, bit2, bit4, bit6.
[all …]
/kernel/linux/linux-6.6/Documentation/driver-api/mtd/
Dnand_ecc.rst32 bytes. This is done by calculating several parity bits over the rows and
33 columns. The parity used is even parity which means that the parity bit = 1
34 if the data over which the parity is calculated is 1 and the parity bit = 0
35 if the data over which the parity is calculated is 0. So the total
36 number of bits over the data over which the parity is calculated + the
37 parity bit is even. (see wikipedia if you can't follow this).
38 Parity is often calculated by means of an exclusive or operation,
59 cp is my abbreviation for column parity, rp for row parity.
61 Let's start to explain column parity.
63 - cp0 is the parity that belongs to all bit0, bit2, bit4, bit6.
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/md/
Draid5-ppl.rst2 Partial Parity Log
5 Partial Parity Log (PPL) is a feature available for RAID5 arrays. The issue
6 addressed by PPL is that after a dirty shutdown, parity of a particular stripe
8 in degraded state, there is no way to recalculate parity, because one of the
10 array or using it is as degraded - data calculated from parity for array blocks
15 Partial parity for a write operation is the XOR of stripe data chunks not
17 write hole. XORing partial parity with the modified chunks produces parity for
20 this stripe is missing, this updated parity can be used to recover its
26 When handling a write request PPL writes partial parity before new data and
27 parity are dispatched to disks. PPL is a distributed log - it is stored on
[all …]
Draid5-cache.rst27 and parity don't match. The reason is that a stripe write involves several RAID
53 write. For non-full-stripe writes, MD must read old data before the new parity
83 ID for recovery identification. Data can be IO data and parity data. Data is
91 write-through mode, MD calculates parity for IO data, writes both IO data and
92 parity to the log, writes the data and parity to RAID disks after the data and
93 parity is settled down in log and finally the IO is finished. Read just reads
99 MD will calculate parity for the data and write parity into the log. After this
100 is finished, MD will write both data and parity into RAID disks, then MD can
107 data and data. If MD finds a stripe with data and valid parities (1 parity for
/kernel/linux/linux-6.6/Documentation/driver-api/md/
Draid5-ppl.rst2 Partial Parity Log
5 Partial Parity Log (PPL) is a feature available for RAID5 arrays. The issue
6 addressed by PPL is that after a dirty shutdown, parity of a particular stripe
8 in degraded state, there is no way to recalculate parity, because one of the
10 array or using it is as degraded - data calculated from parity for array blocks
15 Partial parity for a write operation is the XOR of stripe data chunks not
17 write hole. XORing partial parity with the modified chunks produces parity for
20 this stripe is missing, this updated parity can be used to recover its
26 When handling a write request PPL writes partial parity before new data and
27 parity are dispatched to disks. PPL is a distributed log - it is stored on
[all …]
Draid5-cache.rst27 and parity don't match. The reason is that a stripe write involves several RAID
53 write. For non-full-stripe writes, MD must read old data before the new parity
83 ID for recovery identification. Data can be IO data and parity data. Data is
91 write-through mode, MD calculates parity for IO data, writes both IO data and
92 parity to the log, writes the data and parity to RAID disks after the data and
93 parity is settled down in log and finally the IO is finished. Read just reads
99 MD will calculate parity for the data and write parity into the log. After this
100 is finished, MD will write both data and parity into RAID disks, then MD can
107 data and data. If MD finds a stripe with data and valid parities (1 parity for
/kernel/linux/linux-5.10/drivers/scsi/csiostor/
Dcsio_hw_t5.c75 { MSTGRPPERR_F, "Master Response Read Queue parity error", in csio_t5_pcie_intr_handler()
77 { MSTTIMEOUTPERR_F, "Master Timeout FIFO parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
78 { MSIXSTIPERR_F, "MSI-X STI SRAM parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
79 { MSIXADDRLPERR_F, "MSI-X AddrL parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
80 { MSIXADDRHPERR_F, "MSI-X AddrH parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
81 { MSIXDATAPERR_F, "MSI-X data parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
82 { MSIXDIPERR_F, "MSI-X DI parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
83 { PIOCPLGRPPERR_F, "PCI PIO completion Group FIFO parity error", in csio_t5_pcie_intr_handler()
85 { PIOREQGRPPERR_F, "PCI PIO request Group FIFO parity error", in csio_t5_pcie_intr_handler()
87 { TARTAGPERR_F, "PCI PCI target tag FIFO parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
[all …]
/kernel/linux/linux-6.6/drivers/scsi/csiostor/
Dcsio_hw_t5.c75 { MSTGRPPERR_F, "Master Response Read Queue parity error", in csio_t5_pcie_intr_handler()
77 { MSTTIMEOUTPERR_F, "Master Timeout FIFO parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
78 { MSIXSTIPERR_F, "MSI-X STI SRAM parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
79 { MSIXADDRLPERR_F, "MSI-X AddrL parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
80 { MSIXADDRHPERR_F, "MSI-X AddrH parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
81 { MSIXDATAPERR_F, "MSI-X data parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
82 { MSIXDIPERR_F, "MSI-X DI parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
83 { PIOCPLGRPPERR_F, "PCI PIO completion Group FIFO parity error", in csio_t5_pcie_intr_handler()
85 { PIOREQGRPPERR_F, "PCI PIO request Group FIFO parity error", in csio_t5_pcie_intr_handler()
87 { TARTAGPERR_F, "PCI PCI target tag FIFO parity error", -1, 1 }, in csio_t5_pcie_intr_handler()
[all …]
/kernel/linux/linux-6.6/arch/powerpc/platforms/44x/
Dmachine_check.c30 printk("TLB Parity Error\n"); in machine_check_440A()
33 printk("I-Cache Parity Error\n"); in machine_check_440A()
36 printk("D-Cache Search Parity Error\n"); in machine_check_440A()
38 printk("D-Cache Flush Parity Error\n"); in machine_check_440A()
68 printk(KERN_ERR "TLB Parity Error\n"); in machine_check_47x()
71 printk(KERN_ERR "I-Cache Parity Error\n"); in machine_check_47x()
74 printk(KERN_ERR "D-Cache Search Parity Error\n"); in machine_check_47x()
76 printk(KERN_ERR "GPR Parity Error\n"); in machine_check_47x()
78 printk(KERN_ERR "FPR Parity Error\n"); in machine_check_47x()
/kernel/linux/linux-5.10/arch/powerpc/platforms/44x/
Dmachine_check.c30 printk("TLB Parity Error\n"); in machine_check_440A()
33 printk("I-Cache Parity Error\n"); in machine_check_440A()
36 printk("D-Cache Search Parity Error\n"); in machine_check_440A()
38 printk("D-Cache Flush Parity Error\n"); in machine_check_440A()
68 printk(KERN_ERR "TLB Parity Error\n"); in machine_check_47x()
71 printk(KERN_ERR "I-Cache Parity Error\n"); in machine_check_47x()
74 printk(KERN_ERR "D-Cache Search Parity Error\n"); in machine_check_47x()
76 printk(KERN_ERR "GPR Parity Error\n"); in machine_check_47x()
78 printk(KERN_ERR "FPR Parity Error\n"); in machine_check_47x()
/kernel/linux/linux-6.6/drivers/scsi/aic7xxx/aicasm/
Daicasm_insformat.h55 parity : 1; member
57 uint32_t parity : 1,
74 parity : 1; member
76 uint32_t parity : 1,
92 parity : 1; member
94 uint32_t parity : 1,
110 parity : 1; member
112 uint32_t parity : 1,
128 parity : 1; member
130 uint32_t parity : 1,
[all …]
/kernel/linux/linux-5.10/drivers/scsi/aic7xxx/aicasm/
Daicasm_insformat.h55 parity : 1; member
57 uint32_t parity : 1,
74 parity : 1; member
76 uint32_t parity : 1,
92 parity : 1; member
94 uint32_t parity : 1,
110 parity : 1; member
112 uint32_t parity : 1,
128 parity : 1; member
130 uint32_t parity : 1,
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/serial/
Dxlnx,opb-uartlite.yaml45 xlnx,use-parity:
49 Whether parity checking was enabled when the device was configured.
51 xlnx,odd-parity:
55 Whether odd parity was configured.
63 - xlnx,use-parity
69 xlnx,use-parity:
73 - xlnx,odd-parity
86 xlnx,use-parity = <0>;
/kernel/linux/linux-5.10/arch/mips/mm/
Dcerr-sb1.c80 printk(" tag-parity"); in breakout_cerri()
82 printk(" data-parity"); in breakout_cerri()
255 /* Parity lookup table. */
256 static const uint8_t parity[256] = { variable
275 /* Masks to select bits for Hamming parity, mask_72_64[i] for bit[i] */
287 /* Calculate the parity on a range of bits */
290 char parity = 0; in range_parity() local
295 parity = !parity; in range_parity()
298 return parity; in range_parity()
301 /* Calculate the 4-bit even byte-parity for an instruction */
[all …]
/kernel/linux/linux-6.6/arch/mips/mm/
Dcerr-sb1.c80 printk(" tag-parity"); in breakout_cerri()
82 printk(" data-parity"); in breakout_cerri()
255 /* Parity lookup table. */
256 static const uint8_t parity[256] = { variable
275 /* Masks to select bits for Hamming parity, mask_72_64[i] for bit[i] */
287 /* Calculate the parity on a range of bits */
290 char parity = 0; in range_parity() local
295 parity = !parity; in range_parity()
298 return parity; in range_parity()
301 /* Calculate the 4-bit even byte-parity for an instruction */
[all …]
/kernel/linux/linux-6.6/arch/mips/include/asm/sgi/
Dmc.h21 #define SGIMC_CCTRL0_EPERRGIO 0x00000020 /* GIO parity error enable */
22 #define SGIMC_CCTRL0_EPERRMEM 0x00000040 /* Main mem parity error enable */
23 #define SGIMC_CCTRL0_EPERRCPU 0x00000080 /* CPU bus parity error enable */
28 #define SGIMC_CCTRL0_EPERRSCMD 0x00001000 /* SysCMD bus parity error enable */
36 #define SGIMC_CCTRL0_R4KNOCHKPARR 0x04000000 /* Don't chk parity on mem data reads */
122 #define SGIMC_CSTAT_RD 0x00000100 /* read parity error */
123 #define SGIMC_CSTAT_PAR 0x00000200 /* CPU parity error */
125 #define SGIMC_CSTAT_SYSAD_PAR 0x00000800 /* sysad parity error */
126 #define SGIMC_CSTAT_SYSCMD_PAR 0x00001000 /* syscmd parity error */
128 #define SGIMC_CSTAT_PAR_MASK 0x00001f00 /* parity error mask */
[all …]
/kernel/linux/linux-5.10/arch/mips/include/asm/sgi/
Dmc.h21 #define SGIMC_CCTRL0_EPERRGIO 0x00000020 /* GIO parity error enable */
22 #define SGIMC_CCTRL0_EPERRMEM 0x00000040 /* Main mem parity error enable */
23 #define SGIMC_CCTRL0_EPERRCPU 0x00000080 /* CPU bus parity error enable */
28 #define SGIMC_CCTRL0_EPERRSCMD 0x00001000 /* SysCMD bus parity error enable */
36 #define SGIMC_CCTRL0_R4KNOCHKPARR 0x04000000 /* Don't chk parity on mem data reads */
122 #define SGIMC_CSTAT_RD 0x00000100 /* read parity error */
123 #define SGIMC_CSTAT_PAR 0x00000200 /* CPU parity error */
125 #define SGIMC_CSTAT_SYSAD_PAR 0x00000800 /* sysad parity error */
126 #define SGIMC_CSTAT_SYSCMD_PAR 0x00001000 /* syscmd parity error */
128 #define SGIMC_CSTAT_PAR_MASK 0x00001f00 /* parity error mask */
[all …]
/kernel/linux/linux-6.6/drivers/usb/serial/
Dkeyspan_usa28msg.h48 If the port is configured for parity, the data will be an
49 alternating string of parity and data bytes, so the message
57 If there is no parity, the format is simply:
63 USB IN (USA28 -> host, receive) messages contain data and parity
64 if parity is configred, thusly:
70 If parity is not configured, the format is:
76 In the TX messages (USB OUT), the 0x01 bit of the PARity byte is
77 the parity bit. In the RX messages (USB IN), the PARity byte is
78 the content of the 8051's status register; the parity bit
112 u8 parity, // 1=use parity, 0=don't member
[all …]
/kernel/linux/linux-5.10/drivers/usb/serial/
Dkeyspan_usa28msg.h48 If the port is configured for parity, the data will be an
49 alternating string of parity and data bytes, so the message
57 If there is no parity, the format is simply:
63 USB IN (USA28 -> host, receive) messages contain data and parity
64 if parity is configred, thusly:
70 If parity is not configured, the format is:
76 In the TX messages (USB OUT), the 0x01 bit of the PARity byte is
77 the parity bit. In the RX messages (USB IN), the PARity byte is
78 the content of the 8051's status register; the parity bit
112 u8 parity, // 1=use parity, 0=don't member
[all …]
/kernel/linux/linux-5.10/drivers/media/pci/mantis/
Dmantis_uart.c31 enum mantis_parity parity; member
46 } parity[3] = { variable
71 dprintk(MANTIS_ERROR, 1, "UART parity error"); in mantis_uart_read()
114 mmwrite((mmread(MANTIS_UART_CTL) | (params->parity & 0x3)), MANTIS_UART_CTL); in mantis_uart_setup()
148 /* default parity: */ in mantis_uart_init()
150 params.parity = config->parity; in mantis_uart_init()
151 dprintk(MANTIS_INFO, 1, "Initializing UART @ %sbps parity:%s", in mantis_uart_init()
153 parity[params.parity].string); in mantis_uart_init()
/kernel/linux/linux-6.6/drivers/media/pci/mantis/
Dmantis_uart.c31 enum mantis_parity parity; member
46 } parity[3] = { variable
71 dprintk(MANTIS_ERROR, 1, "UART parity error"); in mantis_uart_read()
114 mmwrite((mmread(MANTIS_UART_CTL) | (params->parity & 0x3)), MANTIS_UART_CTL); in mantis_uart_setup()
148 /* default parity: */ in mantis_uart_init()
150 params.parity = config->parity; in mantis_uart_init()
151 dprintk(MANTIS_INFO, 1, "Initializing UART @ %sbps parity:%s", in mantis_uart_init()
153 parity[params.parity].string); in mantis_uart_init()
/kernel/linux/linux-5.10/Documentation/core-api/
Dlibrs.rst57 and stores the result in the parity buffer. Note that the parity buffer
74 /* Parity buffer. Size = number of roots */
76 /* Initialize the parity buffer */
78 /* Encode 512 byte in data8. Store parity in buffer par */
86 received parity symbols and corrects errors in the data.
107 /* Parity buffer. Size = number of roots */
113 /* Receive parity */
124 /* Parity buffer. Size = number of roots */
130 /* Receive parity */
141 Note: It's not necessary to give data and received parity to the
[all …]

12345678910>>...70