From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Lokesh Vutla <lokeshvutla@ti.com>, Sekhar Nori <nsekhar@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 2/5] dt-bindings: ti_sci_pm_domains: Add support for exclusive and shared access
Date: Thu, 11 Apr 2019 07:34:07 -0700 [thread overview]
Message-ID: <20190411143407.GO2839@atomide.com> (raw)
In-Reply-To: <67537564-c503-8a2a-9f48-26ebca0661ab@ti.com>
* Tero Kristo <t-kristo@ti.com> [190410 15:39]:
> On 10/04/2019 16:15, Lokesh Vutla wrote:
> > Well Ill put it this way. This flag describes that the requested device is a
> > shared device across multiple hosts :)
>
> But that is pure software config, right? Depends on the software design
> choices made, which host is going to use which resource. Personally I don't
> think this justifies a DT binding, but I might be wrong. I'll let Rob
> comment on this.
I agree. It's best to stick to basics with the device tree bindings
and not put any software flags there.
You can configure things on init in the device driver based on
compatible and soc_device_match().
Regards,
Tony
_______________________________________________
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:[~2019-04-11 14:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 5:37 [PATCH v3 0/5] soc: ti: k3-am654: Allow for exclusive and shared device requests Lokesh Vutla
2019-04-10 5:37 ` [PATCH v3 1/5] firmware: ti_sci: Allow for device shared and exclusive requests Lokesh Vutla
2019-04-10 5:37 ` [PATCH v3 2/5] dt-bindings: ti_sci_pm_domains: Add support for exclusive and shared access Lokesh Vutla
2019-04-10 8:04 ` Tero Kristo
2019-04-10 12:37 ` Lokesh Vutla
2019-04-10 12:49 ` Tero Kristo
2019-04-10 13:15 ` Lokesh Vutla
2019-04-10 15:38 ` Tero Kristo
2019-04-11 14:34 ` Tony Lindgren [this message]
2019-05-02 9:24 ` Tero Kristo
2019-06-11 12:34 ` Tero Kristo
2019-06-13 22:22 ` Rob Herring
2019-04-10 5:37 ` [PATCH v3 3/5] soc: ti: " Lokesh Vutla
2019-06-05 5:44 ` Lokesh Vutla
2019-04-10 5:37 ` [PATCH v3 4/5] soc: ti: ti_sci_pm_domains: Switch to SPDX Licensing Lokesh Vutla
2019-04-10 5:37 ` [PATCH v3 5/5] arm64: dts: ti: k3-am654: Update the power domain cells Lokesh Vutla
2019-05-29 8:58 ` [PATCH v3 0/5] soc: ti: k3-am654: Allow for exclusive and shared device requests Lokesh Vutla
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=20190411143407.GO2839@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.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).