From: Sumit Garg <sumit.garg@linaro.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: u-boot@lists.denx.de, Michal Simek <michal.simek@amd.com>,
Tom Rini <trini@konsulko.com>,
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
"paulburton@kernel.org" <paulburton@kernel.org>,
Simon Glass <sjg@chromium.org>, Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>
Subject: Re: [PATCH 12/13] MIPS: boston: Migrate to OF_UPSTREAM
Date: Thu, 16 May 2024 17:40:17 +0530 [thread overview]
Message-ID: <CAFA6WYP_hrZ2g4i4kiOdnk_BkXkn_Cg7bD1_2a18T3GsC3rBaA@mail.gmail.com> (raw)
In-Reply-To: <0d2fd774-7f63-4b3b-abea-6dda6a9159cd@app.fastmail.com>
On Thu, 16 May 2024 at 17:29, Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:
>
>
>
> 在2024年5月14日五月 上午6:45，Sumit Garg写道：
> > Hi Jiaxun,
> >
> [...]
> >> @@ -0,0 +1,10 @@
> >> +// SPDX-License-Identifier: GPL-2.0+
> >> +
> >> +&plat_regs {
> >> + compatible = "img,boston-platform-regs", "syscon", "simple-mfd";
> >> + bootph-all;
> >> +};
> >> +
> >> +&clk_boston {
> >> + bootph-all;
> >> +};
> >
> > You can try to push these overrides to upstream DTS as well, so you
> > won't have to maintain them in U-Boot.
>
> Hi Sumit,
>
> Thanks for your comments! For the compatible override, I already sent
> patch to upstream. However, I have a question, Can we really do bootph-all
> in linux upstream?
Yes.
>
> I don't think it's documented in upstream dt bindings.
>
It has been documented as part of core schema DT bindings here [1].
[1] https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/bootph.yaml
-Sumit
next prev parent reply other threads:[~2024-05-16 12:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 18:12 [PATCH 00/13] MIPS: Boston: Various enhancements Jiaxun Yang
2024-05-13 18:12 ` [PATCH 01/13] pci: xilinx: Handle size of ecam region properly Jiaxun Yang
2024-05-13 18:12 ` [PATCH 02/13] pci: auto: Reduce bridge mem alignment boundary for boston Jiaxun Yang
2024-05-13 18:13 ` [PATCH 03/13] pci: Enable PCI_MAP_SYSTEM_MEMORY when ARCH_MAP_SYSMEM is not set Jiaxun Yang
2024-05-13 18:13 ` [PATCH 04/13] ahci: DMA addressing fixes Jiaxun Yang
2024-05-13 18:13 ` [PATCH 05/13] ahci: dwc_ahsata: Generalize the driver Jiaxun Yang
2024-05-13 18:13 ` [PATCH 06/13] MIPS: Provide dummy acpi_table.h Jiaxun Yang
2024-05-13 18:13 ` [PATCH 07/13] MIPS: boston: Imply various options Jiaxun Yang
2024-05-13 18:13 ` [PATCH 08/13] MIPS: boston: Provide default env vars Jiaxun Yang
2024-05-13 18:13 ` [PATCH 09/13] syscon: Probe device first in syscon_get_regmap Jiaxun Yang
2024-05-14 14:50 ` Jonas Karlman
2024-05-15 0:12 ` Jiaxun Yang
2024-05-15 6:28 ` Jonas Karlman
2024-05-13 18:13 ` [PATCH 10/13] clk: boston: Allow to get regmap from parent device Jiaxun Yang
2024-05-13 18:13 ` [PATCH 11/13] dts/upstream: Add Makefile for MIPS Jiaxun Yang
2024-05-14 5:38 ` Sumit Garg
2024-05-13 18:13 ` [PATCH 12/13] MIPS: boston: Migrate to OF_UPSTREAM Jiaxun Yang
2024-05-14 5:45 ` Sumit Garg
2024-05-16 11:58 ` Jiaxun Yang
2024-05-16 12:10 ` Sumit Garg [this message]
2024-05-13 18:13 ` [PATCH 13/13] mailmap: Update email for Paul Burton Jiaxun Yang
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=CAFA6WYP_hrZ2g4i4kiOdnk_BkXkn_Cg7bD1_2a18T3GsC3rBaA@mail.gmail.com \
--to=sumit.garg@linaro.org \
--cc=daniel.schwierzeck@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=lukma@denx.de \
--cc=michal.simek@amd.com \
--cc=paulburton@kernel.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).