On Mon, Aug 06, 2018 at 12:31:57PM -0600, Rob Herring wrote: > On Mon, Aug 6, 2018 at 11:50 AM Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote: > > > > > > While the "device_type" property is still used and supported, it is > > deprecated so it should be removed from examples in the documentation. > > There is no value in encouraging developers to keep using that > > property, so just quietly disappear it from examples, but leave its > > explanation in the spec. > > > > Signed-off-by: Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> > > > > --- > > > > according to the spec, that property is still marginally acceptable > > for memory and cpu nodes, but it really has no place being used for > > any other types of nodes. > > It's not just acceptable, but it is still required. It is also > required for PCI bridges. So, cpu nodes could probably be identified by location under /cpus, but there's not really a good way of identifying memory nodes other than device_type. PCI bridges shouldn't need it, since they should already have "compatible" properties describing the particular bridge model. > > I'm not sure if Linux and other client programs still have > dependencies on device_type, but we'd need to remove those first. Then > make it optional in the spec, remove from dts files (some time later > to avoid breaking new dtb with old kernel), and then finally remove > from the spec. > > Rob -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Attachment:
signature.asc
Description: PGP signature
