MFC r350303: enable ig4_acpi on aarch64The already-listed APMC0D0F ID belongs to the Ampere eMAG aarch64platform, but ACPI support was not even built on aarch64.Submitted by: Greg V <greg_unrele
MFC r350303: enable ig4_acpi on aarch64The already-listed APMC0D0F ID belongs to the Ampere eMAG aarch64platform, but ACPI support was not even built on aarch64.Submitted by: Greg V <greg_unrelenting.technology>
show more ...
MFC r350591, r350971, r351724r350591: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 reconfigur
MFC r350591, r350971, r351724r350591: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).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 lastminute it got renamed to ads111x to reflect its support for many relatedchips, but I forgot to update the manpage to match the renaming beforecommitting it all.r351724:Fix the name of the devicetree bindings document file cited in the manpage.
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 (regardin
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)'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
Add opt_platform.h for several modules that have #ifdef FDT in the source.Submitted by: Andre Albsmeier <[email protected]>
Build the ds1672 driver as a module. Add a detach() to unregister the rtc.
Build iicbus/rtc8583 as a module.
imcsmb(4): Intel integrated Memory Controller (iMC) SMBus controller driverimcsmb(4) provides smbus(4) support for the SMBus controller functionalityin the integrated Memory Controllers (iMCs) emb
imcsmb(4): Intel integrated Memory Controller (iMC) SMBus controller driverimcsmb(4) provides smbus(4) support for the SMBus controller functionalityin the integrated Memory Controllers (iMCs) embedded in Intel Sandybridge-Xeon, Ivybridge-Xeon, Haswell-Xeon, and Broadwell-Xeon CPUs. Each CPUimplements one or more iMCs, depending on the number of cores; each iMCimplements two SMBus controllers (iMC-SMBs).*** IMPORTANT NOTE ***Because motherboard firmware or the BMC might try to use the iMC-SMBs formonitoring DIMM temperatures and/or managing an NVDIMM, the driver mightneed 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 toboard, and the procedure may be proprietary. It is strongly suggested thatanyone wishing to use this driver contact their motherboard vendor, andmodify 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 SuperMicromotherboards.)Reviewed by: avg, jhbMFC after: 1 weekRelnotes: yesSponsored by: PanasasDifferential Revision: https://reviews.freebsd.org/D14447Discussed with: avg, ian, jhbTested by: allanjude (previous version), Panasas
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 DRIV
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'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't have to ask for ofw_iicbus separately, it justgets built in along with iicbus when option FDT is in effect.
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) encode
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 "Serial PresenceDetect" (SPD) data on JEDEC DDR3 and DDR4 DIMMs. It also calculates andreports the memory capacity of the DIMM, in megabytes. If the DIMM includesa "Thermal Sensor On DIMM" (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)
Build ofw_iicbus as a module if OPT_FDT is defined.
Add iic_recover_bus.c, now part of iicbus. This should have been addedas part of r320463.
Arrange SRCS= as 1 file per line, alphabetical, so it's easier to maintain.Whitespace only, no functional changes.
Give icee(4) a detach() method so it can be used as a module. Add amodule makefile for it.
Add a missing header file to SRCS to fix out-of-kernel builds.PR: 222354Submitted by: eugen@Pointy hat: ian@
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
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't do transfers without interrupts.- Add a detach() routine.- Add to module build.
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 th
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 "chiptype" string of the form "dallas,ds13xx" where 'xx' is the chip id(i.e., the same format as FDT compat strings).
Add missing header file to SRCS.Reported by: manu@
Add missing ofw_bus_if.h src file.
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).
Build iicbus/{ds1307,ds3231,nxprtc} as modules.
Restructure the SUBDIR list as 1-per-line and alphabetize, so it will beeasier to add new things (and see what changed) in the future.
sys/modules: normalize .CURDIR-relative paths to SRCTOPThis simplifies make output/logicTested with: `cd sys/modules; make ALL_MODULES=` on amd64MFC after: 1 monthSponsored by: Dell EMC Isilon
Remove pc98 support completely.I thank all developers and contributors for pc98.Relnotes: yes
[ig4] Add ACPI platform support for ig4 driverAdd ACPI part for ig4 driver to make it work on Intel BayTrail SoC whereig4 device is available only through ACPIReviewed by: avgMFC after: 1 week
[ig4] Add ACPI platform support for ig4 driverAdd ACPI part for ig4 driver to make it work on Intel BayTrail SoC whereig4 device is available only through ACPIReviewed by: avgMFC after: 1 weekDifferential Revision: https://reviews.freebsd.org/D8742
add iic interface to ig4 driver, move isl and cyapa to iicbusSummary:The hardware does not expose a classic SMBus interface.Instead it has a lower level interface that can express a far richerI2
add iic interface to ig4 driver, move isl and cyapa to iicbusSummary:The hardware does not expose a classic SMBus interface.Instead it has a lower level interface that can express a far richerI2C protocol than what smbus offers. However, the interface does notprovide a way to explicitly generate the I2C stop and start conditions.It's only possible to request that the stop condition is generatedafter transferring the next byte in either direction. So, at leastone data byte must always be transferred.Thus, some I2C sequences are impossible to generate, e.g., an equivalentof smbus quick command (<start>-<slave addr>-<r/w bit>-<stop>).At the same time isl(4) and cyapa(4) are moved to iicbus and now they useiicbus_transfer for communication. Previously they used smbus_trans()interface that is not defined by the SMBus protocol and was implementedonly by ig4(4). In fact, that interface was impossible to implementfor the typical SMBus controllers like intpm(4) or ichsmb(4) wherea type of the SMBus command must be programmed.The plan is to remove smbus_trans() and all its uses.As an aside, the smbus_trans() method deviates from the standard,but perhaps backwards, FreeBSD convention of using 8-bit slaveaddresses (shifted by 1 bit to the left). The method expects7-bit addresses.There is a user facing consequence of this change.A user must now provide device hints for isl and cyapa that specify an iicbus to useand a slave address on it.On Chromebook hardware where isl and cyapa devices are commonly foundit is also possible to use a new chromebook_platform(4) driver thatautomatically configures isl and cyapa devices. There is no need toprovide the device hints in that case,Right now smbus(4) driver tries to discover all slaves on the bus.That is very dangerous. Fortunately, the probing code uses smbus_trans()to do its job, so it is really enabled for ig4 only.The plan is to remove that auto-probing code and smbus_trans().Tested by: grembo, Matthias Apitz <[email protected]> (w/o chromebook_platform)Discussed with: grembo, impReviewed by: wblock (docs)MFC after: 1 monthRelnotes: yesDifferential Revision: https://reviews.freebsd.org/D8172
123