<?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>ee82e15c - pcf8574: driver for 8-pin quasi-bidirectional GPIO over I2C</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#ee82e15c</link>
        <description>pcf8574: driver for 8-pin quasi-bidirectional GPIO over I2C(cherry picked from commit 6354154ef520d359492badf0de9c8ae5d7080ae7)

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Thu, 01 Oct 2020 09:48:56 +0000</pubDate>
        <dc:creator>Andriy Gapon &lt;avg@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>8f57430d - driver for MAX44009 I2C illuminance sensor</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#8f57430d</link>
        <description>driver for MAX44009 I2C illuminance sensor(cherry picked from commit ff6fe2983550aeab0852e982e7fe5ac4c672c205)

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Thu, 20 Aug 2020 08:11:31 +0000</pubDate>
        <dc:creator>Andriy Gapon &lt;avg@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>d6f71e09 - pcf8591: driver for adc/dac with i2c interface</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#d6f71e09</link>
        <description>pcf8591: driver for adc/dac with i2c interface(cherry picked from commit a60b30469741392e66ec6fd21a8d5c4810a2d407)

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Mon, 17 Aug 2020 10:05:11 +0000</pubDate>
        <dc:creator>Andriy Gapon &lt;avg@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>2c98edd6 - htu21: driver for HTU21D I2C temperature and humidity sensor</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#2c98edd6</link>
        <description>htu21: driver for HTU21D I2C temperature and humidity sensorMFC after:	2 weeksRelnotes:	perhaps

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Tue, 19 Jan 2021 12:57:24 +0000</pubDate>
        <dc:creator>Andriy Gapon &lt;avg@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>b1f1b07f - hid: Import iichid - I2C transport backend for HID subsystem</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#b1f1b07f</link>
        <description>hid: Import iichid - I2C transport backend for HID subsystemThis implements hid_if.m methods for HID-over-I2C protocol [1].Following kernel options are added:IICHID_SAMPLING - Enable support for a sampling mode as interrupt                  resource acquisition is not always possible in a case                  of GPIO interrupts.IICHID_DEBUG    - Enable debug output.The module is based on prior Marc Priggemeyer work (D16698).[1] http://download.microsoft.com/download/7/d/d/7dd44bb7-2a7a-4505-ac1c-7227d3d96d5b/hid-over-i2c-protocol-spec-v1-0.docxDifferential revision:	https://reviews.freebsd.org/D27892

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Tue, 06 Oct 2020 21:50:16 +0000</pubDate>
        <dc:creator>Vladimir Kondratyev &lt;wulf@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>d97d8385 - Introduce support for Epson RX-8803 RTC.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#d97d8385</link>
        <description>Introduce support for Epson RX-8803 RTC.This patch introduces support for Epson RX-8803 RTC controller accessibleover I2C bus. It has a resolution of 1 sec.Support for interrupt based alarm was not implemented.Submitted by: Kornel Duleba &lt;mindal@semihalf.com&gt;Reviewed by: manuObtained from: SemihalfSponsored by: Alstom GroupDifferential Revision: https://reviews.freebsd.org/D24364

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Mon, 25 May 2020 15:40:02 +0000</pubDate>
        <dc:creator>Marcin Wojtas &lt;mw@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>7187cccc - Add TCA6416 GPIO expander support.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#7187cccc</link>
        <description>Add TCA6416 GPIO expander support.Add basic TCA6416 GPIO expander support over I2C bus. The driver handlesenabling and disabling pins, setting pin mode to IN and OUT andtoggling the pins. External interrupts are not supported.Submitted by: Dawid Gorecki &lt;dgr@semihalf.com&gt;Reviewed by: manu, mmelObtained from: SemihalfSponsored by: Alstom GroupDifferential Revision: https://reviews.freebsd.org/D24363

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Mon, 25 May 2020 15:31:43 +0000</pubDate>
        <dc:creator>Marcin Wojtas &lt;mw@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>422d05da - Add support for i2c bus mux hardware.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#422d05da</link>
        <description>Add support for i2c bus mux hardware.An i2c bus can be divided into segments which can be selectively connectedand disconnected from the main bus. This is usually done to enable usingmultiple slave devices having the same address, by isolating the devicesonto separate bus segments, only one of which is connected to the main busat once.There are several types of i2c bus muxes, which break down into two generalcategories... - Muxes which are themselves i2c slaves. These devices respond to i2c   commands on their upstream bus, and based on those commands, connect   various downstream buses to the upstream. In newbus terms, they are both   a child of an iicbus and the parent of one or more iicbus instances. - Muxes which are not i2c devices themselves. Such devices are part of the   i2c bus electrically, but in newbus terms their parent is some other   bus. The association with the upstream bus must be established by   separate metadata (such as FDT data).In both cases, the mux driver has one or more iicbus child instancesrepresenting the downstream buses. The mux driver implements the iicbus_ifinterface, as if it were an iichb host bridge/i2c controller driver. Itservices the IO requests sent to it by forwarding them to the iicbusinstance representing the upstream bus, after electrically connecting theupstream bus to the downstream bus that hosts the i2c slave device whichmade the IO request.The net effect is automatic mux switching which is transparent to slaves onthe downstream buses. They just do i2c IO they way they normally do, and thebus is electrically connected for the duration of the IO and then idled whenit is complete.The existing iicbus_if callback() method is enhanced so that the parameterpassed to it can be a struct which contains a device_t for the requestingbus and slave devices. This change is done by adding a flag that indicatesthe extra values are present, and making the flags field the first field ofa new args struct. If the flag is set, the iichb or mux driver can recastthe pointer-to-flags into a pointer-to-struct and access the extrafields. Thus abi compatibility with older drivers is retained (but a muxcannot exist on the bus with the older iicbus driver in use.)A new set of core support routines exists in iicbus.c. This code will helpimplement mux drivers for any type of mux hardware by supplying all theboilerplate code that forwards IO requests upstream. It also has code forparsing metadata and instantiating the child iicbus instances based on it.Two new hardware mux drivers are added. The ltc430x driver supports theLTC4305/4306 mux chips which are controlled via i2c commands. Theiic_gpiomux driver supports any mux hardware which is controlled bymanipulating the state of one or more gpio pins.  Test PlanTested locally using a variety of mux&apos;d bus configurations involving bothltc4305 and a homebrew gpio-controlled mux. Tested configurations includedcascaded muxes (unlikely in the real world, but useful to prove that &apos;it alljust works&apos; in terms of the automatic switching and upstream forwarding ofIO requests).

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Thu, 02 Jan 2020 17:51:49 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>5177d294 - Add a driver for Texas Instruments ADS101x/ADS111x i2c ADC chips.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#5177d294</link>
        <description>Add a driver for Texas Instruments ADS101x/ADS111x i2c ADC chips.Instances of the device can be configured using hints or FDT data.Interfaces to reconfigure the chip and extract voltage measurements fromit are available via sysctl(8).

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Mon, 05 Aug 2019 15:56:44 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>b5988450 - Remove jedec_ts(4)</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#b5988450</link>
        <description>Remove jedec_ts(4)The jedec_ts(4) driver has been marked as deprecated in stable/11, and isnow being removed from -HEAD. Add a notice in UPDATING, and update the fewremaining references (regarding jedec_dimm(4)&apos;s compatibility and history)to reflect the fact that jedec_ts(4) is now deleted.Reviewed by:	avgRelnotes:	yesDifferential Revision:	https://reviews.freebsd.org/D16537

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Wed, 01 Aug 2018 08:24:34 +0000</pubDate>
        <dc:creator>Ravi Pokala &lt;rpokala@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>b138780b - Build the ds1672 driver as a module.  Add a detach() to unregister the rtc.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#b138780b</link>
        <description>Build the ds1672 driver as a module.  Add a detach() to unregister the rtc.

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Tue, 06 Mar 2018 02:30:34 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>5a45ce2f - Build iicbus/rtc8583 as a module.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#5a45ce2f</link>
        <description>Build iicbus/rtc8583 as a module.

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Sun, 04 Mar 2018 21:06:21 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>f0a2d31a - Instead of building ofw_iicbus as a separate module, just compile it in to</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#f0a2d31a</link>
        <description>Instead of building ofw_iicbus as a separate module, just compile it in tothe iicbus module for FDT-based systems.The primary motivation for this is that host controller drivers whichdeclare DRIVER_MODULE(ofw_iicbus, thisdriver, etc, etc) now only need asingle MODULE_DEPEND(thisdriver, ofw_iicbus) for runtime linking to resolveall the symbols.  With ofw_iicbus and iicbus in separate modules, driverswould need to declare a MODULE_DEPEND() on both, because symbol lookup isnon-recursive through the dependency chain.  Requiring a driver to haveMODULE_DEPENDS() on both amounts to requiring the drivers to understand thekobj inheritence details of how ofw_iicbus is implemented, which seems likesomething they shouldn&apos;t have to know (and could even change some day).Also, this is somewhat analogous to how the drivers get built when compiledinto the kernel.  You don&apos;t have to ask for ofw_iicbus separately, it justgets built in along with iicbus when option FDT is in effect.

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Sun, 25 Feb 2018 18:26:50 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>dcd935df - jedec_dimm(4): report asset info and temperatures for DDR3 and DDR4 DIMMs</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#dcd935df</link>
        <description>jedec_dimm(4): report asset info and temperatures for DDR3 and DDR4 DIMMsA super-set of the functionality of jedec_ts(4). jedec_dimm(4) reports assetinformation (Part Number, Serial Number) encoded in the &quot;Serial PresenceDetect&quot; (SPD) data on JEDEC DDR3 and DDR4 DIMMs. It also calculates andreports the memory capacity of the DIMM, in megabytes. If the DIMM includesa &quot;Thermal Sensor On DIMM&quot; (TSOD), the temperature is also reported.Reviewed by:	cemMFC after:	1 weekRelnotes:	yesSponsored by:	PanasasDifferential Revision:	https://reviews.freebsd.org/D14392Discussed with:	avg, cemTested by:	avg, cem (previous version, no semantic changes)

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Thu, 22 Feb 2018 23:18:46 +0000</pubDate>
        <dc:creator>Ravi Pokala &lt;rpokala@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>a7e31772 - Build ofw_iicbus as a module if OPT_FDT is defined.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#a7e31772</link>
        <description>Build ofw_iicbus as a module if OPT_FDT is defined.

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Mon, 19 Feb 2018 00:47:03 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>d18915fa - Give icee(4) a detach() method so it can be used as a module.  Add a</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#d18915fa</link>
        <description>Give icee(4) a detach() method so it can be used as a module.  Add amodule makefile for it.

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Sun, 17 Sep 2017 22:58:13 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>098f6cb6 - Minor fixes and enhancements for the s35390a i2c RTC driver...</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#098f6cb6</link>
        <description>Minor fixes and enhancements for the s35390a i2c RTC driver...- Add FDT probe code.- Do i2c transfers with exclusive bus ownership.- Use config_intrhook_oneshot() to defer chip setup because some i2c  busses can&apos;t do transfers without interrupts.- Add a detach() routine.- Add to module build.

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Mon, 14 Aug 2017 00:00:24 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>bb2e8108 - Add a new driver, ds13rtc, that handles all DS13xx series i2c RTC chips.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#bb2e8108</link>
        <description>Add a new driver, ds13rtc, that handles all DS13xx series i2c RTC chips.This driver supports only basic timekeeping functionality.  It completelyreplaces the ds133x driver.  It can also replace the ds1374 driver, but thatwill take a few other changes in MIPS code and config, and will be committedseparately.  It does NOT replace the existing ds1307 driver, which providesaccess to some of the extended features on the 1307 chip, such as controllingthe square wave output signal.  If both ds1307 and ds13rtc drivers arepresent, the ds1307 driver will outbid and win control of the device.This driver can be configured with FDT data, or by using hints on non-FDTsystems.  In addition to the standard hints for i2c devices, it requiresa &quot;chiptype&quot; string of the form &quot;dallas,ds13xx&quot; where &apos;xx&apos; is the chip id(i.e., the same format as FDT compat strings).

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Sun, 13 Aug 2017 21:02:40 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>94759a24 - Add a driver for the Intersil ISL12xx family of i2c RTC chips.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#94759a24</link>
        <description>Add a driver for the Intersil ISL12xx family of i2c RTC chips.Supports ISL1209, ISL1218, ISL1219, ISL1220, ISL1221 (just basic RTCfunctionality, not all the other fancy stuff the chips can do).

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Tue, 01 Aug 2017 04:16:52 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>55b0d8a0 - Build iicbus/{ds1307,ds3231,nxprtc} as modules.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sys/modules/i2c/Makefile#55b0d8a0</link>
        <description>Build iicbus/{ds1307,ds3231,nxprtc} as modules.

            List of files:
            /freebsd-13.1/sys/modules/i2c/Makefile</description>
        <pubDate>Mon, 31 Jul 2017 22:32:11 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
