Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1466991
Summary: | Frequency scaling and thermal zones do not work for iMX6 SOC | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | billiboy |
Component: | kernel | Assignee: | Peter Robinson <pbrobinson> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, pbrobinson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kernel-4.15.2-300.fc27 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-03-05 17:14:04 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 245418 |
Description
billiboy
2017-07-01 08:20:41 UTC
> Additional info:
>
> Building the fedora kernel source package with CONFIG_ARM_IMX6Q_CPUFREQ=y,
> CONFIG_IMX_THERMAL=y, CONFIG_NVMEM=y, CONFIG_NVMEM_IMX_OCOTP=y, i.e flipping
> the modules to build-in make it work for me. cat
> /sys/devices/system/cpu/cpufreq/policy0/stats/time_in_state reports proper
> frequency state usage and the by fuses provided trip points get used.
Which shouldn't be the case, it should work when built modular. We can't build everything in for a distro kernel or else we'd not have enough memory to run. This really needs to be fixed upstream
This will be fixed in 4.15.3+ |