From: Doug Anderson <dianders@chromium.org>
To: Rob Herring <robh@kernel.org>
Cc: "Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
linux-samsung-soc@vger.kernel.org, "Roy Luo" <royluo@google.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Chen-Yu Tsai" <wenst@chromium.org>,
"Julius Werner" <jwerner@chromium.org>,
"William McVicker" <willmcvicker@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: arm: google: Add bindings for frankel/blazer/mustang
Date: Tue, 18 Nov 2025 14:47:42 -0800 [thread overview]
Message-ID: <CAD=FV=ULAvZ3CkSta7bA5ANhen83RJZ2=qczvPM-gC-_eqTfeg@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=W5=AVYeZvz_LxC2-7U83yErY0JGc2nZQ37Pf54FH8++A@mail.gmail.com>
Hi,
On Fri, Nov 14, 2025 at 10:53 AM Doug Anderson <dianders@chromium.org> wrote:
>
> > I think it would help if you described what you want to do more
> > generically rather than mixed in with "add a new SoC" and send that to
> > devicetree-spec and perhaps boot-architecture lists. Present the
> > problem, not just the solution.
>
> Sure, though I think the problem has been discussed at length in a
> number of situations before (mailing lists, conferences, etc). Each
> time it seems like it ends up being too complicated and folks hit dead
> ends and stop trying to upstream. Downstream just keeps doing their
> own downstream things because there are tons of people all hitting the
> same problem and there's no upstream solution.
>
> IMO we need to start moving into the realm of solutions. I understand
> that upstream doesn't want to accept some poorly-thought-out scheme
> that will cause long-term grief, but at some point it feels like we
> need to accept something that's "not too bad" so that we can at least
> iterate from there.
>
> After re-reading all the above, it feels like we're not that far from
> a solution, though perhaps you'll read it all and say that you hate it
> and that we're not as close as I thought. ;-)
I've taken your advice and posted to the devicetree-spec and
boot-architecture lists. To connect anyone that was following this
conversation, see:
https://lore.kernel.org/r/CAD=FV=Ux7nGFnYEyX0cUL-9__BKnTYc+kAJjkF458ZnFS7zoJA@mail.gmail.com
I've done my best to include all the concerns / points that were
brought up in this thread.
-Doug
next prev parent reply other threads:[~2025-11-18 22:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 19:22 [PATCH 0/4] arm64: google: Introduce frankel, blazer, and mustang boards Douglas Anderson
2025-11-11 19:22 ` [PATCH 1/4] dt-bindings: arm: google: Add bindings for frankel/blazer/mustang Douglas Anderson
2025-11-12 7:58 ` Krzysztof Kozlowski
2025-11-12 19:19 ` Doug Anderson
2025-11-13 7:23 ` Krzysztof Kozlowski
2025-11-13 16:23 ` Doug Anderson
2025-11-13 16:34 ` Krzysztof Kozlowski
2025-11-13 17:16 ` Doug Anderson
2025-11-13 17:43 ` Krzysztof Kozlowski
2025-11-13 18:04 ` Doug Anderson
2025-11-13 18:41 ` Doug Anderson
2025-11-14 9:26 ` Krzysztof Kozlowski
2025-11-14 15:54 ` Rob Herring
2025-11-13 2:27 ` Rob Herring
2025-11-13 3:29 ` Doug Anderson
2025-11-14 15:20 ` Rob Herring
2025-11-14 18:53 ` Doug Anderson
2025-11-18 22:47 ` Doug Anderson [this message]
2025-11-11 19:22 ` [PATCH 2/4] dt-bindings: serial: snps-dw-apb-uart: Add "google,lga-uart" Douglas Anderson
2025-11-12 7:59 ` Krzysztof Kozlowski
2025-11-11 19:22 ` [PATCH 3/4] arm64: dts: google: Add dts directory for Google-designed silicon Douglas Anderson
2025-11-12 8:10 ` Krzysztof Kozlowski
2025-11-12 12:26 ` Peter Griffin
2025-11-12 12:36 ` Linus Walleij
2025-11-12 12:43 ` Peter Griffin
2025-11-11 19:22 ` [PATCH 4/4] arm64: dts: google: Add initial dts for frankel, blazer, and mustang Douglas Anderson
2025-11-12 8:14 ` Krzysztof Kozlowski
2025-11-12 9:35 ` Chen-Yu Tsai
2025-11-12 9:48 ` Krzysztof Kozlowski
2025-11-12 20:59 ` Doug Anderson
2025-11-17 6:43 ` Chen-Yu Tsai
2025-11-17 6:55 ` Krzysztof Kozlowski
2025-11-17 7:01 ` Chen-Yu Tsai
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='CAD=FV=ULAvZ3CkSta7bA5ANhen83RJZ2=qczvPM-gC-_eqTfeg@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jwerner@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=royluo@google.com \
--cc=tudor.ambarus@linaro.org \
--cc=wenst@chromium.org \
--cc=willmcvicker@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).