openbsd-src/sys/dev/ofw/ at rk3128 · jcs.org/openbsd-src

jcs.org / openbsd-src

jcs's openbsd hax

openbsd

openbsd-src / sys / dev / ofw /

at rk3128 19 files

Introduce OF_is_enabled(), a helper function to figure out whether the device tree node is available to use or not. So far we have done this manually by explicitly checking for "disabled". Nowadays though there's also "reserved" for devices that are there but shouldn't be touched, and at some point we might need to handle "fail", too. We can't just check for "okay" as some device trees only have "ok" or not even a status property, which we should treat as "okay".

3 months ago

Add functions to set/add properties on an FDT node.

5 years ago

Add thermal zone handling code. This provides support for thermal zones defined in device trees that link together thermal sensors and cooling devices to actively or passively cool devices when certain trip points are reached.

6 years ago

Fix typo that caused us to misassign parents.

7 years ago

Add prototype for clock_set_frequency_idx().

4 years ago

Implement support for using GPIO pins as interrupt pins.

1 year ago

Implement support for using GPIO pins as interrupt pins.

1 year ago

On the Qualcomm SC7280/QCS6490 SoC there is a second cell in the IOMMU specifier that represents an SMR mask. However the "iommu-map" property only specifies how the stream ID gets mapped. Adjust the implementation of iommu_device_lookup_pci() based on these new insights. This means that for PCI devices we pass an SMR mask of zero. That seems to match what Linux does.

2 months ago

Properly set up the IOMMU stream ID mapping. Needed for upcoming changes to apldart(4).

2 years ago

First pass at removing clauses 3 and 4 from NetBSD licenses.

18 years ago

Some devices have no phandle since they are not referenced in the device tree, but they are still registered in our OFW framework. These then tend to have a phandle 0. If we are trying to lookup a device by phandle, we should explicitly check for phandle 0 and bail, since otherwise it is possible that we falsely match that phandle and return a device.

5 years ago

Fix a pasto in a comment.

9 years ago

Add interfaces to enable all power domains for a node.

4 years ago

Add interfaces to enable all power domains for a node.

4 years ago

ofw_regulator.c

Disallow setting the voltage of coupled regulators for now. Some RK3588 boards use different regulators for CPU core voltage and memory interface voltage. But the two have to be kept synchronized. So the devicetree for these boards marks these regulators as coupled. We have no support for coupled regulators yet and letting the DVFS code set just the CPU core voltage would probably lead to strange crashes.

2 years ago

ofw_regulator.h

Disallow setting the voltage of coupled regulators for now. Some RK3588 boards use different regulators for CPU core voltage and memory interface voltage. But the two have to be kept synchronized. So the devicetree for these boards marks these regulators as coupled. We have no support for coupled regulators yet and letting the DVFS code set just the CPU core voltage would probably lead to strange crashes.

2 years ago

Set the cooling level of all cooling devices to 0 when we initialize a zone. This makes sure that things like fans don't stay permanently on if we're below the first trip point. If we're already above the first trip point the code to turn the fans on will run immediately after we finish initialization.

6 months ago

Implement an optional callback function for thermal sensors to set a trip limit to support thermal zones that don't do polling. Thermal sensor drivers should implement this callback if they can generate an interrupt when the trop limit is reached and should call thermal_senser_update() when that happens.

2 years ago

Introduce OF_is_enabled(), a helper function to figure out whether the device tree node is available to use or not. So far we have done this manually by explicitly checking for "disabled". Nowadays though there's also "reserved" for devices that are there but shouldn't be touched, and at some point we might need to handle "fail", too. We can't just check for "okay" as some device trees only have "ok" or not even a status property, which we should treat as "okay".

3 months ago