From: Vinod Koul <vkoul@kernel.org>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: devicetree <devicetree@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: Reusing DTS from arm64 to arm
Date: Tue, 24 Nov 2020 11:14:56 +0530 [thread overview]
Message-ID: <20201124054456.GG8403@vkoul-mobl> (raw)
In-Reply-To: <CAGb2v67DpjMkcXoumQ=92wVovCqor37U7xroxsoh+BO6i7x8jg@mail.gmail.com>
Hello Chen-Yu,
On 24-11-20, 13:36, Chen-Yu Tsai wrote:
> Hi,
>
> On Tue, Nov 24, 2020 at 1:28 PM Vinod Koul <vkoul@kernel.org> wrote:
> >
> > Hello Olof, Rob,
> >
> > We have Qualcomm arm platform which uses PMIC PM8150B. This PMIC was
> > also used in SM8150 board and is already upstream [1] but in arm64.
> >
> > So, what is the guidance to share DTS files between 32 and 64 variants?
> > Does a solution already exist which I may not be aware of..?
> >
> > I can think of following options for this, in case we dont have a
> > solution:
> >
> > 1. Hack up arm include paths to also include arm64 path so that we can
> > share DTS
>
> These are already provided. See scripts/dtc/include-prefixes/ .
>
> So just put
>
> #include <arm64/qcom/pm8150b.dtsi>
>
> in your DTS and it should work?
It does work, thank you for pointing me to this
--
~Vinod
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-24 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 5:27 Reusing DTS from arm64 to arm Vinod Koul
2020-11-24 5:36 ` Chen-Yu Tsai
2020-11-24 5:44 ` Vinod Koul [this message]
2020-11-24 5:38 ` Baruch Siach
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=20201124054456.GG8403@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=wens@kernel.org \
/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