- Jul 19, 2024
-
-
Masatake YAMATO authored
Signed-off-by:
Masatake YAMATO <yamato@redhat.com> Signed-off-by:
Matthew Sakai <msakai@redhat.com> Signed-off-by:
Mikulas Patocka <mpatocka@redhat.com>
-
- Jul 16, 2024
-
-
Beau Belgrave authored
The user events trace subsystem uses the 0x2A/'*' code for ioctls. These are published via the uapi/linux/user_events.h header file. Add a line indicating user events as the owner of the 0x2A/'*' code and reserve the first 32 sequence numbers. Signed-off-by:
Beau Belgrave <beaub@linux.microsoft.com> Signed-off-by:
Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20240715181413.1157-1-beaub@linux.microsoft.com
-
Marc Ferland authored
Small typo. The device name in the example should be "foo-i2c.0" and not "foo-i2c.o". Signed-off-by:
Marc Ferland <marc.ferland@sonatest.com> Signed-off-by:
-
Jakub Kicinski authored
Multiple vendors seem to prefer taking discussions off list, and ask contributors to work with them privately rather than just send patches to the list. I'd imagine this is because it's hard to fit in time for random developers popping up with features to review into packed schedule. From what I've seen "work in private" usually means someone on the company side will be assigned to handle the interaction, possibly months later. In worst case, the person scheduled to help the contributor takes over and writes the code themselves. This is not how the community is supposed to work. Reviewed-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Reviewed-by:
Mark Brown <broonie@kernel.org> Reviewed-by:
Shuah Khan <skhan@linuxfoundation.org> Signed-off-by:
Jakub Kicinski <kuba@kernel.org> Signed-off-by:
-
Ilpo Järvinen authored
pmf.rst was removed by the commit 2fd66f7d ("platform/x86/amd/pmf: Remove update system state document") but the reference in the admin-guide index remained in place which triggers this warning: Documentation/admin-guide/index.rst:75: WARNING: toctree contains reference to nonexisting document 'admin-guide/pmf' Remove pmf also from the index to avoid the warning. Reported-by:
Stephen Rothwell <sfr@canb.auug.org.au> Acked-by:
Randy Dunlap <rdunlap@infradead.org> Link: https://lore.kernel.org/r/20240715104102.4615-1-ilpo.jarvinen@linux.intel.com Signed-off-by:
Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
-
- Jul 15, 2024
-
-
Asbjørn Sloth Tønnesen authored
Describe key-enc-flags and key-enc-flags-mask. These are defined similarly to key-flags and key-flags-mask. Suggested-by:
Asbjørn Sloth Tønnesen <ast@fiberby.net> Reviewed-by:
Donald Hunter <donald.hunter@gmail.com> Link: https://patch.msgid.link/20240713021911.1631517-11-ast@fiberby.net Signed-off-by:
-
Asbjørn Sloth Tønnesen authored
Define new TCA_FLOWER_KEY_FLAGS_* flags for use in struct flow_dissector_key_control, covering the same flags as currently exposed through TCA_FLOWER_KEY_ENC_FLAGS. Put the new flags under FLOW_DIS_F_*. The idea is that we can later, move the existing flags under FLOW_DIS_F_* as well. The ynl flag names have been taken from the RFC iproute2 patch. Signed-off-by:
-
Asbjørn Sloth Tønnesen authored
Describe the flower control flags, and use them for key-flags and key-flags-mask. The flag names have been taken from iproute2. Suggested-by:
-
Bartosz Golaszewski authored
Drop the inputs from the host and instead expect the Bluetooth node to consume the outputs of the internal PMU. This model is closer to reality than how we represent it now. Signed-off-by:
Bartosz Golaszewski <bartosz.golaszewski@linaro.org> Acked-by:
Rob Herring (Arm) <robh@kernel.org> Signed-off-by:
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
-
Rafał Miłecki authored
This helps validating DTS files. Introduced changes: 1. Dropped serial details from example 2. Added required example include Signed-off-by:
Rafał Miłecki <rafal@milecki.pl> Reviewed-by:
-
Bartosz Golaszewski authored
QCA6390 has a compatible listed in the bindings but is missing the regulators description. Add the missing supply property and list the required ones in the allOf section. Reviewed-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Signed-off-by:
-
Rob Herring (Arm) authored
It is possible to have thermal zones which don't have any trip points. These zones in effect simply represent a temperature sensor without any action associated with it. While the schema has always required a 'trips' node, users have existed for a long time without it. Update the schema to match reality. Signed-off-by:
Daniel Lezcano <daniel.lezcano@linaro.org>
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
Conor Dooley <conor.dooley@microchip.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Preferred indentation for DTS examples in the bindings is 4-space. It is also preferred not to have redundant/unused labels. No functional change Acked-by:
-
Krzysztof Kozlowski authored
Simplify few bindings which already reference thermal-sensor.yaml schema by dropping unneeded requiring of '#thermal-sensor-cells' and dropping assigned-clocks properties (core schema allows it if 'clocks' are there). Reviewed-by:
AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Reviewed-by:
Baolin Wang <baolin.wang@linux.alibaba.com> Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Reviewed-by:
Biju Das <biju.das.jz@bp.renesas.com> Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Reviewed-by:
Heiko Stuebner <heiko@sntech.de> Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Reviewed-by:
Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se> Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Reviewed-by:
Amit Kucheria <amitk@kernel.org> Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Reviewed-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Reviewed-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Acked-by:
Florian Fainelli <florian.fainelli@broadcom.com> Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and it requires '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it and bring the common definition of '#thermal-sensor-cells' property. Reviewed-by:
Vasily Khoruzhick <anarsoul@gmail.com> Acked-by:
Chen-Yu Tsai <wens@csie.org> Acked-by:
-
Krzysztof Kozlowski authored
Device is a thermal sensor and all in-tree DTS provide '#thermal-sensor-cells', so reference the thermal-sensor.yaml to simplify it, bring the common definition of '#thermal-sensor-cells' property and require it. Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Reviewed-by:
Guillaume LA ROQUE <glaroque@baylibre.com> Acked-by:
-
Krzysztof Kozlowski authored
All Samsung Exynos SoCs Thermal Management Units have only one sensor, so make '#thermal-sensor-cells' fixed at 0. Acked-by:
-
Krzysztof Kozlowski authored
Linux kernel uses thermal zone node name during registering thermal zones and has a hard-coded limit of 20 characters, including terminating NUL byte. The bindings expect node names to finish with '-thermal' which is eight bytes long, thus we have only 11 characters for the reset of the node name (thus 10 for the pattern after leading fixed character). Reported-by:
-
Abel Vesa authored
Document the Temperature Sensor (TSENS) on the X1E80100 Platform. Reviewed-by:
Krzysztof Kozlowski <krzk@kernel.org> Signed-off-by:
Abel Vesa <abel.vesa@linaro.org> Reviewed-by:
-
Abdulrasaq Lawani authored
Convert the hisilicon SoCs tsensor txt bindings to dt-schema Signed-off-by:
Abdulrasaq Lawani <abdulrasaqolawani@gmail.com> Reviewed-by:
-
Stanislav Jakubek authored
Convert the Spreadtrum SC9860 timer bindings to DT schema. Changes during conversion: - rename file to match compatible - add sprd,sc9860-suspend-timer which was previously undocumented - minor grammar fix in description Signed-off-by:
Stanislav Jakubek <stano.jakubek@gmail.com> Reviewed-by:
-
- Jul 14, 2024
-
-
Kamil Horák (2N) authored
There is a group of PHY chips supporting BroadR-Reach link modes in a manner allowing for more or less identical register usage as standard Clause 22 PHY. These chips support standard Ethernet link modes as well, however, the circuitry is mutually exclusive and cannot be auto-detected. The link modes in question are 100Base-T1 as defined in IEEE802.3bw, based on Broadcom's 1BR-100 link mode, and newly defined 10Base-T1BRR (1BR-10 in Broadcom documents). Add optional brr-mode flag to switch the PHY to BroadR-Reach mode. Signed-off-by:
Kamil Horák (2N) <kamilh@axis.com> Reviewed-by:
-
Neeraj Sanjay Kale authored
This adds a new optional device tree property called firware-name. Signed-off-by:
Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com> Reviewed-by:
-
