aboutsummaryrefslogtreecommitdiff
path: root/sys/dev/iicbus/mux
Commit message (Collapse)AuthorAgeFilesLines
* Replace calls to bus_generic_attach with bus_attach_childrenJohn Baldwin2024-12-064-4/+4
| | | | | Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D47675
* newbus: globally replace device_add_child(..., -1) with DEVICE_UNIT_ANYWarner Losh2024-07-251-2/+2
| | | | Sponsored by: Netflix
* iicbus/mux/pca954x: add support for PCA9546 I2C SwitchBjoern A. Zeeb2024-02-211-1/+10
| | | | | | | | | | | | Add support for the 4 channel I2C switch from NXP by adding a new description struct and the list entries. Compared to x=[2345] which require code to support the INT, for this one no further changes are needed. Tested on: WHLE-LS1088A using a SPF+ MFC after: 1 week Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D44009
* sys: Remove $FreeBSD$: one-line sh patternWarner Losh2023-08-161-1/+0
| | | | Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
* sys: Remove $FreeBSD$: one-line .c patternWarner Losh2023-08-165-10/+0
| | | | Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
* sys: Remove $FreeBSD$: two-line .h patternWarner Losh2023-08-161-2/+0
| | | | Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
* ltc430x(4): Fix a typo in a source code commentGordon Bergling2022-09-031-1/+1
| | | | | | - s/overriden/overridden/ MFC after: 3 days
* pca954x: harmonize pca9547 and pca954x and add pca9540 supportBjoern A. Zeeb2022-07-041-34/+74
| | | | | | | | | | | | | | | The two implementations for the pca9548 switch and the pca9547 mux seemed close enough so we can put them together and with a bit more abstraction add pca9540 support. While here apply a bit of consistency in variable and driver naming and use device_has_property instead of the FDT-only OF_ variant. This disconnects pca9547 from the build but does not yet delete it. MFC after: 2 weeks Reviewed by: mmel (earlier version), avg Differential Revision: https://reviews.freebsd.org/D35701
* iicbus: Remove unused devclass arguments to DRIVER_MODULE.John Baldwin2022-05-064-12/+5
|
* Remove unused ofw_iicbus_devclass.John Baldwin2022-05-064-5/+4
|
* Remove unused iicbus_devclass.John Baldwin2022-05-064-4/+4
|
* pca954x: driver for PCA954x / TCA954x I2C switchesAndriy Gapon2021-11-131-0/+214
| | | | | | At the moment only PCA9548A is supported and has been tested. MFC after: 2 weeks
* Revert "Define PNP info after defining driver modules"Mark Johnston2021-01-233-8/+6
| | | | | | | | | | | | | | | This reverts commit aa37baf3d7cf51da92fd367476182802e71838ae. The reverted commit was motivated by a problem observed on stable/12, but it turns out that a better solution was committed in r348309 but not MFCed. So, revert this change since it is unnecessary and not really correct: it assumes that the order in which module metadata records is defined determines their order in the output linker set. While this seems to hold in my testing, it is not guaranteed. Reported by: cem Discussed with: imp MFC after: 3 days
* Define PNP info after defining driver modulesMark Johnston2021-01-213-6/+8
| | | | | | | | | | | | | | | | PNP info definitions currently have an unfortunate requirement in that they must follow the associated module definition in the module metadata linker set. Otherwise devmatch can segfault while processing the linker hints file since kldxref maintains the order in the linker set. A number of drivers violate this requirement. In some cases this can cause devmatch(8) to segfault when processing the linker hints file. Work around the problem for now simply by adjusting the drivers. Reviewed by: imp MFC after: 1 week Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D28260
* Add basic support for Freescale LX2160A SoC.Michal Meloun2020-12-051-0/+162
| | | | | | | All peripherals but the network processor are supported. Notes: svn path=/head/; revision=368369
* Fix the variable name passed to OF_getprop().John Baldwin2020-09-021-1/+1
| | | | | | | Reported by: tinderbox Notes: svn path=/head/; revision=365283
* In ltc430x(4), add the ability to configure control register 2 via FDT orIan Lepore2020-09-021-2/+39
| | | | | | | | | | | | | | | hints data. Control register 2 holds the settings a user might want to configure, such as the timeout value for idle busses and whether to enable the mass-writes feature. Also add hint support for disconnecting idle busses (which was already supported using FDT data). Update the manpage with the new features, and also split the hints section into separate lists of required and optional hints. Notes: svn path=/head/; revision=365274
* iicmux: fix a sign error in comparisonAndriy Gapon2020-08-181-1/+1
| | | | | | | | | | | | Because pcell_t is unsigned both sides of the comparison were treated as such. Because of that error iicmux created all possible sub-buses even if only a subset was defined in the device tree. MFC after: 1 week Notes: svn path=/head/; revision=364344
* Remove some trailing whitespace; no functional changes.Ian Lepore2020-01-081-3/+3
| | | | Notes: svn path=/head/; revision=356526
* Split the code to find and add iicbus children out to its own function.Ian Lepore2020-01-081-38/+41
| | | | | | | | | | | | | Move the decision to take an early exit from that function after adding children based on FDT data into the #ifdef FDT block, so that it doesn't offend coverity's notion of how the code should be written. (What's the point of compilers optimizing away dead code if static analyzers won't let you use the feature in conjuction with an #ifdef block?) Reported by: coverity via vangyzen@ Notes: svn path=/head/; revision=356525
* Change some KASSERT to device_printf + return EINVAL. There's no need toIan Lepore2020-01-081-10/+15
| | | | | | | | bring the whole kernel down due to a configuration error detected when a module is loaded, it suffices to just not attach the device. Notes: svn path=/head/; revision=356522
* Init sc->maxbus to -1, not 0. It represents the highest array index thatIan Lepore2020-01-081-4/+6
| | | | | | | | | | has a non-NULL child bus stored in it, so the "none" value can't be zero since that's a valid array index. Also, when adding all possible buses because there is no specific per-bus config, there's no need to reset sc->maxbus on each loop iteration, it can be set once after the loop. Notes: svn path=/head/; revision=356521
* Ensure any reserved gpio pins get released if an early exit is takenIan Lepore2020-01-081-7/+25
| | | | | | | from the attach function. Notes: svn path=/head/; revision=356519
* Add support for i2c bus mux hardware.Ian Lepore2020-01-025-0/+984
An i2c bus can be divided into segments which can be selectively connected and disconnected from the main bus. This is usually done to enable using multiple slave devices having the same address, by isolating the devices onto separate bus segments, only one of which is connected to the main bus at once. There are several types of i2c bus muxes, which break down into two general categories... - 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 instances representing the downstream buses. The mux driver implements the iicbus_if interface, as if it were an iichb host bridge/i2c controller driver. It services the IO requests sent to it by forwarding them to the iicbus instance representing the upstream bus, after electrically connecting the upstream bus to the downstream bus that hosts the i2c slave device which made the IO request. The net effect is automatic mux switching which is transparent to slaves on the downstream buses. They just do i2c IO they way they normally do, and the bus is electrically connected for the duration of the IO and then idled when it is complete. The existing iicbus_if callback() method is enhanced so that the parameter passed to it can be a struct which contains a device_t for the requesting bus and slave devices. This change is done by adding a flag that indicates the extra values are present, and making the flags field the first field of a new args struct. If the flag is set, the iichb or mux driver can recast the pointer-to-flags into a pointer-to-struct and access the extra fields. Thus abi compatibility with older drivers is retained (but a mux cannot 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 help implement mux drivers for any type of mux hardware by supplying all the boilerplate code that forwards IO requests upstream. It also has code for parsing metadata and instantiating the child iicbus instances based on it. Two new hardware mux drivers are added. The ltc430x driver supports the LTC4305/4306 mux chips which are controlled via i2c commands. The iic_gpiomux driver supports any mux hardware which is controlled by manipulating the state of one or more gpio pins. Test Plan Tested locally using a variety of mux'd bus configurations involving both ltc4305 and a homebrew gpio-controlled mux. Tested configurations included cascaded muxes (unlikely in the real world, but useful to prove that 'it all just works' in terms of the automatic switching and upstream forwarding of IO requests). Notes: svn path=/head/; revision=356278
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-16 13:02:21 +0000