Searched hist:"0 d1dcb0b" (Results 1 – 2 of 2) sorted by relevance
/qemu/include/hw/ppc/ |
H A D | pnv_chip.h | 0d1dcb0b Wed Oct 25 15:27:14 GMT 2023 Glenn Miles <milesg@linux.vnet.ibm.com> ppc/pnv: Fix number of I2C engines and ports for power9/10
Power9 is supposed to have 4 PIB-connected I2C engines with the following number of ports on each engine:
0: 2 1: 13 2: 2 3: 2
Power10 also has 4 engines but has the following number of ports on each engine:
0: 14 1: 14 2: 2 3: 16
Current code assumes that they all have the same (maximum) number. This can be a problem if software expects to see a certain number of ports present (Power Hypervisor seems to care).
Fixed this by adding separate tables for power9 and power10 that map the I2C controller number to the number of I2C buses that should be attached for that engine.
Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com> Message-ID: <20231025152714.956664-1-milesg@linux.vnet.ibm.com> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com> 0d1dcb0b Wed Oct 25 15:27:14 GMT 2023 Glenn Miles <milesg@linux.vnet.ibm.com> ppc/pnv: Fix number of I2C engines and ports for power9/10
Power9 is supposed to have 4 PIB-connected I2C engines with the following number of ports on each engine:
0: 2 1: 13 2: 2 3: 2
Power10 also has 4 engines but has the following number of ports on each engine:
0: 14 1: 14 2: 2 3: 16
Current code assumes that they all have the same (maximum) number. This can be a problem if software expects to see a certain number of ports present (Power Hypervisor seems to care).
Fixed this by adding separate tables for power9 and power10 that map the I2C controller number to the number of I2C buses that should be attached for that engine.
Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com> Message-ID: <20231025152714.956664-1-milesg@linux.vnet.ibm.com> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com> 0d1dcb0b Wed Oct 25 15:27:14 GMT 2023 Glenn Miles <milesg@linux.vnet.ibm.com> ppc/pnv: Fix number of I2C engines and ports for power9/10
Power9 is supposed to have 4 PIB-connected I2C engines with the following number of ports on each engine:
0: 2 1: 13 2: 2 3: 2
Power10 also has 4 engines but has the following number of ports on each engine:
0: 14 1: 14 2: 2 3: 16
Current code assumes that they all have the same (maximum) number. This can be a problem if software expects to see a certain number of ports present (Power Hypervisor seems to care).
Fixed this by adding separate tables for power9 and power10 that map the I2C controller number to the number of I2C buses that should be attached for that engine.
Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com> Message-ID: <20231025152714.956664-1-milesg@linux.vnet.ibm.com> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
|
/qemu/hw/ppc/ |
H A D | pnv.c | 0d1dcb0b Wed Oct 25 15:27:14 GMT 2023 Glenn Miles <milesg@linux.vnet.ibm.com> ppc/pnv: Fix number of I2C engines and ports for power9/10
Power9 is supposed to have 4 PIB-connected I2C engines with the following number of ports on each engine:
0: 2 1: 13 2: 2 3: 2
Power10 also has 4 engines but has the following number of ports on each engine:
0: 14 1: 14 2: 2 3: 16
Current code assumes that they all have the same (maximum) number. This can be a problem if software expects to see a certain number of ports present (Power Hypervisor seems to care).
Fixed this by adding separate tables for power9 and power10 that map the I2C controller number to the number of I2C buses that should be attached for that engine.
Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com> Message-ID: <20231025152714.956664-1-milesg@linux.vnet.ibm.com> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com> 0d1dcb0b Wed Oct 25 15:27:14 GMT 2023 Glenn Miles <milesg@linux.vnet.ibm.com> ppc/pnv: Fix number of I2C engines and ports for power9/10
Power9 is supposed to have 4 PIB-connected I2C engines with the following number of ports on each engine:
0: 2 1: 13 2: 2 3: 2
Power10 also has 4 engines but has the following number of ports on each engine:
0: 14 1: 14 2: 2 3: 16
Current code assumes that they all have the same (maximum) number. This can be a problem if software expects to see a certain number of ports present (Power Hypervisor seems to care).
Fixed this by adding separate tables for power9 and power10 that map the I2C controller number to the number of I2C buses that should be attached for that engine.
Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com> Message-ID: <20231025152714.956664-1-milesg@linux.vnet.ibm.com> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com> 0d1dcb0b Wed Oct 25 15:27:14 GMT 2023 Glenn Miles <milesg@linux.vnet.ibm.com> ppc/pnv: Fix number of I2C engines and ports for power9/10
Power9 is supposed to have 4 PIB-connected I2C engines with the following number of ports on each engine:
0: 2 1: 13 2: 2 3: 2
Power10 also has 4 engines but has the following number of ports on each engine:
0: 14 1: 14 2: 2 3: 16
Current code assumes that they all have the same (maximum) number. This can be a problem if software expects to see a certain number of ports present (Power Hypervisor seems to care).
Fixed this by adding separate tables for power9 and power10 that map the I2C controller number to the number of I2C buses that should be attached for that engine.
Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com> Message-ID: <20231025152714.956664-1-milesg@linux.vnet.ibm.com> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
|