All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] of: unittest: fix dts for interrupt-map provider build warning
Date: Thu, 28 Oct 2021 22:07:21 -0500	[thread overview]
Message-ID: <e353b41d-48f9-5349-8b89-bafe9ab5101e@gmail.com> (raw)
In-Reply-To: <CAL_JsqJujq0K9tF+m3qQ5GhC-yo7-vj9HRhF69UmrWA7tZv7DA@mail.gmail.com>

On 10/28/21 9:07 PM, Rob Herring wrote:
> On Thu, Oct 28, 2021 at 7:58 PM <frowand.list@gmail.com> wrote:
>>
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> 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@sony.com>
>> ---
>>  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.

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?

-Frank

  reply	other threads:[~2021-10-29  3:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29  0:58 [PATCH 1/1] of: unittest: fix dts for interrupt-map provider build warning frowand.list
2021-10-29  2:07 ` Rob Herring
2021-10-29  3:07   ` Frank Rowand [this message]
2021-10-29 13:16     ` Rob Herring
2021-10-29 17:33       ` Frank Rowand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e353b41d-48f9-5349-8b89-bafe9ab5101e@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.