From: Tom Rix <trix@redhat.com>
To: Xu Yilun <yilun.xu@intel.com>, Lee Jones <lee.jones@linaro.org>
Cc: broonie@kernel.org, linux-kernel@vger.kernel.org,
matthew.gerlach@linux.intel.com, russell.h.weight@intel.com,
lgoncalv@redhat.com, hao.wu@intel.com
Subject: Re: [PATCH v3 0/2] add regmap-spi-avmm & Intel Max10 BMC chip support
Date: Tue, 18 Aug 2020 07:40:45 -0700 [thread overview]
Message-ID: <5a2d4761-e800-bfb6-d67b-8740b8039ecc@redhat.com> (raw)
In-Reply-To: <20200818083647.GE22873@yilunxu-OptiPlex-7050>
Yilun,
I was looking at the tx side a bit and think the padding function could be moved into the pkt/phy function. The pky/phy function already is looking for the eop's so reuse it and remove the search for eop and exchange the loops that do char moving and padding to mem* functions. The logic is something like.
if (tb == tb_end - 1 && !eop_inserted) {
*pb = PKT_EOP;
p_eop = pb;
...
dst_pb = &br->phy_buf[aligned_len];
size_t s = pb - p_eop + 1;
/* move EOP and bytes after EOP to the end of aligned size */
memmove(dst_pb - s, p_eop, s);
/* fill the hole with PHY_IDLEs */
memset(p_eop, PHY_IDLE, aligned_len - br->phy_len);
/* update the phy data length */
Tom
On 8/18/20 1:36 AM, Xu Yilun wrote:
> On Mon, Aug 17, 2020 at 10:12:52AM +0100, Lee Jones wrote:
>> On Mon, 17 Aug 2020, Xu Yilun wrote:
>>
>>> Hi Brown & jones:
>>>
>>> I tried to refacor the regmap code and add comments in this patchset. I
>>> made big changes to the rx flow and remove some tricky parts in it.
>>>
>>> Would it be more understandable than last version? I'm expecting your
>>> comments on it when you have time, thanks in advance.
>> Just resubmit please. We can review the code itself.
> Ok. I'll rebase it to 5.9-rc1 and resubmit it.
>
> Thanks,
> Yilun
>
>> --
>> Lee Jones [李琼斯]
>> Senior Technical Lead - Developer Services
>> Linaro.org │ Open source software for Arm SoCs
>> Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-08-18 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 8:00 [PATCH v3 0/2] add regmap-spi-avmm & Intel Max10 BMC chip support Xu Yilun
2020-08-05 8:00 ` [PATCH v3 1/2] regmap: add Intel SPI Slave to AVMM Bus Bridge support Xu Yilun
2020-08-05 8:00 ` [PATCH v3 2/2] mfd: intel-m10-bmc: add Max10 BMC chip support for Intel FPGA PAC Xu Yilun
2020-08-17 8:24 ` [PATCH v3 0/2] add regmap-spi-avmm & Intel Max10 BMC chip support Xu Yilun
2020-08-17 9:12 ` Lee Jones
2020-08-18 8:36 ` Xu Yilun
2020-08-18 14:40 ` Tom Rix [this message]
2020-08-18 15:07 ` Xu Yilun
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=5a2d4761-e800-bfb6-d67b-8740b8039ecc@redhat.com \
--to=trix@redhat.com \
--cc=broonie@kernel.org \
--cc=hao.wu@intel.com \
--cc=lee.jones@linaro.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=russell.h.weight@intel.com \
--cc=yilun.xu@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