All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan@gerhold.net>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
	Stephan Gerhold <stephan.gerhold@kernkonzept.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Sireesh Kodali <sireeshkodali1@gmail.com>,
	Luca Weiss <luca@z3ntu.xyz>,
	linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/5] dt-bindings: remoteproc: qcom,q6v5: Move MSM8916 to schema
Date: Tue, 26 Jul 2022 19:19:18 +0200	[thread overview]
Message-ID: <YuAh/ahbNiiQL5Ge@gerhold.net> (raw)
In-Reply-To: <27b0d451-4cef-cfc3-c6ae-3bb6cb448083@linaro.org>

On Sat, Jul 23, 2022 at 10:41:53PM +0200, Krzysztof Kozlowski wrote:
> On 21/07/2022 22:02, Stephan Gerhold wrote:
> > What remains is maybe:
> > 
> >   - "qcom,smem-states", which is already used in several other schemas
> >     and could be possibly defined together with #qcom,smem-state-cells
> >     in some generic schema(?)
> > 
> >   - "qcom,halt-regs", "firmware-name", "smd-edge" are used by different
> >     Qualcomm remoteproc drivers, so they could possibly be defined in
> >     some common "qcom-remoteproc.yaml" schema(?)
> 
> smd-edge and glink is already in remoteproc/qcom,smd-edge.yaml
> qcom,glink-edge.yaml
> 

Yep, I'm actually using it already in this patch. I think what I meant
is that the smd-edge property $ref could be already defined in a common
"qcom-remoteproc.yaml" schema and inherited via allOf, since all the
qcom remoteprocs should have either a smd-edge or glink-edge.

But all in all I'm still unsure which "common properties" Rob is
referring to here, in which file to place them, and if this is worth it
at all for the few I have listed above... :-)

Thanks,
Stephan

  reply	other threads:[~2022-07-26 17:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 14:03 [PATCH v2 0/5] remoteproc: qcom_q6v5_mss: Add MSM8909 Stephan Gerhold
2022-07-18 14:03 ` [PATCH v2 1/5] arm64: dts: qcom: msm8916: Drop MSS fallback compatible Stephan Gerhold
2022-07-18 14:03 ` [PATCH v2 2/5] dt-bindings: remoteproc: qcom,q6v5: Move MSM8916 to schema Stephan Gerhold
2022-07-18 22:03   ` Rob Herring
2022-07-20 22:46   ` Rob Herring
2022-07-21 20:02     ` Stephan Gerhold
2022-07-23 20:41       ` Krzysztof Kozlowski
2022-07-26 17:19         ` Stephan Gerhold [this message]
2022-07-18 14:03 ` [PATCH v2 3/5] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MSM8974 Stephan Gerhold
2022-07-18 14:03 ` [PATCH v2 4/5] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MSM8909 Stephan Gerhold
2022-07-18 14:03 ` [PATCH v2 5/5] remoteproc: qcom_q6v5_mss: Add support for MSM8909 Stephan Gerhold
2022-10-18  3:15 ` (subset) [PATCH v2 0/5] remoteproc: qcom_q6v5_mss: Add MSM8909 Bjorn Andersson

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=YuAh/ahbNiiQL5Ge@gerhold.net \
    --to=stephan@gerhold.net \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=luca@z3ntu.xyz \
    --cc=mathieu.poirier@linaro.org \
    --cc=robh@kernel.org \
    --cc=sireeshkodali1@gmail.com \
    --cc=stephan.gerhold@kernkonzept.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.