From: Fenghua Yu <fenghua.yu@intel.com>
To: 'Guanjun' <guanjun@linux.alibaba.com>, <dave.jiang@intel.com>,
<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<vkoul@kernel.org>, <tony.luck@intel.com>
Cc: <jing.lin@intel.com>, <ashok.raj@intel.com>,
<sanjay.k.kumar@intel.com>, <megha.dey@intel.com>,
<jacob.jun.pan@intel.com>, <yi.l.liu@intel.com>,
<tglx@linutronix.de>
Subject: Re: [PATCH v1 2/2] dmaengine: idxd: Fix the incorrect descriptions
Date: Mon, 30 Oct 2023 12:20:24 -0700 [thread overview]
Message-ID: <658133e5-922a-b05c-3cbd-cd967f406427@intel.com> (raw)
In-Reply-To: <20231029080049.1482701-3-guanjun@linux.alibaba.com>
Hi, Guanjun,
On 10/29/23 01:00, 'Guanjun' wrote:
> From: Guanjun <guanjun@linux.alibaba.com>
>
The subject may be changed to:
dmaengine: idxd: Fix incorrect descriptions for GRPWQCFG_OFFSET
> Fix the incorrect descriptions for the GRPCFG register.
> No functional changes
>
> Signed-off-by: Guanjun <guanjun@linux.alibaba.com>
> ---
> drivers/dma/idxd/registers.h | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/dma/idxd/registers.h b/drivers/dma/idxd/registers.h
> index 7b54a3939ea1..385a162a55f2 100644
> --- a/drivers/dma/idxd/registers.h
> +++ b/drivers/dma/idxd/registers.h
> @@ -440,12 +440,15 @@ union wqcfg {
> /*
> * This macro calculates the offset into the GRPCFG register
> * idxd - struct idxd *
> - * n - wq id
> - * ofs - the index of the 32b dword for the config register
> + * n - group id
> + * ofs - the index of the 64b qword for the config register
> *
> - * The WQCFG register block is divided into groups per each wq. The n index
> - * allows us to move to the register group that's for that particular wq.
> - * Each register is 32bits. The ofs gives us the number of register to access.
> + * The GRPCFG register block is divided into three different types, that
s/different types/sub-registers/
> + * includes GRPWQCFG, GRPENGCFG and GRPFLGCFG. The n index in each group
s/that includes/which are/
> + * allows us to move to the register group that's for that particular wq,
> + * engine or group flag.
s/that particular wq, engine or group flag./that contains the three
sub-registers/
> + * Each register is 64bits. And the ofs in GRPWQCFG gives us the number
> + * of register to access.
s/the number of register to access/the offset within the GRPCFG register
to access/
> */
> #define GRPWQCFG_OFFSET(idxd_dev, n, ofs) ((idxd_dev)->grpcfg_offset +\
> (n) * GRPCFG_SIZE + sizeof(u64) * (ofs))
Thanks.
-Fenghua
prev parent reply other threads:[~2023-10-30 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 8:00 [PATCH v1 0/2] Some fixes for idxd driver 'Guanjun'
2023-10-29 8:00 ` [PATCH v1 1/2] dmaengine: idxd: Protect int_handle field in hw descriptor 'Guanjun'
2023-10-30 15:58 ` Dave Jiang
2023-10-30 18:56 ` Fenghua Yu
2023-10-29 8:00 ` [PATCH v1 2/2] dmaengine: idxd: Fix the incorrect descriptions 'Guanjun'
2023-10-30 16:00 ` Dave Jiang
2023-10-30 19:20 ` Fenghua Yu [this message]
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=658133e5-922a-b05c-3cbd-cd967f406427@intel.com \
--to=fenghua.yu@intel.com \
--cc=ashok.raj@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=guanjun@linux.alibaba.com \
--cc=jacob.jun.pan@intel.com \
--cc=jing.lin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=megha.dey@intel.com \
--cc=sanjay.k.kumar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vkoul@kernel.org \
--cc=yi.l.liu@intel.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