From: Christopher Covington <cov@codeaurora.org>
To: Florian Fainelli <f.fainelli@gmail.com>,
Gilad Avidov <gavidov@codeaurora.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Cc: sdharia@codeaurora.org, shankerd@codeaurora.org,
timur@codeaurora.org, gregkh@linuxfoundation.org,
vikrams@codeaurora.org
Subject: Re: [PATCH] net: emac: emac gigabit ethernet controller driver
Date: Tue, 15 Dec 2015 09:30:16 -0500 [thread overview]
Message-ID: <567023F8.80302@codeaurora.org> (raw)
In-Reply-To: <566F6F3D.5050004@gmail.com>
Hi Florian,
Thanks for taking the time to review this code. We'll probably take
additional time to review and implement most of your suggestions but I
was confused by your two comments below.
On 12/14/2015 08:39 PM, Florian Fainelli wrote:
> On 14/12/15 16:19, Gilad Avidov wrote:
>> +static void emac_mac_irq_enable(struct emac_adapter *adpt)
>> +{
>> + int i;
>> +
>> + for (i = 0; i < EMAC_NUM_CORE_IRQ; i++) {
>> + struct emac_irq *irq = &adpt->irq[i];
>> + const struct emac_irq_config *irq_cfg = &emac_irq_cfg_tbl[i];
>> +
>> + writel_relaxed(~DIS_INT, adpt->base + irq_cfg->status_reg);
>> + writel_relaxed(irq->mask, adpt->base + irq_cfg->mask_reg);
>> + }
>> +
>> + wmb(); /* ensure that irq and ptp setting are flushed to HW */
>
> Would not using writel() make the appropriate thing here instead of
> using _relaxed which has no barrier?
It appears to me that the barrier in writel() comes before the access
[1]. The barrier in this code comes after the accesses. In addition to
the ordering, if you're suggesting all writel_relaxed be switched out,
that would seem to add 7 unnecessary barriers, which could adversely
affect performance.
1. http://lxr.free-electrons.com/source/arch/arm64/include/asm/io.h#L130
> [snip]
>
>> + mta = readl_relaxed(adpt->base + EMAC_HASH_TAB_REG0 + (reg << 2));
>> + mta |= (0x1 << bit);
>> + writel_relaxed(mta, adpt->base + EMAC_HASH_TAB_REG0 + (reg << 2));
>> + wmb(); /* ensure that the mac address is flushed to HW */
>
> This is getting too much here, just use the correct I/O accessor for
> your platform, period.
Based on your previous comment, I'm guessing you're suggesting using
readl() and writel() here instead of *_relaxed and an explicit wmb().
Again it's not clear to me why swapping the barrier-access ordering and
adding an additional barrier would result in more correct code.
Thanks,
Christopher Covington
--
Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-12-15 14:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 0:19 [PATCH] net: emac: emac gigabit ethernet controller driver Gilad Avidov
2015-12-15 1:39 ` Florian Fainelli
2015-12-15 14:30 ` Christopher Covington [this message]
[not found] ` <567023F8.80302-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-12-15 14:50 ` Arnd Bergmann
2015-12-15 15:17 ` Timur Tabi
2015-12-15 15:41 ` Arnd Bergmann
2015-12-15 21:09 ` Timur Tabi
2015-12-15 21:55 ` Arnd Bergmann
2015-12-15 22:49 ` Gilad Avidov
2015-12-31 23:03 ` Rob Herring
[not found] ` <1450138740-32562-1-git-send-email-gavidov-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-12-16 0:15 ` Timur Tabi
2015-12-16 3:12 ` David Miller
2015-12-16 3:30 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2015-12-07 22:58 Gilad Avidov
2015-12-07 23:33 ` Felix Fietkau
2015-12-07 23:47 ` Gilad Avidov
2015-12-07 23:37 ` kbuild test robot
2015-12-09 20:09 ` Timur Tabi
2015-12-09 20:37 ` Fabio Estevam
2015-12-09 20:58 ` David Miller
2015-12-10 0:26 ` Gilad Avidov
2015-12-10 4:04 ` Timur Tabi
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=567023F8.80302@codeaurora.org \
--to=cov@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gavidov@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdharia@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=timur@codeaurora.org \
--cc=vikrams@codeaurora.org \
/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).