<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/modules/i2c, branch releng/12.1</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.1</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.1'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2019-09-16T12:54:44Z</updated>
<entry>
<title>MFC r350303: enable ig4_acpi on aarch64</title>
<updated>2019-09-16T12:54:44Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2019-09-16T12:54:44Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1aba590a10cdb79d97737b2c91c9aeeb7f8f7c4a'/>
<id>urn:sha1:1aba590a10cdb79d97737b2c91c9aeeb7f8f7c4a</id>
<content type='text'>
The already-listed APMC0D0F ID belongs to the Ampere eMAG aarch64
platform, but ACPI support was not even built on aarch64.

Submitted by:	Greg V &lt;greg_unrelenting.technology&gt;
</content>
</entry>
<entry>
<title>MFC r350591, r350971, r351724</title>
<updated>2019-09-05T16:37:10Z</updated>
<author>
<name>Ian Lepore</name>
<email>ian@FreeBSD.org</email>
</author>
<published>2019-09-05T16:37:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e27633af9e257806e940c44fb4af7f72b9626d49'/>
<id>urn:sha1:e27633af9e257806e940c44fb4af7f72b9626d49</id>
<content type='text'>
r350591:
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 from
it are available via sysctl(8).

r350971:
Fix the driver name in ads111x.4, and hook the manpage up to the build.

The driver was originally written with the name ads1115, but at the last
minute it got renamed to ads111x to reflect its support for many related
chips, but I forgot to update the manpage to match the renaming before
committing it all.

r351724:
Fix the name of the devicetree bindings document file cited in the manpage.
</content>
</entry>
<entry>
<title>Remove jedec_ts(4)</title>
<updated>2018-08-01T08:24:34Z</updated>
<author>
<name>Ravi Pokala</name>
<email>rpokala@FreeBSD.org</email>
</author>
<published>2018-08-01T08:24:34Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b598845049655b911e4c9c79b9d557da09f57b95'/>
<id>urn:sha1:b598845049655b911e4c9c79b9d557da09f57b95</id>
<content type='text'>
The jedec_ts(4) driver has been marked as deprecated in stable/11, and is
now being removed from -HEAD. Add a notice in UPDATING, and update the few
remaining references (regarding jedec_dimm(4)'s compatibility and history)
to reflect the fact that jedec_ts(4) is now deleted.

Reviewed by:	avg
Relnotes:	yes
Differential Revision:	https://reviews.freebsd.org/D16537
</content>
</entry>
<entry>
<title>Add opt_platform.h for several modules that have #ifdef FDT in the source.</title>
<updated>2018-04-01T18:22:24Z</updated>
<author>
<name>Ian Lepore</name>
<email>ian@FreeBSD.org</email>
</author>
<published>2018-04-01T18:22:24Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=74ca7bf1d4c7173d5575ba168bc4b5f6d181ff5a'/>
<id>urn:sha1:74ca7bf1d4c7173d5575ba168bc4b5f6d181ff5a</id>
<content type='text'>
Submitted by:	Andre Albsmeier &lt;Andre.Albsmeier@siemens.com&gt;
</content>
</entry>
<entry>
<title>Build the ds1672 driver as a module.  Add a detach() to unregister the rtc.</title>
<updated>2018-03-06T02:30:34Z</updated>
<author>
<name>Ian Lepore</name>
<email>ian@FreeBSD.org</email>
</author>
<published>2018-03-06T02:30:34Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b138780b0c4bdb80fde42b4df67a79ecf73773c6'/>
<id>urn:sha1:b138780b0c4bdb80fde42b4df67a79ecf73773c6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Build iicbus/rtc8583 as a module.</title>
<updated>2018-03-04T21:06:21Z</updated>
<author>
<name>Ian Lepore</name>
<email>ian@FreeBSD.org</email>
</author>
<published>2018-03-04T21:06:21Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5a45ce2f62c2e7621888144fe01a8c0a9d5ec215'/>
<id>urn:sha1:5a45ce2f62c2e7621888144fe01a8c0a9d5ec215</id>
<content type='text'>
</content>
</entry>
<entry>
<title>imcsmb(4): Intel integrated Memory Controller (iMC) SMBus controller driver</title>
<updated>2018-03-03T01:53:51Z</updated>
<author>
<name>Ravi Pokala</name>
<email>rpokala@FreeBSD.org</email>
</author>
<published>2018-03-03T01:53:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=24f93aa05f31d8b67368954967ef4cbdde350779'/>
<id>urn:sha1:24f93aa05f31d8b67368954967ef4cbdde350779</id>
<content type='text'>
imcsmb(4) provides smbus(4) support for the SMBus controller functionality
in the integrated Memory Controllers (iMCs) embedded in Intel Sandybridge-
Xeon, Ivybridge-Xeon, Haswell-Xeon, and Broadwell-Xeon CPUs. Each CPU
implements one or more iMCs, depending on the number of cores; each iMC
implements two SMBus controllers (iMC-SMBs).

*** IMPORTANT NOTE ***
Because motherboard firmware or the BMC might try to use the iMC-SMBs for
monitoring DIMM temperatures and/or managing an NVDIMM, the driver might
need to temporarily disable those functions, or take a hardware interlock,
before using the iMC-SMBs. Details on how to do this may vary from board to
board, and the procedure may be proprietary. It is strongly suggested that
anyone wishing to use this driver contact their motherboard vendor, and
modify the driver as described in the manual page and in the driver itself.
(For what it's worth, the driver as-is has been tested on various SuperMicro
motherboards.)

Reviewed by:	avg, jhb
MFC after:	1 week
Relnotes:	yes
Sponsored by:	Panasas
Differential Revision:	https://reviews.freebsd.org/D14447
Discussed with:	avg, ian, jhb
Tested by:	allanjude (previous version), Panasas
</content>
</entry>
<entry>
<title>Instead of building ofw_iicbus as a separate module, just compile it in to</title>
<updated>2018-02-25T18:26:50Z</updated>
<author>
<name>Ian Lepore</name>
<email>ian@FreeBSD.org</email>
</author>
<published>2018-02-25T18:26:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=f0a2d31ab1bbdefe9bbaeba22c6afd3680d28361'/>
<id>urn:sha1:f0a2d31ab1bbdefe9bbaeba22c6afd3680d28361</id>
<content type='text'>
the iicbus module for FDT-based systems.

The primary motivation for this is that host controller drivers which
declare DRIVER_MODULE(ofw_iicbus, thisdriver, etc, etc) now only need a
single MODULE_DEPEND(thisdriver, ofw_iicbus) for runtime linking to resolve
all the symbols.  With ofw_iicbus and iicbus in separate modules, drivers
would need to declare a MODULE_DEPEND() on both, because symbol lookup is
non-recursive through the dependency chain.  Requiring a driver to have
MODULE_DEPENDS() on both amounts to requiring the drivers to understand the
kobj inheritence details of how ofw_iicbus is implemented, which seems like
something they shouldn't have to know (and could even change some day).

Also, this is somewhat analogous to how the drivers get built when compiled
into the kernel.  You don't have to ask for ofw_iicbus separately, it just
gets built in along with iicbus when option FDT is in effect.
</content>
</entry>
<entry>
<title>jedec_dimm(4): report asset info and temperatures for DDR3 and DDR4 DIMMs</title>
<updated>2018-02-22T23:18:46Z</updated>
<author>
<name>Ravi Pokala</name>
<email>rpokala@FreeBSD.org</email>
</author>
<published>2018-02-22T23:18:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=dcd935dfd14a222d347f9d340b1b62243d47d522'/>
<id>urn:sha1:dcd935dfd14a222d347f9d340b1b62243d47d522</id>
<content type='text'>
A super-set of the functionality of jedec_ts(4). jedec_dimm(4) reports asset
information (Part Number, Serial Number) encoded in the "Serial Presence
Detect" (SPD) data on JEDEC DDR3 and DDR4 DIMMs. It also calculates and
reports the memory capacity of the DIMM, in megabytes. If the DIMM includes
a "Thermal Sensor On DIMM" (TSOD), the temperature is also reported.

Reviewed by:	cem
MFC after:	1 week
Relnotes:	yes
Sponsored by:	Panasas
Differential Revision:	https://reviews.freebsd.org/D14392
Discussed with:	avg, cem
Tested by:	avg, cem (previous version, no semantic changes)
</content>
</entry>
<entry>
<title>Build ofw_iicbus as a module if OPT_FDT is defined.</title>
<updated>2018-02-19T00:47:03Z</updated>
<author>
<name>Ian Lepore</name>
<email>ian@FreeBSD.org</email>
</author>
<published>2018-02-19T00:47:03Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a7e31772e7b23aa05bbc111da4d5e75b2d56bfd0'/>
<id>urn:sha1:a7e31772e7b23aa05bbc111da4d5e75b2d56bfd0</id>
<content type='text'>
</content>
</entry>
</feed>
