From: Sudeep Holla <sudeep.holla@arm.com>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>,
linux-kernel@vger.kernel.org,
Bo Zhang <bozhang.zhang@broadcom.com>,
Jim Quinlan <james.quinlan@broadcom.com>,
Volodymyr Babchuk <volodymyr_babchuk@epam.com>,
Gaku Inami <gaku.inami.xh@renesas.com>,
aidapala@qti.qualcomm.com, pajay@qti.qualcomm.com,
Souvik Chakravarty <Souvik.Chakravarty@arm.com>,
wesleys@xilinx.com, Felix Burton <fburton@xilinx.com>,
Saeed Nowshadi <saeed.nowshadi@xilinx.com>,
Ionela Voinescu <Ionela.Voinescu@arm.com>,
Chris Redpath <Chris.Redpath@arm.com>,
Quentin Perret <Quentin.Perret@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 2/5] firmware: arm_scmi: Make use SCMI v2.0 fastchannel for performance protocol
Date: Mon, 5 Aug 2019 14:28:33 +0100 [thread overview]
Message-ID: <20190805132833.GC627@e107155-lin> (raw)
In-Reply-To: <CAN5uoS-dgtz55O+AAxEFkgtijpHj_-NSy7SkNRAkhEJN5v4PWA@mail.gmail.com>
On Mon, Aug 05, 2019 at 03:16:41PM +0200, Etienne Carriere wrote:
> On Fri, 26 Jul 2019 at 16:00, Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > SCMI v2.0 adds support for "FastChannel" which do not use a message
> > header as they are specialized for a single message.
> >
> > Only PERFORMANCE_LIMITS_{SET,GET} and PERFORMANCE_LEVEL_{SET,GET}
> > commands are supported over fastchannels. As they are optional, they
> > need to be discovered by PERFORMANCE_DESCRIBE_FASTCHANNEL command.
> > Further {LIMIT,LEVEL}_SET commands can have optional doorbell support.
> >
> > Add support for making use of these fastchannels.
> >
> > Cc: Ionela Voinescu <Ionela.Voinescu@arm.com>
> > Cc: Chris Redpath <Chris.Redpath@arm.com>
> > Cc: Quentin Perret <Quentin.Perret@arm.com>
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > ---
> > drivers/firmware/arm_scmi/perf.c | 104 +++++++++++++++++++++++++++++--
> > 1 file changed, 100 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/firmware/arm_scmi/perf.c b/drivers/firmware/arm_scmi/perf.c
> > index 6cce3e82e81e..b9144efbd6fb 100644
> > --- a/drivers/firmware/arm_scmi/perf.c
> > +++ b/drivers/firmware/arm_scmi/perf.c
> > @@ -8,6 +8,7 @@
> > #include <linux/bits.h>
> > #include <linux/of.h>
> > #include <linux/io.h>
> > +#include <linux/io-64-nonatomic-hi-lo.h>
> > #include <linux/platform_device.h>
> > #include <linux/pm_opp.h>
> > #include <linux/sort.h>
> > @@ -293,7 +294,42 @@ scmi_perf_describe_levels_get(const struct scmi_handle *handle, u32 domain,
> > return ret;
> > }
> >
> > -static int scmi_perf_limits_set(const struct scmi_handle *handle, u32 domain,
> > +#define SCMI_PERF_FC_RING_DB(doorbell, w) \
>
> Suggest to reformat into a macro style:
> #define SCMI_PERF_FC_RING_DB(doorbell, w) \
> do { \
> (...) \
> } while (0)
>
Sure I can try that.
> > +{ \
> > + u##w val = 0; \
> > + struct scmi_fc_db_info *db = doorbell; \
> > + \
> > + if ((db)->mask) \
>
> remove parentheses. I would say, could simply remove `if (db->mask)` here.
Ah, missed to drop this one. We can avoid reading the value if mask = 0,
so I prefer to keep it.
>
> > + val = ioread##w(db->addr) & db->mask; \
> > + iowrite##w((u##w)db->set | val, db->addr); \
> > +}
> > +
> > +static void scmi_perf_fc_ring_db(struct scmi_fc_db_info *db)
> > +{
> > + if (!db || !db->addr)
> > + return;
> > +
> > + if (db->width == 1)
> > + SCMI_PERF_FC_RING_DB(db, 8)
> > + else if (db->width == 2)
> > + SCMI_PERF_FC_RING_DB(db, 16)
> > + else if (db->width == 4)
> > + SCMI_PERF_FC_RING_DB(db, 32)
> > + else /* db->width == 8 */
> > +#ifdef CONFIG_64BIT
> > + SCMI_PERF_FC_RING_DB(db, 64)
> > +#else
> > + {
> > + u64 val = 0;
> > +
> > + if (db->mask)
> > + val = ioread64_hi_lo(db->addr) & db->mask;
> > + iowrite64_hi_lo(db->set, db->addr);
>
> Is `value` missing here?
> Why not using SCMI_PERF_FC_RING_DB(db, 64) here?
>
I am still using it. Just if CONFIG_64BIT is enabled and io{read,write}64
are defined. ARM32/MIPS and other 32-bit platform build might fail
otherwise. I don't want to restrict SCMI to 64-bit platforms only.
--
Regards,
Sudeep
next prev parent reply other threads:[~2019-08-05 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 13:59 [PATCH 0/5] firmware: arm_scmi: add SCMI v2.0 fastchannels and reset protocol support Sudeep Holla
2019-07-26 13:59 ` [PATCH 1/5] firmware: arm_scmi: Add discovery of SCMI v2.0 performance fastchannels Sudeep Holla
2019-07-26 13:59 ` [PATCH 2/5] firmware: arm_scmi: Make use SCMI v2.0 fastchannel for performance protocol Sudeep Holla
2019-08-05 13:16 ` Etienne Carriere
2019-08-05 13:28 ` Sudeep Holla [this message]
2019-07-26 13:59 ` [PATCH 3/5] dt-bindings: arm: Extend SCMI to support new reset protocol Sudeep Holla
2019-07-26 13:59 ` [PATCH 4/5] firmware: arm_scmi: Add RESET protocol in SCMI v2.0 Sudeep Holla
2019-07-26 13:59 ` [PATCH 5/5] reset: Add support for resets provided by SCMI Sudeep Holla
2019-07-29 9:59 ` Philipp Zabel
2019-07-29 10:34 ` Sudeep Holla
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=20190805132833.GC627@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=Chris.Redpath@arm.com \
--cc=Ionela.Voinescu@arm.com \
--cc=Quentin.Perret@arm.com \
--cc=Souvik.Chakravarty@arm.com \
--cc=aidapala@qti.qualcomm.com \
--cc=bozhang.zhang@broadcom.com \
--cc=etienne.carriere@linaro.org \
--cc=fburton@xilinx.com \
--cc=gaku.inami.xh@renesas.com \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pajay@qti.qualcomm.com \
--cc=peng.fan@nxp.com \
--cc=saeed.nowshadi@xilinx.com \
--cc=volodymyr_babchuk@epam.com \
--cc=wesleys@xilinx.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).