- 14 Aug, 2023 7 commits
-
-
Arnd Bergmann authored
Merge tag 'ti-driver-soc-for-v6.6' of https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux into soc/drivers TI SoC driver updates for v6.6 - Generic fixups: Explicitly include correct DT include. - omap_prm: Cosmetic fixups for using devm_ api for ioremap_resource - ti_sci: Documentation fixups, Using system_state to determine if polling is needed. - k3-ringcc: Documentation fixups, cleanup of log messages, using devm_ to handle ioremap_resource. - k3-socinfo: Add AM62PX detection. * tag 'ti-driver-soc-for-v6.6' of https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux: soc: ti: k3-socinfo.c: Add JTAG ID for AM62PX soc: ti: Use devm_platform_ioremap_resource_byname simplify logic soc: ti: k3-ringacc: remove non-fatal probe deferral log soc: ti: Explicitly include correct DT includes soc: ti: omap-prm: Use devm_platform_get_and_ioremap_resource() soc: ti: k3-ringacc: Fixup documentation errors firmware: ti_sci: Fixup documentation errors firmware: ti_sci: Use system_state to determine polling Link: https://lore.kernel.org/r/20230814160633.my3xbk5k2pxkvjyi@degreaseSigned-off-by:
Arnd Bergmann <arnd@arndb.de>
-
Arnd Bergmann authored
Merge tag 'oxnas-final-for-6.6' of https://git.kernel.org/pub/scm/linux/kernel/git/narmstrong/linux-oxnas into soc/drivers Final OXNAS removal PR for v6.6: - Remove irq-versatile-fpga compatible entry - Mark irq-versatile-fpga oxnas compatible as deprecated - Remove OXNAS maintainers entry * tag 'oxnas-final-for-6.6' of https://git.kernel.org/pub/scm/linux/kernel/git/narmstrong/linux-oxnas: MAINTAINERS: remove OXNAS entry dt-bindings: interrupt-controller: arm,versatile-fpga-irq: mark oxnas compatible as deprecated irqchip: irq-versatile-fpga: remove obsolete oxnas compatible Link: https://lore.kernel.org/r/3f91bb89-bf7b-d967-a302-2a8e1b0c3b01@linaro.orgSigned-off-by:
-
Arnd Bergmann authored
Merge tag 'imx-drivers-6.6' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into soc/drivers i.MX drivers update for 6.6: - A series from NXP i.MX developers (Peng Fan, etc.) to update imx-scu and imx-scu-irq firmware drivers. - Add dedicated lockdep class for nested genpd locks to fix a lockdep warning in imx93-blk-ctrl driver. - A change from Rob to explicitly include correct DT headers for i.MX SoC drivers. - Use devm_platform_ioremap_resource() in imx-weim bus driver. * tag 'imx-drivers-6.6' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux: firmware: imx: scu-irq: support identifying SCU wakeup source from sysfs firmware: imx: scu-irq: enlarge the IMX_SC_IRQ_NUM_GROUP firmware: imx: scu-irq: add imx_scu_irq_get_status firmware: imx: scu-irq: fix RCU complaint after M4 partition reset firmware: imx: scu: use EOPNOTSUPP firmware: imx: scu: use soc name for soc_id firmware: imx: scu: increase RPC timeout firmware: imx: scu: change init level to subsys_initcall_sync soc: imx: Explicitly include correct DT includes bus: imx-weim: use devm_platform_ioremap_resource soc: imx: imx93-blk-ctrl: Add dedicated lockdep class for nested genpd locks Link: https://lore.kernel.org/r/20230813133354.847010-1-shawnguo@kernel.orgSigned-off-by:
-
Arnd Bergmann authored
When the mailbox subsystem is disabled, the driver fails to link, so add an explicit dependency. Some other drivers use 'select' here, but the dependency seems more logical and more common. Fixes: 886bdf9c ("soc: hisilicon: Support HCCS driver on Kunpeng SoC") Signed-off-by:
-
Neil Armstrong authored
Due to lack of maintenance and stall of development for a few years now, and since no new features will ever be added upstream, remove MAINTAINERS entry for OXNAS files. Acked-by:
Linus Walleij <linus.walleij@linaro.org> Acked-by:
Daniel Golle <daniel@makrotopia.org> Acked-by:
Andy Shevchenko <andy@kernel.org> Link: https://lore.kernel.org/r/20230814-topic-oxnas-upstream-remove-v3-3-e2ba579a49d3@linaro.orgSigned-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
Neil Armstrong authored
Due to lack of maintenance and stall of development for a few years now, and since no new features will ever be added upstream, mark the OX810 and OX820 IRQ compatible as deprecated. Acked-by:
Conor Dooley <conor.dooley@microchip.com> Acked-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://lore.kernel.org/r/20230814-topic-oxnas-upstream-remove-v3-2-e2ba579a49d3@linaro.orgSigned-off-by:
-
Neil Armstrong authored
Due to lack of maintenance and stall of development for a few years now, and since no new features will ever be added upstream, remove support for OX810 and OX820 IRQ controller. Acked-by:
Marc Zyngier <maz@kernel.org> Acked-by:
-
- 12 Aug, 2023 10 commits
-
-
Arnd Bergmann authored
Printing a size_t using the %lu format string causes a warning on architectures that define the type as 'unsigned int': In file included from include/linux/device.h:15, from include/linux/acpi.h:14, from drivers/soc/hisilicon/kunpeng_hccs.c:25: drivers/soc/hisilicon/kunpeng_hccs.c: In function 'hccs_get_bd_info': drivers/soc/hisilicon/kunpeng_hccs.c:441:25: error: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'size_t' {aka 'unsigned int'} [-Werror=format=] Use the correct %zu format instead. Fixes: 886bdf9c ("soc: hisilicon: Support HCCS driver on Kunpeng SoC") Signed-off-by: -
https://github.com/hisilicon/linux-hisiArnd Bergmann authored
HiSilicon driver updates for v6.6 - Add HCCS driver for HiSilicon Kunpeng SoC and document the sysfs description * tag 'hisi-drivers-for-6.6' of https://github.com/hisilicon/linux-hisi: doc: soc: hisilicon: Add Kunpeng HCCS driver documentation soc: hisilicon: add sysfs entry to query information of HCCS soc: hisilicon: Support HCCS driver on Kunpeng SoC Link: https://lore.kernel.org/r/64D605DE.2070303@hisilicon.comSigned-off-by:
-
Arnd Bergmann authored
Merge tag 'samsung-drivers-6.6' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux into soc/drivers Samsung SoC driver changes for v6.6 Minor cleanup of headers and maintainer entries for Samsung SoC drivers. * tag 'samsung-drivers-6.6' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux: MAINTAINERS: mfd: Un-support Maxim and Samsung PMIC drivers MAINTAINERS: samsung: Un-support cpuidle and clock drivers soc: samsung: Explicitly include correct DT includes Link: https://lore.kernel.org/r/20230810151250.220202-1-krzysztof.kozlowski@linaro.orgSigned-off-by:
-
git://git.pengutronix.de/pza/linuxArnd Bergmann authored
Reset controller updates for v6.6 Clean up DT includes and remove unneeded platform_set_drvdata() calls across reset drivers, add support for the Versal NET platform to the zynqmp driver, and let the hisilicon driver use dev_err_probe(). * tag 'reset-for-v6.6' of git://git.pengutronix.de/pza/linux: reset: ti: syscon: remove unneeded call to platform_set_drvdata() reset: zynqmp: removed unneeded call to platform_set_drvdata() reset: zynq: remove unneeded call to platfrom_set_drvdata() reset: uniphier-glue: remove unneeded call to platform_set_drvdata() reset: npcm: remove unneeded call to platform_set_drvdata() reset: meson: remove unneeded call to platform_set_drvdata() reset: lpc18xx: remove unneeded call to platform_set_drvdata() reset: lantiq: remove unneeded call to platform_set_drvdata() reset: bcm6345: remove unneeded call to platform_set_drvdata() reset: ath79: remove unneeded call to platform_set_drvdata() reset: hisilicon: Use dev_err_probe instead of dev_err reset: reset-zynqmp: add support for Versal NET platform dt-bindings: reset: Updated binding for Versal-NET reset driver reset: Explicitly include correct DT includes Link: https://lore.kernel.org/r/20230808145950.3057250-1-p.zabel@pengutronix.deSigned-off-by:
-
Arnd Bergmann authored
Merge tag 'sunxi-drivers-for-6.6-1' of https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux into soc/drivers - simplify code in sunxi-rsb - fix includes in sunxi_sram * tag 'sunxi-drivers-for-6.6-1' of https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux: soc: sunxi: Explicitly include correct DT includes bus: sunxi-rsb: Convert to devm_platform_ioremap_resource() Link: https://lore.kernel.org/r/20230806180650.GA127142@jernej-laptopSigned-off-by:
-
Arnd Bergmann authored
Merge tag 'amlogic-drivers-for-v6.6' of https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux into soc/drivers Amlogic drivers changes for v6.6: - Add C3 Power Domains - Explicitly include correct DT includes in Amlogic SoC drivers - fix to avoid potential NULL pointer dereference in meson_sm - Merge of genpd-v6.5-rc1-1 to move genpd amlogic drivers * tag 'amlogic-drivers-for-v6.6' of https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux: firmware: meson_sm: fix to avoid potential NULL pointer dereference soc: amlogic: Explicitly include correct DT includes soc: c3: Add support for power domains controller dt-bindings: power: add Amlogic C3 power domains soc: amlogic: use name instead of index as criterion Link: https://lore.kernel.org/r/77e328b5-0d47-36e8-f62d-c745df06fb87@linaro.orgSigned-off-by:
-
Arnd Bergmann authored
Merge tag 'scmi-updates-6.6' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux into soc/drivers Arm SCMI updates for v6.6 The main addition this time is the support for SCMI v3.2 perf level indexing mode. SCMI v3.2 adds support for hardware which works on performance indices, instead of levels. Certain platforms use indices to identify performance levels. Level Indexing Mode is used to describe such platform behavior. All commands which utilize performance level as a parameter need to specify the corresponding level index instead of the performance level when Level Indexing Mode is used. While at it, these changes also include hardening of all the internal accesses to the performance domain information. * tag 'scmi-updates-6.6' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux: firmware: arm_scmi: Add v3.2 perf level indexing mode support firmware: arm_scmi: Harden perf domain info access Link: https://lore.kernel.org/r/20230804123231.3258141-1-sudeep.holla@arm.comSigned-off-by:
-
Arnd Bergmann authored
Merge tag 'vexpress-updates-6.6' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux into soc/drivers Arm Vexpress updates for v6.6 Couple of minor updates: Code simplification in the vexpress config bus driver with the use of devm_platform_ioremap_resource() and simplification of Arm Vexpress platform and related drivers entries in MAINTAINERS file. * tag 'vexpress-updates-6.6' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux: MAINTAINERS: Simplify entries for Arm Vexpress platform and related drivers bus: vexpress-config: Convert to devm_platform_ioremap_resource() Link: https://lore.kernel.org/r/20230804123214.3258032-1-sudeep.holla@arm.comSigned-off-by:
-
https://github.com/Xilinx/linux-xlnxArnd Bergmann authored
arm64: ZynqMP SoC changes for 6.6 - Cleanup remove callback in event driver - Explicitly include correct DT header in power driver - Fix logic around irq = 0 in power driver * tag 'zynqmp-soc-for-6.6' of https://github.com/Xilinx/linux-xlnx: soc: xilinx: Do not check for 0 return after calling platform_get_irq() soc: xilinx: Explicitly include correct DT includes driver: soc: xilinx: Convert to platform remove callback returning void Link: https://lore.kernel.org/r/399efa45-df0a-4ec7-e25c-774bb8bf6fb4@monstr.euSigned-off-by:
-
Arnd Bergmann authored
Merge tag 'tegra-for-6.6-soc' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into soc/drivers soc/tegra: Changes for v6.6-rc1 This contains a selection of minor cleanups. * tag 'tegra-for-6.6-soc' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux: soc/tegra: cbb: Remove unnecessary print function dev_err() soc/tegra: fuse: Sort includes alphabetically bus: tegra-gmi: Convert to devm_platform_ioremap_resource() soc/tegra: fuse: Use devm_platform_get_and_ioremap_resource() soc/tegra: Explicitly include correct DT includes Link: https://lore.kernel.org/r/20230728094129.3587109-1-thierry.reding@gmail.comSigned-off-by:
-
- 11 Aug, 2023 9 commits
-
-
Vignesh Raghavendra authored
This adds JTAG ID info for the AM62PX so as to enable SoC detection in kernel. Signed-off-by:
Vignesh Raghavendra <vigneshr@ti.com> Reviewed-by:
Praneeth Bajjuri <praneeth@ti.com> Link: https://lore.kernel.org/r/20230811170127.250733-1-vigneshr@ti.comSigned-off-by:
Nishanth Menon <nm@ti.com>
-
Ranjani Vaidyanathan authored
Record SCU wakeup interrupt in /sys/power/pm_wakeup_irq The user can further identify the exact wakeup source by using the following interface: cat /sys/firmware/scu_wakeup_source/wakeup_src The above will print the wake groups and the irqs that could have contributed to waking up the kernel. For example if ON/OFF button was the wakeup source: cat /sys/firmware/scu_wakeup_source/wakeup_src Wakeup source group = 3, irq = 0x1 The user can refer to the SCFW API documentation to identify all the wake groups and irqs. Signed-off-by:
Ranjani Vaidyanathan <ranjani.vaidyanathan@nxp.com> Signed-off-by:
Peng Fan <peng.fan@nxp.com> Signed-off-by:
Shawn Guo <shawnguo@kernel.org>
-
Peng Fan authored
Per SCFW update, update the IMX_SC_IRQ_NUM_GROUP to 9. Signed-off-by:
-
Peng Fan authored
Extract the scu irq get status code from imx_scu_irq_work_handler and make into a new function imx_scu_irq_get_status which could be used by others, such as SECO. Signed-off-by:
-
Robin Gong authored
Use blocking_notifier_chain instead of atomic_notifier_chain, otherwise there will be RCU complaint, because unregister/register_virtio_device() will issue mbox message. mbox_send_message() is blocking again after received M4 partition reset. Actually, no need atomic notifier for scu irq notification since this notifier is called in worker instead of interrupt handler. [ 389.706645] i2c-rpmsg virtio0.rpmsg-i2c-channel.-1.2: i2c rpmsg driver is removed [ 389.767362] Wait for remote ready timeout, use first_notify. [ 389.774084] ------------[ cut here ]------------ [ 389.778729] WARNING: CPU: 0 PID: 397 at kernel/rcu/tree_plugin.h:293 rcu_note_context_switch+0x34/0x338 [ 389.788131] Modules linked in: [ 389.791195] CPU: 0 PID: 397 Comm: kworker/0:13 Not tainted 5.4.0-rc5-02977-g08f78722f07b #26 [ 389.799633] Hardware name: Freescale i.MX8DXL MEK (DT) [ 389.805481] Workqueue: events imx_scu_irq_work_handler Signed-off-by:
Robin Gong <yibin.gong@nxp.com> Reviewed-by:
Dong Aisheng <aisheng.dong@nxp.com> Signed-off-by:
-
Peng Fan authored
Per checkpatch.pl, "ENOTSUPP is not a SUSV4 error code, prefer EOPNOTSUPP" So use EOPNOTSUPP to replace ENOTSUPP. Signed-off-by:
-
Peng Fan authored
Same as soc-imx8m and soc-imx driver, use soc name for soc_id which is user friendly. Signed-off-by:
-
Dong Aisheng authored
When system loading is high, we can meet some command timeout issue occasionally, so increase the timeout to a safe value. Signed-off-by:
-
Dong Aisheng authored
Change firmware init level to subsys_initcall_sync to ensure it's probed before most devices to avoid unnecessary defer probe. Signed-off-by:
-
- 10 Aug, 2023 1 commit
-
-
Zhang Zekun authored
platform_get_resource_byname() and devm_ioremap_resource() can be replaced by devm_platform_ioremap_resource_byname(), which can simplify the code logic a bit, No functional change here. Signed-off-by:
Zhang Zekun <zhangzekun11@huawei.com> Reviewed-by:
Dhruva Gole <d-gole@ti.com> Link: https://lore.kernel.org/r/20230809081523.26196-1-zhangzekun11@huawei.comSigned-off-by:
-
- 08 Aug, 2023 13 commits
-
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Signed-off-by:
Andrei Coardos <aboutphysycs@gmail.com> Acked-by:
Andrew Davis <afd@ti.com> Reviewed-by:
Alexandru Ardelean <alex@shruggie.ro> Link: https://lore.kernel.org/r/20230807111534.12392-1-aboutphysycs@gmail.comSigned-off-by:
Philipp Zabel <p.zabel@pengutronix.de>
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Signed-off-by:
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Signed-off-by:
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Signed-off-by:
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Reviewed-by:
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Reviewed-by:
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Reviewed-by:
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Reviewed-by:
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Reviewed-by:
-
Andrei Coardos authored
This function call was found to be unnecessary as there is no equivalent platform_get_drvdata() call to access the private data of the driver. Also, the private data is defined in this driver, so there is no risk of it being accessed outside of this driver file. Reviewed-by:
-
Huisong Li authored
Document the sysfs attributes description provided by HCCS driver on Kunpeng SoC. Signed-off-by:
Huisong Li <lihuisong@huawei.com> Signed-off-by:
Wei Xu <xuwei5@hisilicon.com>
-
Huisong Li authored
This patch creates chip, die and port directory based on the actual hardware implementation of platform. Some sysfs entries under these directories are created to query the health status and port information of HCCS. Signed-off-by:
-
Huisong Li authored
The Huawei Cache Coherence System (HCCS) is a multi-chip interconnection bus protocol. This driver is aimed to support some features about HCCS on Kunpeng SoC, like, querying the health status of HCCS. This patch adds the probing of HCCS driver, and obtains all HCCS port information by the dimension of chip and die on platform. Signed-off-by:
-
