From: Tom Rini <trini@konsulko.com>
To: Andrey VOLKOV <andrey@volkov.fr>
Cc: Robert Marko <robert.marko@sartura.hr>,
Ramon Fried <rfried.dev@gmail.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/2] mach-snapdragon/mach-ipq40xx: fix, merge and refactoring
Date: Tue, 8 Nov 2022 10:20:15 -0500 [thread overview]
Message-ID: <20221108152015.GQ6335@bill-the-cat> (raw)
In-Reply-To: <20221106015258.217868-1-andrey@volkov.fr>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
On Sun, Nov 06, 2022 at 02:52:56AM +0100, Andrey VOLKOV wrote:
> Hi Robert, Tom,
>
> Updated patches are following, could you review/accept them?
>
> Le 04/11/2022 à 12:05, Robert Marko a écrit :
> > On Tue, Oct 25, 2022 at 3:31 AM Andrey Volkov<andrey@volkov.fr> wrote:
> >> SoC: qcom: Add missing Qualcomm's SOCs definitions to the arch KConfig
> >>
> >> From: Andrey VOLKOV<andrey@volkov.fr>
> >>
> >> Add APQ8016/APQ8096/QCS40X decls to the KConfig, convert SDM845 declaration to the hidden one (selected by target),
> >> and update mach-snapdragon/Makefile accordingly.
> >>
> >> Also move 'CONFIG_ARM64' choice to the new declarations, since 'Snapdragon' contains Cortex A7A members too.
> >>
> >> Signed-off-by: Andrey VOLKOV<andrey@volkov.fr>
> > I like this cleanup effort, however, can you rebase this to apply on the master?
> > I would like to use this as a base of moving IPQ40xx to use Linux DTS
> > and keep it in sync.
>
> It's nice idea, except that full blown DTS is huge enough (+some KiB at least),
> and i'm afraid it's an old, old story about failing to make it :(.
> Probably will be better if we will have some option that allowed to import and
> reuse DTS files directly from the kernel.
> Something like CONFIG_DTS_FILE_PATH/CONFIG_DTS_INCLUDES/...
>
> @Tom, any additional comments/objections?
>
> Btw As far as I remember, this topic (reuse kernel's DTS) has been discussed
> repeatedly since the mid-2000s, but I don't remember why it was not implemented yet.
Is the problem that the full DTS would make the resulting binary too
large to fit in some restricted and can't be changed easily space?
Generally we do want to keep the DTS files in-sync with the kernel.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-11-08 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 1:31 [PATCH 1/2] mach-snapdragon/mach-ipq40xx: fix, merge and refactoring Andrey Volkov
2022-11-04 11:05 ` Robert Marko
2022-11-06 1:52 ` Andrey VOLKOV
2022-11-08 15:20 ` Tom Rini [this message]
2022-11-08 15:23 ` Robert Marko
2022-11-08 15:26 ` Tom Rini
2022-11-06 1:52 ` [PATCH v2 1/2] SoC: qcom: Add missing Qualcomm's SOCs definitions to the arch KConfig Andrey VOLKOV
2022-11-06 1:52 ` [PATCH v2 2/2] ipq40xx/snapdragon: Merge the two, more than 90% overlapping Qualcomm's Snapdrgon based arches, into one: "mach-snapdragon" Andrey VOLKOV
2022-11-08 15:26 ` Robert Marko
2022-11-12 21:46 ` Andrey VOLKOV
2022-11-12 21:46 ` [PATCH v3 1/2] SoC: qcom: Add missing Qualcomm's SOCs definitions to the arch KConfig Andrey VOLKOV
2022-11-12 21:46 ` [PATCH v3 2/2] ipq40xx/snapdragon: Merge the two, more than 90% overlapping Qualcomm's Snapdrgon based arches, into one: "mach-snapdragon" Andrey VOLKOV
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=20221108152015.GQ6335@bill-the-cat \
--to=trini@konsulko.com \
--cc=andrey@volkov.fr \
--cc=rfried.dev@gmail.com \
--cc=robert.marko@sartura.hr \
--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