dt-bindings: mfd: mxs-lradc: Fix interrupt order
Subsystems (7)
Fabio Estevam
reviewerPATCH v5 1/4 dt-bindings: mfd: mxs-lradc: Fix interrupt order
The interrupt descriptions added during the conversion to YAML do not match the ICOLL source numbers used by the existing DTS files.
For i.MX23, Table 5-1 of the reference manual maps source 36 to touch detection and sources 37 through 44 to channels 0 through 7. The DTS lists these sources in that order.
For i.MX28, Table 5-1 maps source 10 to touch detection, sources 14 and 15 to the threshold interrupts, sources 16 through 23 to channels 0 through 7, and sources 24 and 25 to buttons 0 and 1. The DTS also lists these sources in that order.
Reorder the schema descriptions to match the hardware documentation and the existing DT ABI.
This change was prepared with assistance from OpenAI Codex, which was used to compare the binding with the reference manuals, existing DTS, and driver ordering.
---
Changes since v4:
- None.
Documentation/devicetree/bindings/mfd/mxs-lradc.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
Documentation/devicetree/bindings/mfd/mxs-lradc.yaml +4 -4
@@ -87,13 +87,13 @@ then: properties: interrupts: items: + - description: touchscreen - description: channel 0 - description: channel 1 - description: channel 2 - description: channel 3 - description: channel 4 - description: channel 5 - - description: touchscreen - description: channel 6 - description: channel 7 fsl,lradc-touchscreen-wires:
@@ -102,6 +102,7 @@ else: properties: interrupts: items: + - description: touchscreen - description: threshold 0 - description: threshold 1 - description: channel 0
@@ -110,11 +111,10 @@ else: - description: channel 3 - description: channel 4 - description: channel 5 - - description: button 0 - - description: button 1 - - description: touchscreen - description: channel 6 - description: channel 7 + - description: button 0 + - description: button 1 additionalProperties: false
Signature · 1 line
2.43.0
Fabio Estevam
reviewerPATCH v5 2/4 iio: adc: mxs-lradc: Fix trigger use-after-free on removal
The LRADC trigger is devm-allocated against the IIO device, but it is manually unregistered after iio_device_unregister(). The latter deletes the IIO device and releases its managed resources, freeing the trigger before mxs_lradc_adc_trigger_remove() accesses it.
Since commit 699fb50d9903 ("drivers: base: Free devm resources when unregistering a device"), device_del() releases managed resources. Consequently, iio_device_unregister() drops the trigger's allocation reference before the driver unregisters it.
On an i.MX28 EVK with KASAN enabled, unbinding the LRADC parent with:
echo 80050000.lradc > /sys/bus/platform/drivers/mxs-lradc/unbind
reports a slab-use-after-free in device_release_driver_internal().
Allocate the managed trigger against the platform device instead. This matches the trigger device's parent and keeps the allocation alive until the platform driver's remove callback has unregistered the trigger.
---
Changes since v4:
- None. Only collected Joshua's tag.
drivers/iio/adc/mxs-lradc-adc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iio/adc/mxs-lradc-adc.c +1 -1
@@ -454,7 +454,7 @@ static int mxs_lradc_adc_trigger_init(struct iio_dev *iio)struct iio_trigger *trig;struct mxs_lradc_adc *adc =iio_priv (iio); - trig =devm_iio_trigger_alloc (&iio->dev,"%s-dev%i" , iio->name, + trig =devm_iio_trigger_alloc (adc->dev,"%s-dev%i" , iio->name,iio_device_id (iio));if (!trig)return -ENOMEM ;
Signature · 1 line
2.43.0
[email protected]
AI reviewRe: [PATCH v5 2/4] iio: adc: mxs-lradc: Fix trigger use-after-free on removal
Sashiko has reviewed this patch and found no issues.
Quoted 16 lines
The LRADC trigger is devm-allocated against the IIO device, but it is manually unregistered after
iio_device_unregister(). The latter deletes the IIO device and releases its managed resources, freeing the trigger beforemxs_lradc_adc_trigger_remove()accesses it.Since commit
699fb50d9903("drivers: base: Free devm resources when unregistering a device"),device_del()releases managed resources. Consequently,iio_device_unregister()drops the trigger's allocation reference before the driver unregisters it.On an i.MX28 EVK with KASAN enabled, unbinding the LRADC parent with:
echo 80050000.lradc >
/sys/bus/platform/drivers/mxs-lradc/unbindreports a slab-use-after-free in
device_release_driver_internal().
Quoted 7 lines
Allocate the managed trigger against the platform device instead. This matches the trigger device's parent and keeps the allocation alive until the platform driver's remove callback has unregistered the trigger.
Fixes 699fb50d9903 ("drivers: base: Free devm resources when unregistering a device")Signed-off-by Fabio Estevam <[email protected]>
Sashiko has reviewed this patch and found no issues.
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=2
Fabio Estevam
reviewerPATCH v5 3/4 mfd: mxs-lradc: Pass parent IRQs to child drivers
In reply to Fabio EstevamThe MFD driver stores raw DT interrupt indices in IRQ resources but registers its child devices without an IRQ domain or IRQ base. The child drivers consequently receive the indices as if they were mapped Linux IRQ numbers. IRQ index 0 triggers the platform_get_irq_byname() warning:
0 is an invalid IRQ number
The children then try to recover the indices from their resources and map them against the parent OF node. Besides duplicating IRQ names in the parent and children, this relies on invalid platform IRQ resources and fails when IRQ 0 is rejected.
Resolve the interrupts with platform_get_irq() in the MFD parent and store the mapped IRQs in the shared LRADC data. Drop the child IRQ resources and duplicated name arrays, and have both child drivers request the mapped IRQs directly. Map the MMIO region once in the parent and share the mapping with both child drivers through struct mxs_lradc, removing the child memory resources.
Tested on an i.MX28 EVK. The mxs-lradc-ts driver probes successfully, touch events are reported, and the touch-detect and LRADC channel 7 interrupt counters increase as expected.
---
Changes since v4:
- Correct the commit message to describe the shared parent MMIO mapping. (Sashiko)
KASAN is happy now after unbind/bind:
echo 80050000.lradc > /sys/bus/platform/drivers/mxs-lradc/unbind echo 80050000.lradc > /sys/bus/platform/drivers/mxs-lradc/bind echo 80050000.lradc > /sys/bus/platform/drivers/mxs-lradc/unbind
This is a long-standing bug that I reported in 2020:
https://lore.kernel.org/linux-input/CAOMZO5CgTzo6GuXptD4mFTN=UsJJqpkixDW1Q64gqZGrij8+uQ@mail.gmail.com/
This patch touches MFD, IIO, and Input. Since the IRQ mapping is moved into the MFD parent, I suggest merging it through the MFD tree, with acks from the IIO and Input maintainers.
The full backtrace:
[ 10.540505] WARNING: drivers/base/platform.c:492 at __platform_get_irq_byname+0xb4/0xcc, CPU#0: swapper/0/1 [ 10.555516] 0 is an invalid IRQ number [ 10.559627] Modules linked in: [ 10.562849] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.3.0-rc7-next-20261016-00003-g36062817a968 #17 VOLUNTARY [ 10.573732] Hardware name: Freescale MXS (Device Tree) [ 10.578934] Call trace: [ 10.578992] unwind_backtrace from show_stack+0x10/0x14 [ 10.586955] show_stack from dump_stack_lvl+0x48/0x64 [ 10.592170] dump_stack_lvl from __warn+0x8c/0x190 [ 10.597114] __warn from warn_slowpath_fmt+0x94/0xcc [ 10.602232] warn_slowpath_fmt from __platform_get_irq_byname+0xb4/0xcc [ 10.609027] __platform_get_irq_byname from platform_get_irq_byname+0x10/0x30 [ 10.616337] platform_get_irq_byname from mxs_lradc_ts_probe+0x18c/0x378 [ 10.623247] mxs_lradc_ts_probe from platform_probe+0x58/0x90 [ 10.629174] platform_probe from really_probe+0xc4/0x2cc [ 10.634649] really_probe from __driver_probe_device+0xa0/0x1e0 [ 10.640721] __driver_probe_device from driver_probe_device+0x30/0xc0 [ 10.647315] driver_probe_device from __driver_attach+0x94/0x158 [ 10.653466] __driver_attach from bus_for_each_dev+0x7c/0xd0 [ 10.659280] bus_for_each_dev from bus_add_driver+0x158/0x1fc [ 10.665169] bus_add_driver from driver_register+0x7c/0x114 [ 10.670901] driver_register from do_one_initcall+0x60/0x294 [ 10.676721] do_one_initcall from kernel_init_freeable+0x19c/0x24c [ 10.683073] kernel_init_freeable from kernel_init+0x14/0x10c [ 10.688997] kernel_init from ret_from_fork+0x14/0x38 [ 10.694200] Exception stack(0xc8819fb0 to 0xc8819ff8) [ 10.699335] 9fa0: 00000000 00000000 00000000 00000000 [ 10.707591] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 10.715843] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 10.723117] irq event stamp: 146363 [ 10.726729] hardirqs last enabled at (146367): [<c00adbd8>] __nbcon_atomic_flush_pending_con+0x120/0x1c0 [ 10.736770] hardirqs last disabled at (146372): [<c0008f38>] __irq_svc+0x58/0xb0 [ 10.744618] softirqs last enabled at (146362): [<c0032c20>] __irq_exit_rcu+0x148/0x1d4 [ 10.753153] softirqs last disabled at (146385): [<c0032c20>] __irq_exit_rcu+0x148/0x1d4 [ 10.761603] ---[ end trace 0000000000000000 ]--- [ 10.766374] mxs-lradc-ts mxs-lradc-ts: error -EINVAL: IRQ mxs-lradc-touchscreen not found [ 10.766456] mxs-lradc-ts mxs-lradc-ts: probe with driver mxs-lradc-ts failed with error -22
drivers/iio/adc/mxs-lradc-adc.c | 53 +------ drivers/input/touchscreen/mxs-lradc-ts.c | 35 ++--- drivers/mfd/mxs-lradc.c | 184 +++++++++++------------ include/linux/mfd/mxs-lradc.h | 12 ++ 4 files changed, 115 insertions(+), 169 deletions(-)
drivers/iio/adc/mxs-lradc-adc.c +6 -47
@@ -17,7 +17,6 @@#include <linux/mfd/core.h> #include <linux/mfd/mxs-lradc.h> #include <linux/module.h> -#include <linux/of_irq.h> #include <linux/platform_device.h> #include <linux/sysfs.h>
@@ -39,28 +38,6 @@#define VREF_MV_BASE 1850 -static const char *mx23_lradc_adc_irq_names[] = { -"mxs-lradc-channel0" , -"mxs-lradc-channel1" , -"mxs-lradc-channel2" , -"mxs-lradc-channel3" , -"mxs-lradc-channel4" , -"mxs-lradc-channel5" , -}; - -static const char *mx28_lradc_adc_irq_names[] = { -"mxs-lradc-thresh0" , -"mxs-lradc-thresh1" , -"mxs-lradc-channel0" , -"mxs-lradc-channel1" , -"mxs-lradc-channel2" , -"mxs-lradc-channel3" , -"mxs-lradc-channel4" , -"mxs-lradc-channel5" , -"mxs-lradc-button0" , -"mxs-lradc-button1" , -}; -static const u32 mxs_lradc_adc_vref_mv[][LRADC_MAX_TOTAL_CHANS ] = { [IMX23_LRADC ] = {VREF_MV_BASE ,/* CH0 */
@@ -690,10 +667,8 @@ static int mxs_lradc_adc_probe(struct platform_device *pdev)struct mxs_lradc *lradc =dev_get_drvdata (dev->parent);struct mxs_lradc_adc *adc;struct iio_dev *iio; -struct resource *iores; -int ret, irq, virq, i, s, n; +int ret, i, s;u64 scale_uv; -const char **irq_name;/* Allocate the IIO device. */ iio =devm_iio_device_alloc (dev,sizeof (*adc));
@@ -703,14 +678,7 @@ static int mxs_lradc_adc_probe(struct platform_device *pdev) adc =iio_priv (iio); adc->lradc = lradc; adc->dev = dev; - - iores =platform_get_resource (pdev,IORESOURCE_MEM ,0 ); -if (!iores) -return -EINVAL ; - - adc->base =devm_ioremap (dev, iores->start,resource_size (iores)); -if (!adc->base) -return -ENOMEM ; + adc->base = lradc->base;init_completion (&adc->completion);spin_lock_init (&adc->lock);
@@ -725,28 +693,19 @@ static int mxs_lradc_adc_probe(struct platform_device *pdev)if (lradc->soc ==IMX23_LRADC ) { iio->channels = mx23_lradc_chan_spec; iio->num_channels =ARRAY_SIZE (mx23_lradc_chan_spec); - irq_name = mx23_lradc_adc_irq_names; - n =ARRAY_SIZE (mx23_lradc_adc_irq_names); }else { iio->channels = mx28_lradc_chan_spec; iio->num_channels =ARRAY_SIZE (mx28_lradc_chan_spec); - irq_name = mx28_lradc_adc_irq_names; - n =ARRAY_SIZE (mx28_lradc_adc_irq_names); } ret =stmp_reset_block (adc->base);if (ret)return ret; -for (i =0 ; i < n; i++) { - irq =platform_get_irq_byname (pdev, irq_name[i]); -if (irq <0 ) -return irq; - - virq =irq_of_parse_and_map (dev->parent->of_node, irq); - - ret =devm_request_irq (dev, virq, mxs_lradc_adc_handle_irq, -0 , irq_name[i], iio); +for (i =0 ; i < lradc->num_adc_irqs; i++) { + ret =devm_request_irq (dev, lradc->adc_irq[i], + mxs_lradc_adc_handle_irq,0 , +dev_name (dev), iio);if (ret)return ret; }
drivers/input/touchscreen/mxs-lradc-ts.c +9 -26
@@ -18,15 +18,8 @@#include <linux/mfd/core.h> #include <linux/mfd/mxs-lradc.h> #include <linux/of.h> -#include <linux/of_irq.h> #include <linux/platform_device.h> -static const char *const mxs_lradc_ts_irq_names[] = { -"mxs-lradc-touchscreen" , -"mxs-lradc-channel6" , -"mxs-lradc-channel7" , -}; -/* * Touchscreen handling */
@@ -601,12 +594,12 @@ static int mxs_lradc_ts_register(struct mxs_lradc_ts *ts)static int mxs_lradc_ts_probe (struct platform_device *pdev) { -struct device *dev = &pdev->dev; -struct device_node *node = dev->parent->of_node; -struct mxs_lradc *lradc =dev_get_drvdata (dev->parent);struct mxs_lradc_ts *ts; -int ret, irq, virq, i; +struct device_node *node = pdev->dev.parent->of_node; +struct mxs_lradc *lradc =dev_get_drvdata (pdev->dev.parent); +struct device *dev = &pdev->dev;u32 ts_wires =0 , adapt; +int ret, i; ts =devm_kzalloc_obj (dev, *ts);if (!ts)
@@ -616,12 +609,9 @@ static int mxs_lradc_ts_probe(struct platform_device *pdev) ts->lradc = lradc; ts->dev = dev; + ts->base = lradc->base;spin_lock_init (&ts->lock); - ts->base =devm_platform_ioremap_resource (pdev,0 ); -if (IS_ERR (ts->base)) -return PTR_ERR (ts->base); - ret =of_property_read_u32 (node,"fsl,lradc-touchscreen-wires" , &ts_wires);if (ret)
@@ -668,19 +658,12 @@ static int mxs_lradc_ts_probe(struct platform_device *pdev)return ret;mxs_lradc_ts_hw_init (ts); +mxs_lradc_ts_stop (ts); -for (i =0 ; i <3 ; i++) { - irq =platform_get_irq_byname (pdev, mxs_lradc_ts_irq_names[i]); -if (irq <0 ) -return irq; - - virq =irq_of_parse_and_map (node, irq); - -mxs_lradc_ts_stop (ts); - - ret =devm_request_irq (dev, virq, +for (i =0 ; i <ARRAY_SIZE (lradc->ts_irq); i++) { + ret =devm_request_irq (dev, lradc->ts_irq[i], mxs_lradc_ts_handle_irq, -0 , mxs_lradc_ts_irq_names[i], ts); +0 ,dev_name (dev), ts);if (ret)return ret; }
drivers/mfd/mxs-lradc.c +88 -96
234 lines not on this page · raw message
include/linux/mfd/mxs-lradc.h +12 -0
@@ -19,6 +19,9 @@#define LRADC_MAX_MAPPED_CHANS 8#define LRADC_MAX_TOTAL_CHANS 16 +#define MXS_LRADC_MAX_ADC_IRQS 10 +#define MXS_LRADC_NUM_TS_IRQS 3 +#define LRADC_DELAY_TIMER_HZ 2000#define LRADC_CTRL0 0x00
@@ -149,18 +152,27 @@ enum mxs_lradc_ts_wires {/** * struct mxs_lradc * @soc: soc type (IMX23 or IMX28) +* @base: mapped LRADC register base * @clk: 2 kHz clock for delay units * @buffer_vchans: channels that can be used during buffered capture * @touchscreen_wire: touchscreen type (4-wire or 5-wire) * @use_touchbutton: button state (on or off) +* @num_adc_irqs: number of ADC interrupts +* @adc_irq: ADC interrupts +* @ts_irq: touchscreen interrupts */ struct mxs_lradc {enum mxs_lradc_id soc; +void __iomem *base;struct clk *clk;u8 buffer_vchans;enum mxs_lradc_ts_wires touchscreen_wire;bool use_touchbutton; + +unsigned int num_adc_irqs; +int adc_irq[MXS_LRADC_MAX_ADC_IRQS ]; +int ts_irq[MXS_LRADC_NUM_TS_IRQS ]; };static inline u32 mxs_lradc_irq_mask (struct mxs_lradc *lradc)
Signature · 1 line
2.43.0
[email protected]
AI reviewRe: [PATCH v5 3/4] mfd: mxs-lradc: Pass parent IRQs to child drivers
Sashiko has reviewed this patch and found no issues.
Quoted 23 lines
The MFD driver stores raw DT interrupt indices in IRQ resources but registers its child devices without an IRQ domain or IRQ base. The child drivers consequently receive the indices as if they were mapped Linux IRQ numbers. IRQ index 0 triggers the
platform_get_irq_byname()warning:0 is an invalid IRQ number
The children then try to recover the indices from their resources and map them against the parent OF node. Besides duplicating IRQ names in the parent and children, this relies on invalid platform IRQ resources and fails when IRQ 0 is rejected.
Resolve the interrupts with
platform_get_irq()in the MFD parent and store the mapped IRQs in the shared LRADC data. Drop the child IRQ resources and duplicated name arrays, and have both child drivers request the mapped IRQs directly. Map the MMIO region once in the parent and share the mapping with both child drivers through structmxs_lradc, removing the child memory resources.Tested on an i.MX28 EVK. The mxs-lradc-ts driver probes successfully, touch events are reported, and the touch-detect and LRADC channel 7 interrupt counters increase as expected.
Quoted 5 lines
Suggested-by Lee Jones <[email protected]>Closes https://lore.kernel.org/linux-input/CAOMZO5CgTzo6GuXptD4mFTN=UsJJqpkixDW1Q64gqZGrij8+uQ@mail.gmail.com/ open hereFixes a85a6c86c25b ("driver core: platform: Clarify that IRQ 0 is invalid")Signed-off-by Fabio Estevam <[email protected]>
Sashiko has reviewed this patch and found no issues.
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=3
Fabio Estevam
reviewerPATCH v5 4/4 mfd: mxs-lradc: Convert to devm_clk_get_enabled()
In reply to Fabio EstevamThe LRADC clock is acquired with a managed helper but enabled and disabled manually.
Acquire the LRADC clock with devm_clk_get_enabled() instead of a bare devm_clk_get() followed by a manual clk_prepare_enable(), so it is prepared/enabled for the device lifetime and released on unbind.
This conversion makes the code simpler.
---
Changes since v4:
- None.
drivers/mfd/mxs-lradc.c | 35 +++++++---------------------------- 1 file changed, 7 insertions(+), 28 deletions(-)
drivers/mfd/mxs-lradc.c +7 -28
@@ -160,17 +160,10 @@ static int mxs_lradc_probe(struct platform_device *pdev)if (IS_ERR (lradc->base))return PTR_ERR (lradc->base); - lradc->clk =devm_clk_get (&pdev->dev,NULL ); -if (IS_ERR (lradc->clk)) { -dev_err (dev,"Failed to get the delay unit clock\n" ); -return PTR_ERR (lradc->clk); - } - - ret =clk_prepare_enable (lradc->clk); -if (ret) { -dev_err (dev,"Failed to enable the delay unit clock\n" ); -return ret; - } + lradc->clk =devm_clk_get_enabled (dev,NULL ); +if (IS_ERR (lradc->clk)) +return dev_err_probe (dev,PTR_ERR (lradc->clk), +"Failed to get and enable the delay unit clock\n" ); ret =of_property_read_u32 (node,"fsl,lradc-touchscreen-wires" , &ts_wires);
@@ -193,8 +186,7 @@ static int mxs_lradc_probe(struct platform_device *pdev)dev_err (&pdev->dev,"Unsupported number of touchscreen wires (%d)\n" , ts_wires); - ret = -EINVAL ; - goto err_clk; +return -EINVAL ; } }else { lradc->buffer_vchans =BUFFER_VCHANS_ALL ;
@@ -204,29 +196,17 @@ static int mxs_lradc_probe(struct platform_device *pdev) ret =mxs_lradc_get_irqs (pdev, lradc, data);if (ret) - goto err_clk; +return ret; num_cells = lradc->touchscreen_wire ?ARRAY_SIZE (mxs_lradc_cells) :1 ; ret =devm_mfd_add_devices (dev,PLATFORM_DEVID_NONE , mxs_lradc_cells, num_cells,NULL ,0 ,NULL );if (ret) {dev_err (dev,"Failed to add subdevices\n" ); - goto err_clk; +return ret; }return 0 ; - -err_clk: -clk_disable_unprepare (lradc->clk); - -return ret; -} - -static void mxs_lradc_remove (struct platform_device *pdev) -{ -struct mxs_lradc *lradc =platform_get_drvdata (pdev); - -clk_disable_unprepare (lradc->clk); }static struct platform_driver mxs_lradc_driver = {
@@ -235,7 +215,6 @@ static struct platform_driver mxs_lradc_driver = { .of_match_table = mxs_lradc_dt_ids, }, .probe = mxs_lradc_probe, - .remove = mxs_lradc_remove, };module_platform_driver (mxs_lradc_driver);
Signature · 1 line
2.43.0
[email protected]
AI reviewRe: [PATCH v5 4/4] mfd: mxs-lradc: Convert to devm_clk_get_enabled()
Sashiko has reviewed this patch and found no issues.
Quoted 11 lines
The LRADC clock is acquired with a managed helper but enabled and disabled manually.
Acquire the LRADC clock with
devm_clk_get_enabled()instead of a baredevm_clk_get()followed by a manualclk_prepare_enable(), so it is prepared/enabled for the device lifetime and released on unbind.This conversion makes the code simpler.
Suggested-by Jonathan Cameron <[email protected]>Signed-off-by Fabio Estevam <[email protected]>
Sashiko has reviewed this patch and found no issues.
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=4
[email protected]
AI reviewSashiko has reviewed this patch and found no issues.
Quoted 15 lines
The interrupt descriptions added during the conversion to YAML do not match the ICOLL source numbers used by the existing DTS files.
For i.MX23, Table 5-1 of the reference manual maps source 36 to touch detection and sources 37 through 44 to channels 0 through 7. The DTS lists these sources in that order.
For i.MX28, Table 5-1 maps source 10 to touch detection, sources 14 and 15 to the threshold interrupts, sources 16 through 23 to channels 0 through 7, and sources 24 and 25 to buttons 0 and 1. The DTS also lists these sources in that order.
Reorder the schema descriptions to match the hardware documentation and the existing DT ABI.
Quoted 6 lines
This change was prepared with assistance from OpenAI Codex, which was used to compare the binding with the reference manuals, existing DTS, and driver ordering.
Fixes 009528b5aa13 ("dt-bindings: mfd: convert mxs-lradc bindings to json-schema")Signed-off-by Fabio Estevam <[email protected]>
Sashiko has reviewed this patch and found no issues.
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1