<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>3a379bbc - i3c: Add core I3C infrastructure</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/i3c/Makefile#3a379bbc</link>
        <description>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&apos;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&apos;d say that, from a  representation PoV it&apos;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&apos;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&apos;t  have a huge impact on the I3C framework because I3C slaves don&apos;t see  the whole bus, it&apos;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 &lt;boris.brezillon@bootlin.com&gt;Reviewed-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/i3c/Makefile</description>
        <pubDate>Wed, 19 Jul 2017 09:52:29 +0000</pubDate>
        <dc:creator>Boris Brezillon &lt;boris.brezillon@bootlin.com&gt;</dc:creator>
    </item>
</channel>
</rss>
