August 2019 - Linux-stable-mirror

[PATCH v2] gpiolib: acpi: Add gpiolib_acpi_run_edge_events_on_boot option and blacklist

by Hans de Goede

Another day; another DSDT bug we need to workaround... Since commit ca876c7483b6 ("gpiolib-acpi: make sure we trigger edge events at least once on boot") we call _AEI edge handlers at boot. In some rare cases this causes problems. One example of this is the Minix Neo Z83-4 mini PC, this device has a clear DSDT bug where it has some copy and pasted code for dealing with Micro USB-B connector host/device role switching, while the mini PC does not even have a micro-USB connector. This code, which should not be there, messes with the DDC data pin from the HDMI connector (switching it to GPIO mode) breaking HDMI support. To avoid problems like this, this commit adds a new gpiolib_acpi.run_edge_events_on_boot kernel commandline option, which allows disabling the running of _AEI edge event handlers at boot. The default value is -1/auto which uses a DMI based blacklist, the initial version of this blacklist contains the Neo Z83-4 fixing the HDMI breakage. Cc: stable(a)vger.kernel.org Cc: Daniel Drake <drake(a)endlessm.com> Cc: Ian W MORRISON <ianwmorrison(a)gmail.com> Reported-by: Ian W MORRISON <ianwmorrison(a)gmail.com> Suggested-by: Ian W MORRISON <ianwmorrison(a)gmail.com> Fixes: ca876c7483b6 ("gpiolib-acpi: make sure we trigger edge events at least once on boot") Signed-off-by: Hans de Goede <hdegoede(a)redhat.com> --- Changes in v2: - Use a module_param instead of __setup - Do DMI check only once from a postcore_initcall --- drivers/gpio/gpiolib-acpi.c | 42 +++++++++++++++++++++++++++++++++---- 1 file changed, 38 insertions(+), 4 deletions(-) diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c index 39f2f9035c11..bda28eb82c3f 100644 --- a/drivers/gpio/gpiolib-acpi.c +++ b/drivers/gpio/gpiolib-acpi.c @@ -7,6 +7,7 @@ * Mika Westerberg <mika.westerberg(a)linux.intel.com> */ +#include <linux/dmi.h> #include <linux/errno.h> #include <linux/gpio/consumer.h> #include <linux/gpio/driver.h> @@ -19,6 +20,11 @@ #include "gpiolib.h" +static int run_edge_events_on_boot = -1; +module_param(run_edge_events_on_boot, int, 0444); +MODULE_PARM_DESC(run_edge_events_on_boot, + "Run edge _AEI event-handlers at boot: 0=no, 1=yes, -1=auto"); + /** * struct acpi_gpio_event - ACPI GPIO event handler data * @@ -170,10 +176,13 @@ static void acpi_gpiochip_request_irq(struct acpi_gpio_chip *acpi_gpio, event->irq_requested = true; /* Make sure we trigger the initial state of edge-triggered IRQs */ - value = gpiod_get_raw_value_cansleep(event->desc); - if (((event->irqflags & IRQF_TRIGGER_RISING) && value == 1) || - ((event->irqflags & IRQF_TRIGGER_FALLING) && value == 0)) - event->handler(event->irq, event); + if (run_edge_events_on_boot && + (event->irqflags & (IRQF_TRIGGER_RISING | IRQF_TRIGGER_FALLING))) { + value = gpiod_get_raw_value_cansleep(event->desc); + if (((event->irqflags & IRQF_TRIGGER_RISING) && value == 1) || + ((event->irqflags & IRQF_TRIGGER_FALLING) && value == 0)) + event->handler(event->irq, event); + } } static void acpi_gpiochip_request_irqs(struct acpi_gpio_chip *acpi_gpio) @@ -1283,3 +1292,28 @@ static int acpi_gpio_handle_deferred_request_irqs(void) } /* We must use _sync so that this runs after the first deferred_probe run */ late_initcall_sync(acpi_gpio_handle_deferred_request_irqs); + +static const struct dmi_system_id run_edge_events_on_boot_blacklist[] = { + { + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "MINIX"), + DMI_MATCH(DMI_PRODUCT_NAME, "Z83-4"), + } + }, + {} /* Terminating entry */ +}; + +static int acpi_gpio_setup_params(void) +{ + if (run_edge_events_on_boot < 0) { + if (dmi_check_system(run_edge_events_on_boot_blacklist)) + run_edge_events_on_boot = 0; + else + run_edge_events_on_boot = 1; + } + + return 0; +} + +/* Directly after dmi_setup() which runs as core_initcall() */ +postcore_initcall(acpi_gpio_setup_params); -- 2.23.0

4 years, 7 months

5
6
0 0

❌ FAIL: Stable queue: queue-5.2

by CKI Project

Hello, We ran automated tests on a patchset that was proposed for merging into this kernel tree. The patches were applied to: Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Commit: f7d5b3dc4792 - Linux 5.2.10 The results of these automated tests are provided below. Overall result: FAILED (see details below) Merge: OK Compile: OK Tests: FAILED All kernel binaries, config files, and logs are available for download here: https://artifacts.cki-project.org/pipelines/128519 One or more kernel tests failed: x86_64: ❌ Networking socket: fuzz We hope that these logs can help you find the problem quickly. For the full detail on our testing procedures, please scroll to the bottom of this message. Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Merge testing ------------- We cloned this repository and checked out the following commit: Repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Commit: f7d5b3dc4792 - Linux 5.2.10 We grabbed the 54831dad38d2 commit of the stable queue repository. We then merged the patchset with `git am`: asoc-simple_card_utils.h-care-null-dai-at-asoc_simpl.patch asoc-simple-card-fix-an-use-after-free-in-simple_dai.patch asoc-simple-card-fix-an-use-after-free-in-simple_for.patch asoc-audio-graph-card-fix-use-after-free-in-graph_da.patch asoc-audio-graph-card-fix-an-use-after-free-in-graph.patch asoc-audio-graph-card-add-missing-const-at-graph_get.patch regulator-axp20x-fix-dcdca-and-dcdcd-for-axp806.patch regulator-axp20x-fix-dcdc5-and-dcdc6-for-axp803.patch asoc-samsung-odroid-fix-an-use-after-free-issue-for-.patch asoc-samsung-odroid-fix-a-double-free-issue-for-cpu_.patch asoc-intel-bytcht_es8316-add-quirk-for-irbis-nb41-ne.patch hid-logitech-hidpp-add-usb-pid-for-a-few-more-suppor.patch hid-add-044f-b320-thrustmaster-inc.-2-in-1-dt.patch mips-kernel-only-use-i8253-clocksource-with-periodic.patch mips-fix-cacheinfo.patch libbpf-sanitize-var-to-conservative-1-byte-int.patch netfilter-ebtables-fix-a-memory-leak-bug-in-compat.patch asoc-dapm-fix-handling-of-custom_stop_condition-on-d.patch asoc-sof-use-__u32-instead-of-uint32_t-in-uapi-heade.patch spi-pxa2xx-balance-runtime-pm-enable-disable-on-erro.patch bpf-sockmap-sock_map_delete-needs-to-use-xchg.patch bpf-sockmap-synchronize_rcu-before-free-ing-map.patch bpf-sockmap-only-create-entry-if-ulp-is-not-already-.patch selftests-bpf-fix-sendmsg6_prog-on-s390.patch asoc-dapm-fix-a-memory-leak-bug.patch bonding-force-slave-speed-check-after-link-state-rec.patch net-mvpp2-don-t-check-for-3-consecutive-idle-frames-.patch selftests-forwarding-gre_multipath-enable-ipv4-forwa.patch selftests-forwarding-gre_multipath-fix-flower-filter.patch selftests-bpf-add-another-gso_segs-access.patch libbpf-fix-using-uninitialized-ioctl-results.patch can-dev-call-netif_carrier_off-in-register_candev.patch can-mcp251x-add-error-check-when-wq-alloc-failed.patch can-gw-fix-error-path-of-cgw_module_init.patch asoc-fail-card-instantiation-if-dai-format-setup-fai.patch staging-fbtft-fix-gpio-handling.patch libbpf-silence-gcc8-warning-about-string-truncation.patch st21nfca_connectivity_event_received-null-check-the-.patch st_nci_hci_connectivity_event_received-null-check-th.patch nl-mac-80211-fix-interface-combinations-on-crypto-co.patch asoc-ti-davinci-mcasp-fix-clk-pdir-handling-for-i2s-.patch asoc-rockchip-fix-mono-capture.patch asoc-ti-davinci-mcasp-correct-slot_width-posed-const.patch net-usb-qmi_wwan-add-the-broadmobi-bm818-card.patch qed-rdma-fix-the-hw_ver-returned-in-device-attribute.patch isdn-misdn-hfcsusb-fix-possible-null-pointer-derefer.patch habanalabs-fix-f-w-download-in-be-architecture.patch mac80211_hwsim-fix-possible-null-pointer-dereference.patch net-stmmac-manage-errors-returned-by-of_get_mac_addr.patch netfilter-ipset-actually-allow-destination-mac-addre.patch netfilter-ipset-copy-the-right-mac-address-in-bitmap.patch netfilter-ipset-fix-rename-concurrency-with-listing.patch rxrpc-fix-potential-deadlock.patch rxrpc-fix-the-lack-of-notification-when-sendmsg-fail.patch nvmem-use-the-same-permissions-for-eeprom-as-for-nvm.patch iwlwifi-mvm-avoid-races-in-rate-init-and-rate-perfor.patch iwlwifi-dbg_ini-move-iwl_dbg_tlv_load_bin-out-of-deb.patch iwlwifi-dbg_ini-move-iwl_dbg_tlv_free-outside-of-deb.patch iwlwifi-fix-locking-in-delayed-gtk-setting.patch iwlwifi-mvm-send-lq-command-always-async.patch enetc-fix-build-error-without-phylib.patch isdn-hfcsusb-fix-misdn-driver-crash-caused-by-transf.patch net-phy-phy_led_triggers-fix-a-possible-null-pointer.patch perf-bench-numa-fix-cpu0-binding.patch spi-pxa2xx-add-support-for-intel-tiger-lake.patch can-sja1000-force-the-string-buffer-null-terminated.patch can-peak_usb-force-the-string-buffer-null-terminated.patch asoc-amd-acp3x-use-dma_ops-of-parent-device-for-acp3.patch net-ethernet-qlogic-qed-force-the-string-buffer-null.patch enetc-select-phylib-while-config_fsl_enetc_vf-is-set.patch nfsv4-fix-a-credential-refcount-leak-in-nfs41_check_.patch nfsv4-when-recovering-state-fails-with-eagain-retry-.patch nfsv4.1-fix-open-stateid-recovery.patch nfsv4.1-only-reap-expired-delegations.patch nfsv4-fix-a-potential-sleep-while-atomic-in-nfs4_do_.patch nfs-fix-regression-whereby-fscache-errors-are-appear.patch hid-quirks-set-the-increment_usage_on_duplicate-quir.patch hid-input-fix-a4tech-horizontal-wheel-custom-usage.patch drm-rockchip-suspend-dp-late.patch smb3-fix-potential-memory-leak-when-processing-compo.patch smb3-kernel-oops-mounting-a-encryptdata-share-with-c.patch sched-deadline-fix-double-accounting-of-rq-running-b.patch sched-psi-reduce-psimon-fifo-priority.patch sched-psi-do-not-require-setsched-permission-from-th.patch s390-protvirt-avoid-memory-sharing-for-diag-308-set-.patch s390-mm-fix-dump_pagetables-top-level-page-table-wal.patch s390-put-_stext-and-_etext-into-.text-section.patch ata-rb532_cf-fix-unused-variable-warning-in-rb532_pa.patch net-cxgb3_main-fix-a-resource-leak-in-a-error-path-i.patch net-stmmac-fix-issues-when-number-of-queues-4.patch net-stmmac-tc-do-not-return-a-fragment-entry.patch drm-amdgpu-pin-the-csb-buffer-on-hw-init-for-gfx-v8.patch net-hisilicon-make-hip04_tx_reclaim-non-reentrant.patch net-hisilicon-fix-hip04-xmit-never-return-tx_busy.patch net-hisilicon-fix-dma_map_single-failed-on-arm64.patch nfsv4-ensure-state-recovery-handles-etimedout-correc.patch libata-have-ata_scsi_rw_xlat-fail-invalid-passthroug.patch libata-add-sg-safety-checks-in-sff-pio-transfers.patch x86-lib-cpu-address-missing-prototypes-warning.patch drm-vmwgfx-fix-memory-leak-when-too-many-retries-hav.patch block-aoe-fix-kernel-crash-due-to-atomic-sleep-when-.patch block-bfq-handle-null-return-value-by-bfq_init_rq.patch perf-ftrace-fix-failure-to-set-cpumask-when-only-one.patch perf-cpumap-fix-writing-to-illegal-memory-in-handlin.patch perf-pmu-events-fix-missing-cpu_clk_unhalted.core-ev.patch dt-bindings-riscv-fix-the-schema-compatible-string-f.patch kvm-arm64-don-t-write-junk-to-sysregs-on-reset.patch kvm-arm-don-t-write-junk-to-cp15-registers-on-reset.patch selftests-kvm-adding-config-fragments.patch iwlwifi-mvm-disable-tx-amsdu-on-older-nics.patch hid-wacom-correct-misreported-ekr-ring-values.patch hid-wacom-correct-distance-scale-for-2nd-gen-intuos-devices.patch revert-kvm-x86-mmu-zap-only-the-relevant-pages-when-removing-a-memslot.patch revert-dm-bufio-fix-deadlock-with-loop-device.patch clk-socfpga-stratix10-fix-rate-caclulationg-for-cnt_clks.patch ceph-clear-page-dirty-before-invalidate-page.patch ceph-don-t-try-fill-file_lock-on-unsuccessful-getfilelock-reply.patch libceph-fix-pg-split-vs-osd-re-connect-race.patch drm-amdgpu-gfx9-update-pg_flags-after-determining-if-gfx-off-is-possible.patch drm-nouveau-don-t-retry-infinitely-when-receiving-no-data-on-i2c-over-aux.patch scsi-ufs-fix-null-pointer-dereference-in-ufshcd_config_vreg_hpm.patch gpiolib-never-report-open-drain-source-lines-as-input-to-user-space.patch drivers-hv-vmbus-fix-virt_to_hvpfn-for-x86_pae.patch userfaultfd_release-always-remove-uffd-flags-and-clear-vm_userfaultfd_ctx.patch x86-retpoline-don-t-clobber-rflags-during-call_nospec-on-i386.patch x86-apic-handle-missing-global-clockevent-gracefully.patch x86-cpu-amd-clear-rdrand-cpuid-bit-on-amd-family-15h-16h.patch x86-boot-save-fields-explicitly-zero-out-everything-else.patch x86-boot-fix-boot-regression-caused-by-bootparam-sanitizing.patch ib-hfi1-unsafe-psn-checking-for-tid-rdma-read-resp-packet.patch ib-hfi1-add-additional-checks-when-handling-tid-rdma-read-resp-packet.patch ib-hfi1-add-additional-checks-when-handling-tid-rdma-write-data-packet.patch ib-hfi1-drop-stale-tid-rdma-packets-that-cause-tiderr.patch psi-get-poll_work-to-run-when-calling-poll-syscall-next-time.patch dm-kcopyd-always-complete-failed-jobs.patch dm-dust-use-dust-block-size-for-badblocklist-index.patch dm-btree-fix-order-of-block-initialization-in-btree_split_beneath.patch dm-integrity-fix-a-crash-due-to-bug_on-in-__journal_read_write.patch dm-raid-add-missing-cleanup-in-raid_ctr.patch dm-space-map-metadata-fix-missing-store-of-apply_bops-return-value.patch dm-table-fix-invalid-memory-accesses-with-too-high-sector-number.patch dm-zoned-improve-error-handling-in-reclaim.patch dm-zoned-improve-error-handling-in-i-o-map-code.patch dm-zoned-properly-handle-backing-device-failure.patch genirq-properly-pair-kobject_del-with-kobject_add.patch mm-z3fold.c-fix-race-between-migration-and-destruction.patch mm-page_alloc-move_freepages-should-not-examine-struct-page-of-reserved-memory.patch mm-memcontrol-flush-percpu-vmstats-before-releasing-memcg.patch mm-memcontrol-flush-percpu-vmevents-before-releasing-memcg.patch mm-page_owner-handle-thp-splits-correctly.patch mm-zsmalloc.c-migration-can-leave-pages-in-zs_empty-indefinitely.patch mm-zsmalloc.c-fix-race-condition-in-zs_destroy_pool.patch mm-kasan-fix-false-positive-invalid-free-reports-with-config_kasan_sw_tags-y.patch xfs-fix-missing-ilock-unlock-when-xfs_setattr_nonsize-fails-due-to-edquot.patch ib-hfi1-drop-stale-tid-rdma-packets.patch dm-zoned-fix-potential-null-dereference-in-dmz_do_re.patch io_uring-fix-potential-hang-with-polled-io.patch io_uring-don-t-enter-poll-loop-if-we-have-cqes-pendi.patch io_uring-add-need_resched-check-in-inner-poll-loop.patch powerpc-allow-flush_-inval_-dcache_range-to-work-across-ranges-4gb.patch rxrpc-fix-local-endpoint-refcounting.patch rxrpc-fix-read-after-free-in-rxrpc_queue_local.patch rxrpc-fix-local-endpoint-replacement.patch Compile testing --------------- We compiled the kernel for 3 architectures: aarch64: make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg ppc64le: make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg x86_64: make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test [0] ✅ xfstests: xfs [1] ✅ selinux-policy: serge-testsuite [2] ✅ lvm thinp sanity [3] ✅ storage: software RAID testing [4] 🚧 ✅ Storage blktests [5] Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test [0] ⚡⚡⚡ Podman system integration test (as root) [6] ⚡⚡⚡ Podman system integration test (as user) [6] ⚡⚡⚡ Loopdev Sanity [7] ⚡⚡⚡ jvm test suite [8] ⚡⚡⚡ AMTU (Abstract Machine Test Utility) [9] ⚡⚡⚡ LTP: openposix test suite [10] ⚡⚡⚡ Ethernet drivers sanity [11] ⚡⚡⚡ Networking socket: fuzz [12] ⚡⚡⚡ audit: audit testsuite test [13] ⚡⚡⚡ httpd: mod_ssl smoke sanity [14] ⚡⚡⚡ iotop: sanity [15] ⚡⚡⚡ tuned: tune-processes-through-perf [16] ⚡⚡⚡ Usex - version 1.9-29 [17] ⚡⚡⚡ storage: SCSI VPD [18] ⚡⚡⚡ stress: stress-ng [19] 🚧 ⚡⚡⚡ LTP lite [20] ppc64le: Host 1: ✅ Boot test [0] ✅ xfstests: xfs [1] ✅ selinux-policy: serge-testsuite [2] ✅ lvm thinp sanity [3] ✅ storage: software RAID testing [4] 🚧 ✅ Storage blktests [5] Host 2: ✅ Boot test [0] ✅ Podman system integration test (as root) [6] ✅ Podman system integration test (as user) [6] ✅ Loopdev Sanity [7] ✅ jvm test suite [8] ✅ AMTU (Abstract Machine Test Utility) [9] ✅ LTP: openposix test suite [10] ✅ Ethernet drivers sanity [11] ✅ Networking socket: fuzz [12] ✅ audit: audit testsuite test [13] ✅ httpd: mod_ssl smoke sanity [14] ✅ iotop: sanity [15] ✅ tuned: tune-processes-through-perf [16] ✅ Usex - version 1.9-29 [17] 🚧 ✅ LTP lite [20] x86_64: Host 1: ✅ Boot test [0] ✅ Podman system integration test (as root) [6] ✅ Podman system integration test (as user) [6] ✅ Loopdev Sanity [7] ✅ jvm test suite [8] ✅ AMTU (Abstract Machine Test Utility) [9] ✅ LTP: openposix test suite [10] ✅ Ethernet drivers sanity [11] ❌ Networking socket: fuzz [12] ⚡⚡⚡ audit: audit testsuite test [13] ⚡⚡⚡ httpd: mod_ssl smoke sanity [14] ⚡⚡⚡ iotop: sanity [15] ⚡⚡⚡ tuned: tune-processes-through-perf [16] ⚡⚡⚡ pciutils: sanity smoke test [21] ⚡⚡⚡ Usex - version 1.9-29 [17] ⚡⚡⚡ storage: SCSI VPD [18] ⚡⚡⚡ stress: stress-ng [19] 🚧 ❌ LTP lite [20] Host 2: ✅ Boot test [0] ✅ xfstests: xfs [1] ✅ selinux-policy: serge-testsuite [2] ✅ lvm thinp sanity [3] ✅ storage: software RAID testing [4] 🚧 ✅ Storage blktests [5] Test source: 💚 Pull requests are welcome for new tests or improvements to existing tests! [0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution… [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems… [2]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/se… [3]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/… [4]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/swra… [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/blk [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/container/p… [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#filesystems/… [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/jvm [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#misc/amtu [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution… [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/aud… [14]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/htt… [15]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/iot… [16]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tun… [17]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/us… [18]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/scsi… [19]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stres… [20]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution… [21]: https://github.com/CKI-project/tests-beaker/archive/master.zip#pciutils/san… Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed.

4 years, 7 months

4
5
0 0

[PATCH v2] regulator: twl: voltage lists for vdd1/2 on twl4030

by Andreas Kemnade

_opp_supported_by_regulators() wrongly ignored errors from regulator_is_supported_voltage(), so it considered errors as success. Since commit 498209445124 ("regulator: core: simplify return value on suported_voltage") regulator_is_supported_voltage() returns a real boolean, so errors make _opp_supported_by_regulators() return false. That reveals a problem with the declaration of the VDD1/2 regulators on twl4030. The VDD1/VDD2 regulators on twl4030 are neither defined with voltage lists nor with the continuous flag set, so regulator_is_supported_voltage() returns false and an error before above mentioned commit (which was considered success) The result is that after the above mentioned commit cpufreq does not work properly e.g. dm3730. [ 2.490997] core: _opp_supported_by_regulators: OPP minuV: 1012500 maxuV: 1012500, not supported by regulator [ 2.501617] cpu cpu0: _opp_add: OPP not supported by regulators (300000000) [ 2.509246] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1200000, not supported by regulator [ 2.519775] cpu cpu0: _opp_add: OPP not supported by regulators (600000000) [ 2.527313] core: _opp_supported_by_regulators: OPP minuV: 1325000 maxuV: 1325000, not supported by regulator [ 2.537750] cpu cpu0: _opp_add: OPP not supported by regulators (800000000) The patch fixes declaration of VDD1/2 regulators by adding proper voltage lists. Fixes: 498209445124 ("regulator: core: simplify return value on suported_voltage") Cc: stable(a)vger.kernel.org Signed-off-by: Andreas Kemnade <andreas(a)kemnade.info> --- resent because it was rejected by mailing lists, due to technical issues, sorry for the noise. changes in v2: using a proper voltage list instead of misusing the continuous flag subject was regulator: twl: mark vdd1/2 as continuous on twl4030 drivers/regulator/twl-regulator.c | 23 ++++++++++++++++++++--- 1 file changed, 20 insertions(+), 3 deletions(-) diff --git a/drivers/regulator/twl-regulator.c b/drivers/regulator/twl-regulator.c index 6fa15b2d6fb3..866b4dd01da9 100644 --- a/drivers/regulator/twl-regulator.c +++ b/drivers/regulator/twl-regulator.c @@ -359,6 +359,17 @@ static const u16 VINTANA2_VSEL_table[] = { 2500, 2750, }; +/* 600mV to 1450mV in 12.5 mV steps */ +static const struct regulator_linear_range VDD1_ranges[] = { + REGULATOR_LINEAR_RANGE(600000, 0, 68, 12500) +}; + +/* 600mV to 1450mV in 12.5 mV steps, everything above = 1500mV */ +static const struct regulator_linear_range VDD2_ranges[] = { + REGULATOR_LINEAR_RANGE(600000, 0, 68, 12500), + REGULATOR_LINEAR_RANGE(1500000, 69, 69, 12500) +}; + static int twl4030ldo_list_voltage(struct regulator_dev *rdev, unsigned index) { struct twlreg_info *info = rdev_get_drvdata(rdev); @@ -427,6 +438,8 @@ static int twl4030smps_get_voltage(struct regulator_dev *rdev) } static const struct regulator_ops twl4030smps_ops = { + .list_voltage = regulator_list_voltage_linear_range, + .set_voltage = twl4030smps_set_voltage, .get_voltage = twl4030smps_get_voltage, }; @@ -466,7 +479,8 @@ static const struct twlreg_info TWL4030_INFO_##label = { \ }, \ } -#define TWL4030_ADJUSTABLE_SMPS(label, offset, num, turnon_delay, remap_conf) \ +#define TWL4030_ADJUSTABLE_SMPS(label, offset, num, turnon_delay, remap_conf, \ + n_volt) \ static const struct twlreg_info TWL4030_INFO_##label = { \ .base = offset, \ .id = num, \ @@ -479,6 +493,9 @@ static const struct twlreg_info TWL4030_INFO_##label = { \ .owner = THIS_MODULE, \ .enable_time = turnon_delay, \ .of_map_mode = twl4030reg_map_mode, \ + .n_voltages = n_volt, \ + .n_linear_ranges = ARRAY_SIZE(label ## _ranges), \ + .linear_ranges = label ## _ranges, \ }, \ } @@ -518,8 +535,8 @@ TWL4030_ADJUSTABLE_LDO(VSIM, 0x37, 9, 100, 0x00); TWL4030_ADJUSTABLE_LDO(VDAC, 0x3b, 10, 100, 0x08); TWL4030_ADJUSTABLE_LDO(VINTANA2, 0x43, 12, 100, 0x08); TWL4030_ADJUSTABLE_LDO(VIO, 0x4b, 14, 1000, 0x08); -TWL4030_ADJUSTABLE_SMPS(VDD1, 0x55, 15, 1000, 0x08); -TWL4030_ADJUSTABLE_SMPS(VDD2, 0x63, 16, 1000, 0x08); +TWL4030_ADJUSTABLE_SMPS(VDD1, 0x55, 15, 1000, 0x08, 68); +TWL4030_ADJUSTABLE_SMPS(VDD2, 0x63, 16, 1000, 0x08, 69); /* VUSBCP is managed *only* by the USB subchip */ TWL4030_FIXED_LDO(VINTANA1, 0x3f, 1500, 11, 100, 0x08); TWL4030_FIXED_LDO(VINTDIG, 0x47, 1500, 13, 100, 0x08); -- 2.20.1

4 years, 7 months

3
5
0 0

[PATCH AUTOSEL 5.2 001/123] ASoC: simple_card_utils.h: care NULL dai at asoc_simple_debug_dai()

by Sasha Levin

From: Kuninori Morimoto <kuninori.morimoto.gx(a)renesas.com> [ Upstream commit 52db6685932e326ed607644ab7ebdae8c194adda ] props->xxx_dai might be NULL when DPCM. This patch cares it for debug. Fixes: commit 0580dde59438 ("ASoC: simple-card-utils: add asoc_simple_debug_info()") Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx(a)renesas.com> Link: https://lore.kernel.org/r/87o922gw4u.wl-kuninori.morimoto.gx@renesas.com Signed-off-by: Mark Brown <broonie(a)kernel.org> Signed-off-by: Sasha Levin <sashal(a)kernel.org> --- include/sound/simple_card_utils.h | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/include/sound/simple_card_utils.h b/include/sound/simple_card_utils.h index 3429888347e7c..b3609e4c46e0f 100644 --- a/include/sound/simple_card_utils.h +++ b/include/sound/simple_card_utils.h @@ -149,6 +149,10 @@ inline void asoc_simple_debug_dai(struct asoc_simple_priv *priv, { struct device *dev = simple_priv_to_dev(priv); + /* dai might be NULL */ + if (!dai) + return; + if (dai->name) dev_dbg(dev, "%s dai name = %s\n", name, dai->name); -- 2.20.1

4 years, 7 months

4
137
0 0

[PATCH] VMCI: Release resource if the work is already queued

by Nadav Amit

Francois reported that VMware balloon gets stuck after a balloon reset, when the VMCI doorbell is removed. A similar error can occur when the balloon driver is removed with the following splat: [ 1088.622000] INFO: task modprobe:3565 blocked for more than 120 seconds. [ 1088.622035] Tainted: G W 5.2.0 #4 [ 1088.622087] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1088.622205] modprobe D 0 3565 1450 0x00000000 [ 1088.622210] Call Trace: [ 1088.622246] __schedule+0x2a8/0x690 [ 1088.622248] schedule+0x2d/0x90 [ 1088.622250] schedule_timeout+0x1d3/0x2f0 [ 1088.622252] wait_for_completion+0xba/0x140 [ 1088.622320] ? wake_up_q+0x80/0x80 [ 1088.622370] vmci_resource_remove+0xb9/0xc0 [vmw_vmci] [ 1088.622373] vmci_doorbell_destroy+0x9e/0xd0 [vmw_vmci] [ 1088.622379] vmballoon_vmci_cleanup+0x6e/0xf0 [vmw_balloon] [ 1088.622381] vmballoon_exit+0x18/0xcc8 [vmw_balloon] [ 1088.622394] __x64_sys_delete_module+0x146/0x280 [ 1088.622408] do_syscall_64+0x5a/0x130 [ 1088.622410] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 1088.622415] RIP: 0033:0x7f54f62791b7 [ 1088.622421] Code: Bad RIP value. [ 1088.622421] RSP: 002b:00007fff2a949008 EFLAGS: 00000206 ORIG_RAX: 00000000000000b0 [ 1088.622426] RAX: ffffffffffffffda RBX: 000055dff8b55d00 RCX: 00007f54f62791b7 [ 1088.622426] RDX: 0000000000000000 RSI: 0000000000000800 RDI: 000055dff8b55d68 [ 1088.622427] RBP: 000055dff8b55d00 R08: 00007fff2a947fb1 R09: 0000000000000000 [ 1088.622427] R10: 00007f54f62f5cc0 R11: 0000000000000206 R12: 000055dff8b55d68 [ 1088.622428] R13: 0000000000000001 R14: 000055dff8b55d68 R15: 00007fff2a94a3f0 The cause for the bug is that when the "delayed" doorbell is invoked, it takes a reference on the doorbell entry and schedules work that is supposed to run the appropriate code and drop the doorbell entry reference. The code ignores the fact that if the work is already queued, it will not be scheduled to run one more time. As a result one of the references would not be dropped. When the code waits for the reference to get to zero, during balloon reset or module removal, it gets stuck. Fix it. Drop the reference if schedule_work() indicates that the work is already queued. Note that this bug got more apparent (or apparent at all) due to commit ce664331b248 ("vmw_balloon: VMCI_DOORBELL_SET does not check status"). Fixes: 83e2ec765be03 ("VMCI: doorbell implementation.") Reported-by: Francois Rigault <rigault.francois(a)gmail.com> Cc: Jorgen Hansen <jhansen(a)vmware.com> Cc: Adit Ranadive <aditr(a)vmware.com> Cc: Alexios Zavras <alexios.zavras(a)intel.com> Cc: Vishnu DASA <vdasa(a)vmware.com> Cc: stable(a)vger.kernel.org Signed-off-by: Nadav Amit <namit(a)vmware.com> --- drivers/misc/vmw_vmci/vmci_doorbell.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/misc/vmw_vmci/vmci_doorbell.c b/drivers/misc/vmw_vmci/vmci_doorbell.c index bad89b6e0802..345addd9306d 100644 --- a/drivers/misc/vmw_vmci/vmci_doorbell.c +++ b/drivers/misc/vmw_vmci/vmci_doorbell.c @@ -310,7 +310,8 @@ int vmci_dbell_host_context_notify(u32 src_cid, struct vmci_handle handle) entry = container_of(resource, struct dbell_entry, resource); if (entry->run_delayed) { - schedule_work(&entry->work); + if (!schedule_work(&entry->work)) + vmci_resource_put(resource); } else { entry->notify_cb(entry->client_data); vmci_resource_put(resource); @@ -361,7 +362,8 @@ static void dbell_fire_entries(u32 notify_idx) atomic_read(&dbell->active) == 1) { if (dbell->run_delayed) { vmci_resource_get(&dbell->resource); - schedule_work(&dbell->work); + if (!schedule_work(&dbell->work)) + vmci_resource_put(&dbell->resource); } else { dbell->notify_cb(dbell->client_data); } -- 2.19.1

4 years, 7 months

3
4
0 0

FAILED: patch "[PATCH] mm/zsmalloc.c: fix race condition in zs_destroy_pool" failed to apply to 4.9-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 4.9-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. thanks, greg k-h ------------------ original commit in Linus's tree ------------------ >From 701d678599d0c1623aaf4139c03eea260a75b027 Mon Sep 17 00:00:00 2001 From: Henry Burns <henryburns(a)google.com> Date: Sat, 24 Aug 2019 17:55:06 -0700 Subject: [PATCH] mm/zsmalloc.c: fix race condition in zs_destroy_pool In zs_destroy_pool() we call flush_work(&pool->free_work). However, we have no guarantee that migration isn't happening in the background at that time. Since migration can't directly free pages, it relies on free_work being scheduled to free the pages. But there's nothing preventing an in-progress migrate from queuing the work *after* zs_unregister_migration() has called flush_work(). Which would mean pages still pointing at the inode when we free it. Since we know at destroy time all objects should be free, no new migrations can come in (since zs_page_isolate() fails for fully-free zspages). This means it is sufficient to track a "# isolated zspages" count by class, and have the destroy logic ensure all such pages have drained before proceeding. Keeping that state under the class spinlock keeps the logic straightforward. In this case a memory leak could lead to an eventual crash if compaction hits the leaked page. This crash would only occur if people are changing their zswap backend at runtime (which eventually starts destruction). Link: http://lkml.kernel.org/r/20190809181751.219326-2-henryburns@google.com Fixes: 48b4800a1c6a ("zsmalloc: page migration support") Signed-off-by: Henry Burns <henryburns(a)google.com> Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky(a)gmail.com> Cc: Henry Burns <henrywolfeburns(a)gmail.com> Cc: Minchan Kim <minchan(a)kernel.org> Cc: Shakeel Butt <shakeelb(a)google.com> Cc: Jonathan Adams <jwadams(a)google.com> Cc: <stable(a)vger.kernel.org> Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds(a)linux-foundation.org> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c index 5105b9b66653..08def3a0d200 100644 --- a/mm/zsmalloc.c +++ b/mm/zsmalloc.c @@ -54,6 +54,7 @@ #include <linux/mount.h> #include <linux/pseudo_fs.h> #include <linux/migrate.h> +#include <linux/wait.h> #include <linux/pagemap.h> #include <linux/fs.h> @@ -268,6 +269,10 @@ struct zs_pool { #ifdef CONFIG_COMPACTION struct inode *inode; struct work_struct free_work; + /* A wait queue for when migration races with async_free_zspage() */ + struct wait_queue_head migration_wait; + atomic_long_t isolated_pages; + bool destroying; #endif }; @@ -1874,6 +1879,19 @@ static void putback_zspage_deferred(struct zs_pool *pool, } +static inline void zs_pool_dec_isolated(struct zs_pool *pool) +{ + VM_BUG_ON(atomic_long_read(&pool->isolated_pages) <= 0); + atomic_long_dec(&pool->isolated_pages); + /* + * There's no possibility of racing, since wait_for_isolated_drain() + * checks the isolated count under &class->lock after enqueuing + * on migration_wait. + */ + if (atomic_long_read(&pool->isolated_pages) == 0 && pool->destroying) + wake_up_all(&pool->migration_wait); +} + static void replace_sub_page(struct size_class *class, struct zspage *zspage, struct page *newpage, struct page *oldpage) { @@ -1943,6 +1961,7 @@ static bool zs_page_isolate(struct page *page, isolate_mode_t mode) */ if (!list_empty(&zspage->list) && !is_zspage_isolated(zspage)) { get_zspage_mapping(zspage, &class_idx, &fullness); + atomic_long_inc(&pool->isolated_pages); remove_zspage(class, zspage, fullness); } @@ -2042,8 +2061,16 @@ static int zs_page_migrate(struct address_space *mapping, struct page *newpage, * Page migration is done so let's putback isolated zspage to * the list if @page is final isolated subpage in the zspage. */ - if (!is_zspage_isolated(zspage)) + if (!is_zspage_isolated(zspage)) { + /* + * We cannot race with zs_destroy_pool() here because we wait + * for isolation to hit zero before we start destroying. + * Also, we ensure that everyone can see pool->destroying before + * we start waiting. + */ putback_zspage_deferred(pool, class, zspage); + zs_pool_dec_isolated(pool); + } reset_page(page); put_page(page); @@ -2094,8 +2121,8 @@ static void zs_page_putback(struct page *page) * so let's defer. */ putback_zspage_deferred(pool, class, zspage); + zs_pool_dec_isolated(pool); } - spin_unlock(&class->lock); } @@ -2118,8 +2145,36 @@ static int zs_register_migration(struct zs_pool *pool) return 0; } +static bool pool_isolated_are_drained(struct zs_pool *pool) +{ + return atomic_long_read(&pool->isolated_pages) == 0; +} + +/* Function for resolving migration */ +static void wait_for_isolated_drain(struct zs_pool *pool) +{ + + /* + * We're in the process of destroying the pool, so there are no + * active allocations. zs_page_isolate() fails for completely free + * zspages, so we need only wait for the zs_pool's isolated + * count to hit zero. + */ + wait_event(pool->migration_wait, + pool_isolated_are_drained(pool)); +} + static void zs_unregister_migration(struct zs_pool *pool) { + pool->destroying = true; + /* + * We need a memory barrier here to ensure global visibility of + * pool->destroying. Thus pool->isolated pages will either be 0 in which + * case we don't care, or it will be > 0 and pool->destroying will + * ensure that we wake up once isolation hits 0. + */ + smp_mb(); + wait_for_isolated_drain(pool); /* This can block */ flush_work(&pool->free_work); iput(pool->inode); } @@ -2357,6 +2412,8 @@ struct zs_pool *zs_create_pool(const char *name) if (!pool->name) goto err; + init_waitqueue_head(&pool->migration_wait); + if (create_cache(pool)) goto err;

4 years, 7 months

3
3
0 0

FAILED: patch "[PATCH] HID: logitech-hidpp: remove support for the G700 over USB" failed to apply to 5.2-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 5.2-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. thanks, greg k-h ------------------ original commit in Linus's tree ------------------ >From a3384b8d9f63cc042711293bb97bdc92dca0391d Mon Sep 17 00:00:00 2001 From: Benjamin Tissoires <benjamin.tissoires(a)redhat.com> Date: Tue, 13 Aug 2019 15:38:07 +0200 Subject: [PATCH] HID: logitech-hidpp: remove support for the G700 over USB MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The G700 suffers from the same issue than the G502: when plugging it in, the driver tries to contact it but it fails. This timeout is problematic as it introduce a delay in the boot, and having only the mouse event node means that the hardware macros keys can not be relayed to the userspace. Link: https://github.com/libratbag/libratbag/issues/797 Fixes: 91cf9a98ae41 ("HID: logitech-hidpp: make .probe usbhid capable") Cc: stable(a)vger.kernel.org # v5.2 Reviewed-by: Filipe Laíns <lains(a)archlinux.org> Signed-off-by: Benjamin Tissoires <benjamin.tissoires(a)redhat.com> diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c index 343052b117a9..0179f7ed77e5 100644 --- a/drivers/hid/hid-logitech-hidpp.c +++ b/drivers/hid/hid-logitech-hidpp.c @@ -3751,8 +3751,6 @@ static const struct hid_device_id hidpp_devices[] = { { /* Logitech G403 Wireless Gaming Mouse over USB */ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, 0xC082) }, - { /* Logitech G700 Gaming Mouse over USB */ - HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, 0xC06B) }, { /* Logitech G703 Gaming Mouse over USB */ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, 0xC087) }, { /* Logitech G703 Hero Gaming Mouse over USB */

4 years, 7 months

2
1
0 0

kvm: x86: skip populating logical dest map if apic is not sw enabled

by Bandan Das

Please consider commit b14c876b994f208b6b95c222056e1deb0a45de0e Author: Radim Krcmar <rkrcmar(a)redhat.com> Date: Tue Aug 13 23:37:37 2019 -0400 kvm: x86: skip populating logical dest map if apic is not sw enabled This fixes 1e08ec4a130e2745d96df169e67c58df98a07311 that was introduced in v3.7. The bug is that the KVM lapic is not considering whether the guest apic is enabled before populating the apic in the logical destination table. Thanks, Bandan

4 years, 7 months

2
1
0 0

[PATCH] power/supply: ingenic-battery: Don't change scale if there's only one

by Paul Cercueil

The ADC in the JZ4740 can work either in high-precision mode with a 2.5V range, or in low-precision mode with a 7.5V range. The code in place in this driver will select the proper scale according to the maximum voltage of the battery. The JZ4770 however only has one mode, with a 6.6V range. If only one scale is available, there's no need to change it (and nothing to change it to), and trying to do so will fail with -EINVAL. Fixes commit fb24ccfbe1e0 ("power: supply: add Ingenic JZ47xx battery driver.") Signed-off-by: Paul Cercueil <paul(a)crapouillou.net> Cc: stable(a)vger.kernel.org --- drivers/power/supply/ingenic-battery.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drivers/power/supply/ingenic-battery.c b/drivers/power/supply/ingenic-battery.c index 35816d4b3012..5a53057b4f64 100644 --- a/drivers/power/supply/ingenic-battery.c +++ b/drivers/power/supply/ingenic-battery.c @@ -80,6 +80,10 @@ static int ingenic_battery_set_scale(struct ingenic_battery *bat) if (ret != IIO_AVAIL_LIST || scale_type != IIO_VAL_FRACTIONAL_LOG2) return -EINVAL; + /* Only one (fractional) entry - nothing to change */ + if (scale_len == 2) + return 0; + max_mV = bat->info.voltage_max_design_uv / 1000; for (i = 0; i < scale_len; i += 2) { -- 2.21.0.593.g511ec345e18

4 years, 7 months

2
1
0 0

Kernel 5.2.11 dpes not compile

by François Valenduc

The following patch causes a build failure: Author: Henry Burns <henryburns(a)google.com> Date: Sat Aug 24 17:55:06 2019 -0700 mm/zsmalloc.c: fix race condition in zs_destroy_pool I get this error: CALL scripts/checksyscalls.sh CALL scripts/atomic/check-atomics.sh DESCEND objtool CHK include/generated/compile.h CC mm/zsmalloc.o In file included from ./include/linux/mmzone.h:10:0, from ./include/linux/gfp.h:6, from ./include/linux/umh.h:4, from ./include/linux/kmod.h:9, from ./include/linux/module.h:13, from mm/zsmalloc.c:33: mm/zsmalloc.c: In function ‘zs_create_pool’: mm/zsmalloc.c:2435:27: error: ‘struct zs_pool’ has no member named ‘migration_wait’ init_waitqueue_head(&pool->migration_wait); ^ ./include/linux/wait.h:67:26: note: in definition of macro ‘init_waitqueue_head’ __init_waitqueue_head((wq_head), #wq_head, &__key); \ ^~~~~~~ scripts/Makefile.build:278: recipe for target 'mm/zsmalloc.o' failed make[1]: *** [mm/zsmalloc.o] Error 1 Makefile:1073: recipe for target 'mm' failed You can find my configuration file attached. Does anybody have any idea about this ? Thanks in advance, François Valenduc

4 years, 7 months

4
5
0 0

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror August 2019