- Nov 16, 2023
-
-
Robert Beckett authored
Add bindings for the wave5 chips&media codec driver Signed-off-by:
Robert Beckett <bob.beckett@collabora.com> Signed-off-by:
Dafna Hirschfeld <dafna.hirschfeld@collabora.com> Signed-off-by:
Sebastian Fricke <sebastian.fricke@collabora.com> Reviewed-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Hans Verkuil <hverkuil-cisco@xs4all.nl>
-
Jack Zhu authored
Add starfive_camss.rst file that documents the Starfive Camera Subsystem driver which is used for handing image sensor data. Signed-off-by:
Jack Zhu <jack.zhu@starfivetech.com> Signed-off-by:
-
Jack Zhu authored
Add the bindings documentation for Starfive JH7110 Camera Subsystem which is used for handing image sensor data. Reviewed-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
-
- Nov 10, 2023
-
-
Masami Hiramatsu (Google) authored
Add a note about the argument and return value accecss will be best effort. Depending on the type, it will be passed via stack or a pair of the registers, but $argN and $retval only support the single register access. Link: https://lore.kernel.org/all/169556269377.146934.14829235476649685954.stgit@devnote2/ Suggested-by:
Alexei Starovoitov <alexei.starovoitov@gmail.com> Signed-off-by:
Masami Hiramatsu (Google) <mhiramat@kernel.org>
-
- Nov 07, 2023
-
-
Evan Green authored
In /proc/cpuinfo, most of the information we show for each processor is specific to that hart: marchid, mvendorid, mimpid, processor, hart, compatible, and the mmu size. But the ISA string gets filtered through a lowest common denominator mask, so that if one CPU is missing an ISA extension, no CPUs will show it. Now that we track the ISA extensions for each hart, let's report ISA extension info accurately per-hart in /proc/cpuinfo. We cannot change the "isa:" line, as usermode may be relying on that line to show only the common set of extensions supported across all harts. Add a new "hart isa" line instead, which reports the true set of extensions for that hart. Signed-off-by:
Evan Green <evan@rivosinc.com> Reviewed-by:
Andrew Jones <ajones@ventanamicro.com> Reviewed-by:
Conor Dooley <conor.dooley@microchip.com> Link: https://lore.kernel.org/r/20231106232439.3176268-1-evan@rivosinc.com Signed-off-by:
Palmer Dabbelt <palmer@rivosinc.com>
-
Marielle Novastrider authored
Small typos in register and field names. Signed-off-by:
Marielle Novastrider <marielle@novastrider.com> Acked-by:
Will Deacon <will@kernel.org> Link: https://lore.kernel.org/r/20231031200838.55569-1-marielle@novastrider.com Signed-off-by:
Catalin Marinas <catalin.marinas@arm.com>
-
- Nov 04, 2023
-
-
Neil Armstrong authored
Document the Inter-Processor Communication Controller on the SM8650 Platform. Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org> Reviewed-by:
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Signed-off-by:
Jassi Brar <jaswinder.singh@linaro.org>
-
- Nov 02, 2023
-
-
Gerd Bayer authored
Since commit 833bac7e ("net/smc: Fix setsockopt and sysctl to specify same buffer size again") the SMC protocol uses its own default values for the smc.rmem and smc.wmem sysctl variables which are no longer derived from the TCP IPv4 buffer sizes. Fixup the kernel documentation to reflect this change, too. Fixes: 833bac7e ("net/smc: Fix setsockopt and sysctl to specify same buffer size again") Signed-off-by:
Gerd Bayer <gbayer@linux.ibm.com> Reviewed-by:
Wenjia Zhang <wenjia@linux.ibm.com> Reviewed-by:
Dust Li <dust.li@linux.alibaba.com> Link: https://lore.kernel.org/r/20231030170343.748097-1-gbayer@linux.ibm.com Signed-off-by:
Paolo Abeni <pabeni@redhat.com>
-
Dave Marchevsky authored
BPF kfuncs are meant to be called from BPF programs. Accordingly, most kfuncs are not called from anywhere in the kernel, which the -Wmissing-prototypes warning is unhappy about. We've peppered __diag_ignore_all("-Wmissing-prototypes", ... everywhere kfuncs are defined in the codebase to suppress this warning. This patch adds two macros meant to bound one or many kfunc definitions. All existing kfunc definitions which use these __diag calls to suppress -Wmissing-prototypes are migrated to use the newly-introduced macros. A new __diag_ignore_all - for "-Wmissing-declarations" - is added to the __bpf_kfunc_start_defs macro based on feedback from Andrii on an earlier version of this patch [0] and another recent mailing list thread [1]. In the future we might need to ignore different warnings or do other kfunc-specific things. This change will make it easier to make such modifications for all kfunc defs. [0]: https://lore.kernel.org/bpf/CAEf4BzaE5dRWtK6RPLnjTW-MW9sx9K3Fn6uwqCTChK2Dcb1Xig@mail.gmail.com/ [1]: https://lore.kernel.org/bpf/ZT+2qCc%2FaXep0%2FLf@krava/ Signed-off-by:Dave Marchevsky <davemarchevsky@fb.com> Suggested-by:
Andrii Nakryiko <andrii@kernel.org> Acked-by:
Jiri Olsa <jolsa@kernel.org> Acked-by:
David Vernet <void@manifault.com> Acked-by:
Yafang Shao <laoar.shao@gmail.com> Link: https://lore.kernel.org/r/20231031215625.2343848-1-davemarchevsky@fb.com Signed-off-by:
Alexei Starovoitov <ast@kernel.org>
-
Jiri Pirko authored
Add two enum values that the blamed commit omitted. Fixes: f2f9dd16 ("netlink: specs: devlink: add the remaining command to generate complete split_ops") Signed-off-by:
Jiri Pirko <jiri@nvidia.com> Link: https://lore.kernel.org/r/20231030161750.110420-1-jiri@resnulli.us Signed-off-by:
Jakub Kicinski <kuba@kernel.org>
-
- Nov 01, 2023
-
-
Tom Yang authored
The "first" is spelled "fist". Link: https://lkml.kernel.org/r/20231023095737.21823-1-yangqixiao@inspur.com Signed-off-by:
Tom Yang <yangqixiao@inspur.com> Reviewed-by:
Liam R. Howlett <Liam.Howlett@oracle.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org>
-
Andrey Konovalov authored
Drop "the" from the title of the documentation article for UBSAN, as it is redundant. Also add SPDX-License-Identifier for ubsan.rst. Link: https://lkml.kernel.org/r/5fb11a4743eea9d9232a5284dea0716589088fec.1698161845.git.andreyknvl@google.com Signed-off-by:
Andrey Konovalov <andreyknvl@google.com> Reviewed-by:
Marco Elver <elver@google.com> Cc: Alexander Potapenko <glider@google.com> Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com> Cc: Dmitry Vyukov <dvyukov@google.com> Signed-off-by:
-
Masahiro Yamada authored
This syntax is useful to specify libraries linked to all userspace programs in the Makefile. Signed-off-by:Masahiro Yamada <masahiroy@kernel.org>
-
Shawn.Shao authored
Fix the wrong drivers_autoprobe path name in the document Signed-off-by:
Shawn.Shao <shawn.shao@jaguarmicro.com> Message-Id: <20230821011535.1117-1-shawn.shao@jaguarmicro.com> Signed-off-by:
Michael S. Tsirkin <mst@redhat.com> Acked-by:
Jason Wang <jasowang@redhat.com>
-
André Apitzsch authored
Document Kinetic KTD2026/2027 LED driver devicetree bindings. Signed-off-by:
André Apitzsch <git@apitzsch.eu> Reviewed-by:
Lee Jones <lee@kernel.org>
-
Ondrej Jirman authored
Increase the limit to match available values in dt-bindings/leds/common.h Fixes: 472d7b9e ("dt-bindings: leds: Expand LED_COLOR_ID definitions") Signed-off-by:
Ondrej Jirman <megi@xff.cz> Reviewed-by:
-
Linus Walleij authored
We reuse the trigger-sources phandle to just point to GPIOs we may want to use as LED triggers. Example: gpio: gpio@0 { compatible "my-gpio"; gpio-controller; #gpio-cells = <2>; interrupt-controller; #interrupt-cells = <2>; #trigger-source-cells = <2>; }; leds { compatible = "gpio-leds"; led-my-gpio { label = "device:blue:myled"; gpios = <&gpio 0 GPIO_ACTIVE_HIGH>; default-state = "off"; linux,default-trigger = "gpio"; trigger-sources = <&gpio 1 GPIO_ACTIVE_HIGH>; }; }; Signed-off-by:Linus Walleij <linus.walleij@linaro.org> Acked-by:
-
Marek Behún authored
If the MCU on Turris Omnia is running newer firmware versions, the LED controller supports RGB gamma correction (and enables it by default for newer boards). Determine whether the gamma correction setting feature is supported and add the ability to set it via sysfs attribute file. Signed-off-by:
Marek Behún <kabel@kernel.org> Link: https://lore.kernel.org/r/20230918161104.20860-5-kabel@kernel.org Signed-off-by:
-
Rob Herring authored
The Arm Ltd board bindings are a bit unusual in that they define child nodes for various syscon's. The schemas are also incomplete as they lack constraints on having additional properties and some properties are missing. As the bindings for the different platforms only vary by compatibles, combine them into a single schema doc. Add the "arm,im-pd1-syscon" compatible which was not documented. Add "ranges", "#address-cells", and "#size-cells properties which were missing. With this, fix the error exposed in the register-bit-led binding. Signed-off-by:
-
Ondrej Jirman authored
Declare support for this property. Signed-off-by:
Sebastian Reichel <sebastian.reichel@collabora.com> Link: https://lore.kernel.org/r/20231019165732.3818789-3-megi@xff.cz Signed-off-by:
-
Ondrej Jirman authored
Deprecate support for this property in favor of standard system-power-controller one. Signed-off-by:
-
Sebastian Reichel authored
Convert the binding to DT schema format. The sub-functions of this MFD device do not have their own compatible string and are thus described directly in the MFD binding document after being converted to YAML. Signed-off-by:
-
Russ Weight authored
Change ABI documentation contact information from Russ Weight to Peter Colberg. Signed-off-by:
Russ Weight <russell.h.weight@intel.com> Acked-by:
Peter Colberg <peter.colberg@intel.com> Link: https://lore.kernel.org/r/20230928164738.278635-1-russell.h.weight@intel.com Signed-off-by:
-
Luca Weiss authored
There's not much point in having unused labels in the binding example, so drop them. This patch was originally motivated by ea25d61b ("arm64: dts: qcom: Use plural _gpios node label for PMIC gpios") updating all dts files to use the plural _gpios label instead of the singular _gpio as label but this example wasn't updated. But since we should just drop the label alltogether, do that. Signed-off-by:
Luca Weiss <luca.weiss@fairphone.com> Acked-by:
-
Chen-Yu Tsai authored
The MT6366 PMIC is mostly, but not fully, compatible with MT6358. It has a different set of regulators. Specifically, it lacks the camera related VCAM* LDOs and VLDO28, but has additional VM18, VMDDR, and VSRAM_CORE LDOs. The PMICs contain a chip ID register that can be used to detect which exact model is preset, so it is possible to share a common base compatible string. Add a separate compatible for the MT6366 PMIC, with a fallback to the MT6358 PMIC. Fixes: 49be1630 ("dt-bindings: mfd: Add compatible for the MediaTek MT6366 PMIC") Signed-off-by:
Chen-Yu Tsai <wenst@chromium.org> Acked-by:
AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Link: https://lore.kernel.org/r/20230928085537.3246669-2-wenst@chromium.org Signed-off-by:
-
Rob Herring authored
Just as unevaluatedProperties or additionalProperties are required at the top level of schemas, they should (and will) also be required for child node schemas. That ensures only documented properties are present for any node. Add unevaluatedProperties as needed, and then add any missing properties flagged by the addition. Signed-off-by:
-
Andre Przywara authored
All X-Powers PMICs described by this binding have an IRQ pin, and so far (almost) all boards connected this to some NMI pin or GPIO on the SoC they are connected to. However we start to see boards that omit this connection, and technically the IRQ pin is not essential to the basic PMIC operation. The existing Linux driver allows skipping the IRQ pin setup for two chips already, so update the binding to also make the DT property optional for the missing chip. And while we are at it, add the AXP313a to that list, as they are actually boards out there not connecting the IRQ pin. This allows to have DTs correctly describing those boards not wiring up the interrupt. Signed-off-by:
Andre Przywara <andre.przywara@arm.com> Acked-by:
-
Andreas Kemnade authored
Since these devices provide clock outputs, add the corresponding property. Signed-off-by:
Andreas Kemnade <andreas@kemnade.info> Acked-by:
-
Andreas Kemnade authored
Convert the TWL[46]030 binding to DT schema format. To do it as a step by step work, do not include / handle nodes for subdevices yet, just convert things with minimal corrections. There are already some bindings for its subdevices in the tree. Signed-off-by:
-
Andrew Davis authored
Add TI DSS OLDI-IO control registers compatible. This is a region of 5 32bit registers found in the TI AM65 CTRL_MMR0 register space[0]. They are used to control the characteristics of the OLDI DATA/CLK IO as needed by the DSS display controller node. [0] https://www.ti.com/lit/pdf/spruid7 Signed-off-by:
Andrew Davis <afd@ti.com> Acked-by:
Aradhya Bhatia <a-bhatia1@ti.com> Link: https://lore.kernel.org/r/20230911142556.64108-1-afd@ti.com Signed-off-by:
-
Krzysztof authoredConvert the bindings for Maxim MAX8998, National/TI LP3974 Power Management IC to DT schema. Adjust example to real DTS and make second interrupt optional (like on s5pv210-aries.dtsi). Signed-off-by:
-
Tengfei Fan authored
Document the qcom,sm4450-tcsr compatible. Signed-off-by:
Tengfei Fan <quic_tengfan@quicinc.com> Reviewed-by:
-
Geert Uytterhoeven authored
Fix a misspelling of "Cortex-A9". Signed-off-by:
Geert Uytterhoeven <geert+renesas@glider.be> Reviewed-by:
-
Alex Bee authored
Document Rockchip RK3128 SoC compatible for qos registers. Signed-off-by:
Alex Bee <knaerzche@gmail.com> Acked-by:
-
Bryan O'Donoghue authoredAdd the PMIC Type-C port driver to the list of devices. Signed-off-by:
Bryan O'Donoghue <bryan.odonoghue@linaro.org> Acked-by:
-
Dmitry Baryshkov authoredAdd gpio, keypad, led, mpps, pwrkey, vibrator and xoadc as possible child nodes of qcom,pm8xxx, referencing existint schema files. Signed-off-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Reviewed-by:
-
Dmitry Baryshkov authored
Add bindings for the PM8450 PMIC (qcom,pm8450). No driver changes are necessary, since the PMIC is handled by the generic qcom,spmi-pmic entry. Signed-off-by:
-
- Oct 31, 2023
-
-
Paul E. McKenney authored
Add /proc/bootconfig description to Documentation/filesystems/proc.rst. Link: https://lore.kernel.org/all/20231005171747.541123-3-paulmck@kernel.org/ Reported-by:
Paul E. McKenney <paulmck@kernel.org> Acked-by:
-
- Oct 30, 2023
-
-
Amir Goldstein authored
Add new mount options lowerdir+ and datadir+ that can be used to add layers to lower layers stack one by one. Unlike the legacy lowerdir mount option, special characters (i.e. colons and cammas) are not unescaped with these new mount options. The new mount options can be repeated to compose a large stack of lower layers, but they may not be mixed with the lagacy lowerdir mount option, because for displaying lower layers in mountinfo, we do not want to mix escaped with unescaped lower layers path syntax. Similar to data-only layer rules with the lowerdir mount option, the datadir+ option must follow at least one lowerdir+ option and the lowerdir+ option must not follow the datadir+ option. If the legacy lowerdir mount option follows lowerdir+ and datadir+ mount options, it overrides them. Sepcifically, calling: fsconfig(FSCONFIG_SET_STRING, "lowerdir", "", 0); can be used to reset previously setup lower layers. Suggested-by:
Miklos Szeredi <miklos@szeredi.hu> Link: https://lore.kernel.org/r/CAJfpegt7VC94KkRtb1dfHG8+4OzwPBLYqhtc8=QFUxpFJE+=RQ@mail.gmail.com/ Signed-off-by:
Amir Goldstein <amir73il@gmail.com>
-
Alexander Larsson authored
Signed-off-by:
Alexander Larsson <alexl@redhat.com> Reviewed-by:
-
