Changes in Makefile

58445641 - i3c: ast2600: Add AST2600 platform-specific driver

Fri, 31 Mar 2023 09:15:01 +0000

i3c: ast2600: Add AST2600 platform-specific driverNow that we have platform-specific infrastructure for the dw i3c driver,add platform support for the ASPEED AST2600 SoC.The AST2600 has a small set of "i3c global" registers, providingplatform-level i3c configuration outside of the i3c core.For the ast2600, we need a couple of extra setup operations: - on probe: find the i3c global register set and parse the SDA pullup resistor values - on init: set the pullups accordingly, and set the i3c instance IDsSigned-off-by: Jeremy Kerr Reviewed-by: Joel Stanley Link: https://lore.kernel.org/r/20230331091501.3800299-4-jk@codeconstruct.com.auSigned-off-by: Alexandre Belloni List of files: /linux-6.15/drivers/i3c/master/Makefile

dd3c5284 - i3c: master: svc: Add Silvaco I3C master driver

Thu, 21 Jan 2021 10:18:07 +0000

i3c: master: svc: Add Silvaco I3C master driverAdd support for Silvaco I3C dual-role IP. The master role is supportedin SDR mode only. I2C transfers have not been tested but are sharedbecause they are very close to the I3C transfers in terms of registerconfiguration.The IBI processing follows this logic:- When a slave advertizes an interrupt (SDA pulled low) an interrupt gets generated by the master. This time is unbounded and may be deferred.- The IRQ handler itself does not process anything: it only queues a work that will be run in non-atomic context. This is needed because short wait periods must be experienced.- The IBI job is divided in two parts: the first one is "critical" in the sense that it may not support getting interrupted. If this happens, after this first section the driver checks the master error register and depending on its content either flushes everything and errors out, or ends the processing (this second section may be interrupted).- If the critical section got interrupted, the slave will automatically respin it's IBI request when it will be allowed to.Signed-off-by: Miquel Raynal Signed-off-by: Alexandre Belloni Link: https://lore.kernel.org/r/20210121101808.14654-6-miquel.raynal@bootlin.com List of files: /linux-6.15/drivers/i3c/master/Makefile

9ad9a52c - i3c/master: introduce the mipi-i3c-hci driver

Wed, 11 Nov 2020 22:05:10 +0000

i3c/master: introduce the mipi-i3c-hci driverThis adds basic support for hardware implementing the MIPI I3C HCIspecification. This driver is currently limited by the capabilitiesof the I3C subsystem, meaning things like scheduled commands,auto-commands and NCM mode are not yet supported.This supports version 1.0 of the MIPI I3C HCI spec, as well as theimminent release of version 1.1. Support for draft version 2.0 of thespec is also largely included with the caveat that future adjustmentsto this code are likely as the spec is still a work in progress.This is also lightly tested as actual hardware is still very scarce,even for HCI v1.0. Hence the EXPERIMENTAL tag. Further contributionsto this driver are expected once vendor implementations and new I3Cdevices become available.Signed-off-by: Nicolas Pitre Signed-off-by: Boris Brezillon Link: https://lore.kernel.org/linux-i3c/20201111220510.3622216-3-nico@fluxnic.net List of files: /linux-6.15/drivers/i3c/master/Makefile

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/i3c/master/Makefile

1dd728f5 - i3c: master: Add driver for Synopsys DesignWare IP

Tue, 13 Nov 2018 14:09:51 +0000

i3c: master: Add driver for Synopsys DesignWare IPAdd driver for Synopsys DesignWare I3C master IPSigned-off-by: Vitor Soares Signed-off-by: Boris Brezillon List of files: /linux-6.15/drivers/i3c/master/Makefile

603f2bee - i3c: master: Add driver for Cadence IP

Wed, 19 Jul 2017 09:53:04 +0000

i3c: master: Add driver for Cadence IPAdd a driver for Cadence I3C master IP.Signed-off-by: Boris Brezillon Reviewed-by: Arnd Bergmann Acked-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/i3c/master/Makefile

3a379bbc - i3c: Add core I3C infrastructure

Wed, 19 Jul 2017 09:52:29 +0000

i3c: Add core I3C infrastructureAdd core infrastructure to support I3C in Linux and document it.This infrastructure adds basic I3C support. Advanced features will beadded afterwards.There are a few design choices that are worth mentioning because theyimpact the way I3C device drivers can interact with their devices:- all functions used to send I3C/I2C frames must be called in non-atomic context. Mainly done this way to ease implementation, but this is not set in stone, and if anyone needs async support, new functions can be added later on.- the bus element is a separate object, but it's tightly coupled with the master object. We thus have a 1:1 relationship between i3c_bus and i3c_master_controller objects, and if 2 master controllers are connected to the same bus and both exposed to the same Linux instance they will appear as two distinct busses, and devices on this bus will be exposed twice.- I2C backward compatibility has been designed to be transparent to I2C drivers and the I2C subsystem. The I3C master just registers an I2C adapter which creates a new I2C bus. I'd say that, from a representation PoV it's not ideal because what should appear as a single I3C bus exposing I3C and I2C devices here appears as 2 different buses connected to each other through the parenting (the I3C master is the parent of the I2C and I3C busses). On the other hand, I don't see a better solution if we want something that is not invasive.Missing features:- I3C HDR modes are not supported- no support for multi-master and the associated concepts (mastership handover, support for secondary masters, ...)- I2C devices can only be described using DT because this is the only use case I have. However, the framework can easily be extended with ACPI and board info support- I3C slave framework. This has been completely omitted, but shouldn't have a huge impact on the I3C framework because I3C slaves don't see the whole bus, it's only about handling master requests and generating IBIs. Some of the struct, constant and enum definitions could be shared, but most of the I3C slave framework logic will be differentSigned-off-by: Boris Brezillon Reviewed-by: Arnd Bergmann Acked-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/i3c/master/Makefile