Hi,
On Sun, May 15, 2022 at 11:57 PM Krzysztof Kozlowski
<krzysztof.kozlowski@xxxxxxxxxx> wrote:
>
> On 13/05/2022 18:59, Douglas Anderson wrote:
> > This documents how many Chromebooks pick the device tree that will be
> > passed to the OS and can help understand the revisions / skus listed
> > as the top-level "compatible" in many Chromebooks.
> >
> > Signed-off-by: Douglas Anderson <dianders@xxxxxxxxxxxx>
> > ---
> >
> > Changes in v2:
> > - ("Document how Chromebooks with depthcharge boot") new for v2.
> >
> > .../devicetree/chromebook-boot-flow.rst | 63 +++++++++++++++++++
> > 1 file changed, 63 insertions(+)
> > create mode 100644 Documentation/devicetree/chromebook-boot-flow.rst
>
> This is not a Devicetree (generic) document, so it is not the best place
> for it. Maybe regular vendor place, e.g . Documentation/arm/google/ ?
I can put it there. ...but taking your two pieces of advice together,
you're saying:
1. Don't add this under the devicetree directory.
2. Don't refer to this by URL but instead by a relative file path.
I can do both of those two things, but I always had it in my mind that
the device tree was supposed to be "Linux agnostic". In other words,
you could refer to Linux as one OS that boots with device tree, but I
thought that the device tree docs were supposed to stand on their own.
With the above two suggestions, it seems like an extra piece tieing
the two together and assuming that both Linux and device tree docs are
living in the same place.
In any case, I'm happy to do what you request but I just want to double-check.
-Doug
