[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6db6e1d4-a0b1-4ce3-9235-d92bb19da1d6@foss.st.com>
Date: Wed, 5 Feb 2025 17:02:19 +0100
From: Alexandre TORGUE <alexandre.torgue@...s.st.com>
To: Oleksij Rempel <o.rempel@...gutronix.de>,
"Rob Herring (Arm)"
<robh@...nel.org>
CC: <linux-kernel@...r.kernel.org>, Jakub Kicinski <kuba@...nel.org>,
Maxime
Coquelin <mcoquelin.stm32@...il.com>,
Woojung Huh
<woojung.huh@...rochip.com>,
Paolo Abeni <pabeni@...hat.com>, Andrew Lunn
<andrew+netdev@...n.ch>,
<devicetree@...r.kernel.org>, Eric Dumazet
<edumazet@...gle.com>,
<linux-stm32@...md-mailman.stormreply.com>,
Krzysztof
Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
"David S.
Miller" <davem@...emloft.net>, <netdev@...r.kernel.org>,
<kernel@...gutronix.de>
Subject: Re: [PATCH v3 0/4] Add support for Priva E-Measuringbox board
Hi Oleksij
On 2/5/25 10:17, Oleksij Rempel wrote:
> Hi Alexandre,
>
> On Mon, Feb 03, 2025 at 09:37:06AM -0600, Rob Herring (Arm) wrote:
>>
>> On Mon, 03 Feb 2025 09:58:16 +0100, Oleksij Rempel wrote:
>>> This patch series introduces support for the Priva E-Measuringbox board
>>> based on the ST STM32MP133 SoC. The set includes all the necessary
>>> changes for device tree bindings, vendor prefixes, thermal support, and
>>> board-specific devicetree to pass devicetree validation and checkpatch
>>> tests.
>>>
>
> ...
>
>> arch/arm/boot/dts/st/stm32mp133c-prihmb.dtb: adc@...04000: adc@0:interrupts: 0 was expected
>> from schema $id: http://devicetree.org/schemas/iio/adc/st,stm32-adc.yaml#
>> arch/arm/boot/dts/st/stm32mp133c-prihmb.dtb: adc@...03000: adc@0:interrupts: 0 was expected
>> from schema $id: http://devicetree.org/schemas/iio/adc/st,stm32-adc.yaml#
>
>
> Can I please get your attention here. The reported issue is not related
> to this patch set. adc@0:interrupts are set in the dtsi file.
Yes I saw this issue too when I tried to merge your series. I'm
discussing with STM32 ADC driver owner to fix the issue (either in stm32
adc yaml or maybe in schema).
Anyway we also have the issue for STM32MP135F-DK board so I'll merge
your series as it doesn't introduce the issue.
regards
Alex
> Kind regards,
> Oleksij
Powered by blists - more mailing lists