From: huangchenghai <huangchenghai2@huawei.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
<linux-crypto@vger.kernel.org>, <shenyang39@huawei.com>,
<liulongfang@huawei.com>, <qianweili@huawei.com>
Subject: Re: [PATCH 2/2] crypto: hisilicon/zip - optimize the address offset of the reg query function
Date: Fri, 31 May 2024 18:09:03 +0800 [thread overview]
Message-ID: <f1febadb-4cbd-4278-a3b0-dbb93d5af212@huawei.com> (raw)
In-Reply-To: <ZlmZh5d8RDo3C-HS@gondor.apana.org.au>
在 2024/5/31 17:33, Herbert Xu 写道:
> On Mon, May 06, 2024 at 07:59:53PM +0800, Chenghai Huang wrote:
>> @@ -807,6 +786,18 @@ static int hisi_zip_regs_show(struct seq_file *s, void *unused)
>>
>> DEFINE_SHOW_ATTRIBUTE(hisi_zip_regs);
>>
>> +static void __iomem *get_zip_core_addr(struct hisi_qm *qm, int core_num)
>> +{
>> + u32 zip_comp_core_num = qm->cap_tables.dev_cap_table[ZIP_CLUSTER_COMP_NUM_CAP_IDX].cap_val;
>> +
>> + if (core_num < zip_comp_core_num)
>> + return qm->io_base + HZIP_CORE_DFX_BASE +
>> + (core_num + 1) * HZIP_CORE_ADDR_INTRVL;
>> +
>> + qm->io_base + HZIP_CORE_DFX_DECOMP_BASE +
>> + (core_num - zip_comp_core_num) * HZIP_CORE_ADDR_INTRVL;
>> +}
>> +
> This doesn't even build.
I'm so sorry, I forgot to build it. I'll build and verify it carefully next time.
The second version will be corrected and send soon.
Thanks,
ChengHai
prev parent reply other threads:[~2024-05-31 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 11:59 [PATCH 0/2] crypto: hisilicon - adjust vf configuration sequence and optimize zip reg offset Chenghai Huang
2024-05-06 11:59 ` [PATCH 1/2] crypto: hisilicon/qm - adjust the internal processing sequence of the vf enable and disable Chenghai Huang
2024-05-06 11:59 ` [PATCH 2/2] crypto: hisilicon/zip - optimize the address offset of the reg query function Chenghai Huang
2024-05-31 9:33 ` Herbert Xu
2024-05-31 10:09 ` huangchenghai [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=f1febadb-4cbd-4278-a3b0-dbb93d5af212@huawei.com \
--to=huangchenghai2@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=qianweili@huawei.com \
--cc=shenyang39@huawei.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
all inboxes | Powered by JetHome®