Bootloader (as U-Boot) is not using interrupt which doesn't need to be even
described in DT that's why make interrupt optional property.

Signed-off-by: Michal Simek <michal.simek@amd.com>
---

For example mini configurations used for programming.
https://source.denx.de/u-boot/u-boot/-/blob/master/arch/arm/dts/zynqmp-mini-emmc0.dts
---
 Documentation/devicetree/bindings/mmc/arasan,sdhci.yaml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/mmc/arasan,sdhci.yaml b/Documentation/devicetree/bindings/mmc/arasan,sdhci.yaml
index 8e79de97b242..0472225e6e58 100644
--- a/Documentation/devicetree/bindings/mmc/arasan,sdhci.yaml
+++ b/Documentation/devicetree/bindings/mmc/arasan,sdhci.yaml
@@ -192,7 +192,6 @@ dependencies:
 required:
   - compatible
   - reg
-  - interrupts
   - clocks
   - clock-names
 
-- 
2.43.0

On Wed, Jun 04, 2025 at 10:51:54AM +0200, Michal Simek wrote:
> Bootloader (as U-Boot) is not using interrupt which doesn't need to be even
> described in DT that's why make interrupt optional property.

That's true for 'interrupts' everywhere. It could also be true for 
clocks, resets, etc. If the h/w always has the resource, it should be 
required in DT.

Rob

On 6/5/25 15:03, Rob Herring wrote:
> On Wed, Jun 04, 2025 at 10:51:54AM +0200, Michal Simek wrote:
>> Bootloader (as U-Boot) is not using interrupt which doesn't need to be even
>> described in DT that's why make interrupt optional property.
> 
> That's true for 'interrupts' everywhere. It could also be true for
> clocks, resets, etc. If the h/w always has the resource, it should be
> required in DT.

ok. fine.

Thanks,
Michal