Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1352711

Re: [PATCH] scripts/dtc: Update to upstream version 53bf130b1cdd

Show all headers | View raw

On Mon, Mar 7, 2016 at 5:27 AM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Hi Rob,
>
> On Fri, Mar 4, 2016 at 4:13 PM, Rob Herring <robh@kernel.org> wrote:
>> Sync to upstream dtc commit 53bf130b1cdd ("libfdt: simplify
>> fdt_node_check_compatible()"). This adds the following commits from
>> upstream:
>>
>> 53bf130 libfdt: simplify fdt_node_check_compatible()
>> c9d9121 Warn on node name unit-address presence/absence mismatch
>> 2e53f9d Catch unsigned 32bit overflow when parsing flattened device tree offsets
>>
>> Signed-off-by: Rob Herring <robh@kernel.org>
>> ---
>> As usual, this is just an automated copy of upstream dtc into the kernel
>> tree. The changeset is small enough that I have left it here.
>>
>> The main reason for this sync is to pick-up the new unit-address
>> warnings.
>
> I gave this a try. Obviously it finds many abuses that should be fixed.
>
> However, I'm wondering about the following, where the unit-address is just
> used to distinguish between multiple instances:
>
>     Warning (unit_address_vs_reg): Node /cache-controller@0 has a unit
> name, but no reg property
>         compatible = "cache";

Just add a reg property. The values should probably match the MPIDR in
some way (e.g. 0 and 100).

>     Warning (unit_address_vs_reg): Node /regulator@1 has a unit name,
> but no reg property
>         compatible = "regulator-fixed"

Regulators are oddball in that the node names are generally supposed
to be the regulator name not generic.

>     Warning (unit_address_vs_reg): Node /i2c@2 has a unit name, but no
> reg property
>         compatible = "i2c-gpio"

You all should have all the on-chip devices under a simple-bus, then
you would not have this namespace collision here. Still you could have
2 i2c-gpio devices. We can add reg in those cases.

>
> How should these be fixed?
>
> BTW, there seems to be a missing dependency of the DTBs on the dtc itself.
> Applying your patch and running "make dtbs" didn't rebuilt any DTBs.

Should probably fix, but It is rare that that would actually matter.

Rob

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH] scripts/dtc: Update to upstream version 53bf130b1cdd Rob Herring <robh@kernel.org> - 2016-03-04 16:20 +0100
  Re: [PATCH] scripts/dtc: Update to upstream version 53bf130b1cdd Geert Uytterhoeven <geert@linux-m68k.org> - 2016-03-07 12:30 +0100
    Re: [PATCH] scripts/dtc: Update to upstream version 53bf130b1cdd Rob Herring <robh@kernel.org> - 2016-03-08 09:10 +0100
      Re: [PATCH] scripts/dtc: Update to upstream version 53bf130b1cdd Geert Uytterhoeven <geert@linux-m68k.org> - 2016-03-08 09:20 +0100
  Re: [PATCH] scripts/dtc: Update to upstream version 53bf130b1cdd Olof Johansson <olof@lixom.net> - 2016-03-08 00:20 +0100
    Re: [PATCH] scripts/dtc: Update to upstream version 53bf130b1cdd Rob Herring <robh@kernel.org> - 2016-03-08 08:40 +0100
      Re: [PATCH] scripts/dtc: Update to upstream version 53bf130b1cdd Olof Johansson <olof@lixom.net> - 2016-03-08 17:30 +0100

csiph-web