Re: [PATCH 1/1] of: unittest: fix dts for interrupt-map provider build warning

From: Rob Herring
Date: Fri Oct 29 2021 - 09:16:42 EST


On Thu, Oct 28, 2021 at 10:07 PM Frank Rowand <frowand.list@xxxxxxxxx> wrote:
>
> On 10/28/21 9:07 PM, Rob Herring wrote:
> > On Thu, Oct 28, 2021 at 7:58 PM <frowand.list@xxxxxxxxx> wrote:
> >>
> >> From: Frank Rowand <frank.rowand@xxxxxxxx>
> >>
> >> Fix kernel build warning:
> >> drivers/of/unittest-data/tests-interrupts.dtsi:32.26-35.6: Warning (interrupt_map): /testcase-data/interrupts/intmap1: Missing '#address-cells' in interrupt-map provider
> >>
> >> A recently implemented dtc compiler warning reported the dts problem.
> >>
> >> Signed-off-by: Frank Rowand <frank.rowand@xxxxxxxx>
> >> ---
> >> drivers/of/unittest-data/tests-interrupts.dtsi | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/drivers/of/unittest-data/tests-interrupts.dtsi b/drivers/of/unittest-data/tests-interrupts.dtsi
> >> index 9b60a549f502..8c2b91b998aa 100644
> >> --- a/drivers/of/unittest-data/tests-interrupts.dtsi
> >> +++ b/drivers/of/unittest-data/tests-interrupts.dtsi
> >> @@ -31,6 +31,7 @@ test_intmap0: intmap0 {
> >>
> >> test_intmap1: intmap1 {
> >> #interrupt-cells = <2>;
> >> + #address-cells = <1>;
> >
> > Notice that we have 2 nodes with interrupt-map here. One has
> > '#address-cells' and one doesn't. Why? Because we need to test that
> > the code can handle both cases.>
> > The dtc warnings are more what should 'new' users do. I don't know
> > what DTs don't have #address-cells, but my guess is ancient ones.
> >
> > Rob
> >
>
> I had hoped to build all of the .dts files in the Linux tree, with the
> new dtc, but did not get to that today. That should flush out any
> cases that would result in build fail from the new approach of treating
> all warnings as errors. I may get to that tomorrow.

They are still just warnings. You mean the requirement to be warning
free? That's not new for dts files.

> If there any any existing .dts files that will trigger the interrupt
> map warning, will we require that they be fixed so that the build will
> not fail?

I already submitted patches for them.

Rob