From: houlong wei <houlong.wei@mediatek.com>
To: "Bibby Hsieh (謝濟遠)" <Bibby.Hsieh@mediatek.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Nicolas Boichat" <drinkcat@chromium.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
srv_heupstream <srv_heupstream@mediatek.com>,
"Daoyuan Huang (黃道原)" <Daoyuan.Huang@mediatek.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Jassi Brar" <jassisinghbrar@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Daniel Kurtz" <djkurtz@chromium.org>,
houlong.wei@mediatek.com, "YT Shen (沈岳霆)" <Yt.Shen@mediatek.com>,
"CK Hu (胡俊光)" <ck.hu@mediatek.com>,
"Rob Herring" <robh+dt@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Ginny Chen (陳治傑)" <ginny.chen@mediatek.com>,
"Sascha Hauer" <kernel@pengutronix.de>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Jiaguang Zhang (张加广)" <Jiaguang.Zhang@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Dennis-YC Hsieh (謝宇哲)" <Dennis-YC.Hsieh@mediatek.com>
Subject: Re: [PATCH v11 09/12] soc: mediatek: cmdq: define the instruction struct
Date: Sun, 11 Aug 2019 00:38:01 +0800 [thread overview]
Message-ID: <1565455081.19079.36.camel@mhfsdcap03> (raw)
In-Reply-To: <1565453520.19079.17.camel@mhfsdcap03>
On Sun, 2019-08-11 at 00:12 +0800, houlong wei wrote:
> Hi Bibby, I have inline comment in function cmdq_pkt_write_mask().
>
> On Mon, 2019-07-29 at 15:01 +0800, Bibby Hsieh wrote:
> > Define an instruction structure for gce driver to append command.
> > This structure can make the client's code more readability.
> >
> > Signed-off-by: Bibby Hsieh <bibby.hsieh@mediatek.com>
> > Reviewed-by: CK Hu <ck.hu@mediatek.com>
> > ---
> > drivers/soc/mediatek/mtk-cmdq-helper.c | 103 +++++++++++++++--------
> > include/linux/mailbox/mtk-cmdq-mailbox.h | 2 +
> > 2 files changed, 72 insertions(+), 33 deletions(-)
> >
> > diff --git a/drivers/soc/mediatek/mtk-cmdq-helper.c b/drivers/soc/mediatek/mtk-cmdq-helper.c
> > index 7aa0517ff2f3..0886c4967ca4 100644
> > --- a/drivers/soc/mediatek/mtk-cmdq-helper.c
> > +++ b/drivers/soc/mediatek/mtk-cmdq-helper.c
> > @@ -9,12 +9,24 @@
> > #include <linux/mailbox_controller.h>
> > #include <linux/soc/mediatek/mtk-cmdq.h>
[...]
> >
> > int cmdq_pkt_write_mask(struct cmdq_pkt *pkt, u8 subsys,
> > u16 offset, u32 value, u32 mask)
> > {
> > + struct cmdq_instruction *inst;
> > u32 offset_mask = offset;
> > - int err = 0;
> >
> > if (mask != 0xffffffff) {
> > - err = cmdq_pkt_append_command(pkt, CMDQ_CODE_MASK, 0, ~mask);
> > + inst = cmdq_pkt_append_command(pkt);
> > + if (!inst)
> > + return -ENOMEM;
> > +
> > + inst->op = CMDQ_CODE_MASK;
> > + inst->mask = ~mask;
> > offset_mask |= CMDQ_WRITE_ENABLE_MASK;
> > }
> > - err |= cmdq_pkt_write(pkt, value, subsys, offset_mask);
> >
> > - return err;
> > + return cmdq_pkt_write(pkt, subsys, offset_mask, value);
We need add a type conversion here, (u8)offset_mask, for your new
function type. Er... it's better to remove local variable 'offset_mask'
and replace it with 'offset'.
> > }
[...]
_______________________________________________
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-08-10 16:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 7:00 [PATCH v11 00/12] support gce on mt8183 platform Bibby Hsieh
2019-07-29 7:00 ` [PATCH v11 01/12] dt-binding: gce: remove thread-num property Bibby Hsieh
2019-07-29 7:00 ` [PATCH v11 02/12] dt-binding: gce: add gce header file for mt8183 Bibby Hsieh
2019-07-29 7:00 ` [PATCH v11 03/12] dt-binding: gce: add binding for gce client reg property Bibby Hsieh
2019-08-16 22:06 ` Rob Herring
2019-07-29 7:00 ` [PATCH v11 04/12] mailbox: mediatek: cmdq: move the CMDQ_IRQ_MASK into cmdq driver data Bibby Hsieh
2019-07-29 7:00 ` [PATCH v11 05/12] mailbox: mediatek: cmdq: support mt8183 gce function Bibby Hsieh
2019-07-29 7:01 ` [PATCH v11 06/12] soc: mediatek: cmdq: clear the event in cmdq initial flow Bibby Hsieh
2019-07-29 7:01 ` [PATCH v11 07/12] soc: mediatek: cmdq: reorder the parameter Bibby Hsieh
2019-07-29 7:01 ` [PATCH v11 08/12] soc: mediatek: cmdq: change the type of input parameter Bibby Hsieh
2019-07-29 7:01 ` [PATCH v11 09/12] soc: mediatek: cmdq: define the instruction struct Bibby Hsieh
2019-08-10 16:12 ` houlong wei
2019-08-10 16:38 ` houlong wei [this message]
2019-07-29 7:01 ` [PATCH v11 10/12] soc: mediatek: cmdq: add polling function Bibby Hsieh
2019-07-29 7:01 ` [PATCH v11 11/12] soc: mediatek: cmdq: add cmdq_dev_get_client_reg function Bibby Hsieh
2019-08-10 16:18 ` houlong wei
2019-07-29 7:01 ` [PATCH v11 12/12] arm64: dts: add gce node for mt8183 Bibby Hsieh
2019-08-10 16:25 ` houlong wei
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=1565455081.19079.36.camel@mhfsdcap03 \
--to=houlong.wei@mediatek.com \
--cc=Bibby.Hsieh@mediatek.com \
--cc=Daoyuan.Huang@mediatek.com \
--cc=Dennis-YC.Hsieh@mediatek.com \
--cc=Jiaguang.Zhang@mediatek.com \
--cc=Yt.Shen@mediatek.com \
--cc=ck.hu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=drinkcat@chromium.org \
--cc=ginny.chen@mediatek.com \
--cc=jassisinghbrar@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=srv_heupstream@mediatek.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