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


Groups > linux.kernel > #1667373

Re: [PATCH v5 0/4] of: remove *phandle properties from expanded device tree

From Frank Rowand <frowand.list@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH v5 0/4] of: remove *phandle properties from expanded device tree
Date 2017-06-16 03:40 +0200
Message-ID <tSOoV-1JC-3@gated-at.bofh.it> (permalink)
References <tQHrz-34D-1@gated-at.bofh.it> <tSMZQ-YC-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 06/15/17 17:06, Benjamin Herrenschmidt wrote:
> On Fri, 2017-06-09 at 22:47 -0700, frowand.list@gmail.com wrote:
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> Remove "phandle" and "linux,phandle" properties from the internal
>> device tree.  The phandle will still be in the struct device_node
>> phandle field.
>>
>> This is to resolve the issue found by Stephen Boyd [1] when he changed
>> the type of struct property.value from void * to const void *.  As
>> a result of the type change, the overlay code had compile errors
>> where the resolver updates phandle values.
> 
> Piggy back on the powerpc breakage thread...
> 
> So various things in userspace will consume these. The main one is
> kexec which needs them to rebuild a fdt. So if you're going to do that
> you need to modify the sysfs code to expose a phandle attribute from
> the device node ->phandle.

Hi Ben,

Thanks for the comment.  My devicetree knowledge related to powerpc
is more limited than I would like, so any insights from you are
greatly appreciated.

/proc/device-tree is a documented ABI, so the patches do contain files
there for phandle.  (See the new function __of_add_phandle_sysfs() if
you want details.)  One difference from before is that if more than one of
"phandle", "linux,phandle", or "ibm,phandle" exist for a node, there will
only be one file "phandle" for the node under /proc/device-tree.  This
reflects the reality that the struct device_node phandle field has been
collapsing the three different properties into a single value.

For any interested parties, the current status (thanks to Guenter's
debugging efforts) is that the struct device_node type field is
NULL when it should contain a pointer to a type.  I am in the process
of setting up a qemu environment so I can debug the problem directly
instead of burdening Guenter with the extra work.  Rob is planning
to (or may have already) removed the patch series from the branch
that feeds into -next.

Thanks,

Frank

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


Thread

[PATCH v5 0/4] of: remove *phandle properties from expanded device tree frowand.list@gmail.com - 2017-06-10 07:50 +0200
  [PATCH v5 3/4] of: be consistent in form of file mode frowand.list@gmail.com - 2017-06-10 07:50 +0200
  [PATCH v5 1/4] of: remove *phandle properties from expanded device tree frowand.list@gmail.com - 2017-06-10 07:50 +0200
    Re: [PATCH v5 1/4] of: remove *phandle properties from expanded device tree Michael Ellerman <mpe@ellerman.id.au> - 2017-06-15 09:00 +0200
  [PATCH v5 4/4] of: detect invalid phandle in overlay frowand.list@gmail.com - 2017-06-10 07:50 +0200
  [PATCH v5 2/4] of: make __of_attach_node() static frowand.list@gmail.com - 2017-06-10 07:50 +0200
  Re: [PATCH v5 0/4] of: remove *phandle properties from expanded  device tree Rob Herring <robh+dt@kernel.org> - 2017-06-14 00:10 +0200
  Re: [PATCH v5 0/4] of: remove *phandle properties from expanded  device tree Benjamin Herrenschmidt <benh@kernel.crashing.org> - 2017-06-16 02:10 +0200
    Re: [PATCH v5 0/4] of: remove *phandle properties from expanded  device tree Frank Rowand <frowand.list@gmail.com> - 2017-06-16 03:40 +0200

csiph-web