From: Nishanth Menon <nm@ti.com>
To: Markus Schneider-Pargmann <msp@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Vibhore Vardhan <vibhore@ti.com>,
Dhruva Gole <d-gole@ti.com>, Akashdeep Kaur <a-kaur@ti.com>
Subject: Re: [PATCH v10 3/4] firmware: ti_sci: Introduce Power Management Ops
Date: Thu, 29 Aug 2024 13:05:19 -0500 [thread overview]
Message-ID: <20240829180519.bftb7qxh4oj65oew@postnasal> (raw)
In-Reply-To: <rowimkyghjzuwt5hmwgl24oyyyjpth2zpvljc2mnyp5h5o7fyg@tdsdtsvwxfbx>
On 10:47-20240829, Markus Schneider-Pargmann wrote:
[...]
> Thanks for explaining. So should I add the header already with this
> series although it is unused right now, or should we add it together
> with the first actual user later on, so there is no unused header in the
> meantime?
Thinking deeper: we have two options:
a) dt bindings update with the property without knowing how the driver
changes will be accepted or not.
b) drop the header changes for the macros.
I think (a) at this point is risky given the driver usage model is
un-clear - the APIs are abstract enough to be used in any way of choice,
but we do not want to be stuck with binding that then has to be
backward-forward compatible fixup..
So. (b) is better approach, IMHO..
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-08-29 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 15:39 [PATCH v10 0/4] firmware: ti_sci: Introduce system suspend support Kevin Hilman
2024-08-14 15:39 ` [PATCH v10 1/4] firmware: ti_sci: Add support for querying the firmware caps Kevin Hilman
2024-08-26 14:46 ` Nishanth Menon
2024-08-14 15:39 ` [PATCH v10 2/4] firmware: ti_sci: Add system suspend and resume call Kevin Hilman
2024-08-26 16:34 ` Nishanth Menon
2024-08-14 15:39 ` [PATCH v10 3/4] firmware: ti_sci: Introduce Power Management Ops Kevin Hilman
2024-08-20 8:20 ` Akashdeep Kaur
2024-08-26 16:43 ` Nishanth Menon
2024-08-28 19:54 ` Markus Schneider-Pargmann
2024-08-29 3:24 ` Nishanth Menon
2024-08-29 8:47 ` Markus Schneider-Pargmann
2024-08-29 18:05 ` Nishanth Menon [this message]
2024-08-14 15:39 ` [PATCH v10 4/4] firmware: ti_sci: add CPU latency constraint management Kevin Hilman
2024-08-20 8:03 ` [PATCH v10 0/4] firmware: ti_sci: Introduce system suspend support Dhruva Gole
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=20240829180519.bftb7qxh4oj65oew@postnasal \
--to=nm@ti.com \
--cc=a-kaur@ti.com \
--cc=d-gole@ti.com \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=ssantosh@kernel.org \
--cc=vibhore@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