Home
last modified time | relevance | path

Searched hist:"22 d40209" (Results 1 – 4 of 4) sorted by relevance

/openbmc/linux/drivers/i2c/busses/
H A Di2c-thunderx-pcidrv.c22d40209 Wed Aug 24 16:25:44 CDT 2016 Jan Glauber <jglauber@cavium.com> i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI, interrupts are MSI-X. The
clock rates can be set via device tree or ACPI.

Signed-off-by: Jan Glauber <jglauber@cavium.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
22d40209 Wed Aug 24 16:25:44 CDT 2016 Jan Glauber <jglauber@cavium.com> i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI, interrupts are MSI-X. The
clock rates can be set via device tree or ACPI.

Signed-off-by: Jan Glauber <jglauber@cavium.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
H A Di2c-octeon-core.h22d40209 Wed Aug 24 16:25:44 CDT 2016 Jan Glauber <jglauber@cavium.com> i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI, interrupts are MSI-X. The
clock rates can be set via device tree or ACPI.

Signed-off-by: Jan Glauber <jglauber@cavium.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
22d40209 Wed Aug 24 16:25:44 CDT 2016 Jan Glauber <jglauber@cavium.com> i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI, interrupts are MSI-X. The
clock rates can be set via device tree or ACPI.

Signed-off-by: Jan Glauber <jglauber@cavium.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
H A DMakefile22d40209 Wed Aug 24 16:25:44 CDT 2016 Jan Glauber <jglauber@cavium.com> i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI, interrupts are MSI-X. The
clock rates can be set via device tree or ACPI.

Signed-off-by: Jan Glauber <jglauber@cavium.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
22d40209 Wed Aug 24 16:25:44 CDT 2016 Jan Glauber <jglauber@cavium.com> i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI, interrupts are MSI-X. The
clock rates can be set via device tree or ACPI.

Signed-off-by: Jan Glauber <jglauber@cavium.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
H A DKconfig22d40209 Wed Aug 24 16:25:44 CDT 2016 Jan Glauber <jglauber@cavium.com> i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI, interrupts are MSI-X. The
clock rates can be set via device tree or ACPI.

Signed-off-by: Jan Glauber <jglauber@cavium.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
22d40209 Wed Aug 24 16:25:44 CDT 2016 Jan Glauber <jglauber@cavium.com> i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI, interrupts are MSI-X. The
clock rates can be set via device tree or ACPI.

Signed-off-by: Jan Glauber <jglauber@cavium.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>