From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 1/2] sh_eth: fix *enum* RPADIR_BIT
Date: Tue, 26 Jun 2018 13:37:10 +0300 [thread overview]
Message-ID: <e9cd4d85-36ed-b829-ba7a-ccebec306f1d@cogentembedded.com> (raw)
In-Reply-To: <CAMuHMdXro+fWQtoURHeqC6APqmci60NiMn5JAF98xcLxrjLNEg@mail.gmail.com>
On 6/26/2018 10:25 AM, Geert Uytterhoeven wrote:
>> The *enum* RPADIR_BIT was declared in the commit 86a74ff21a7a ("net:
>> sh_eth: add support for Renesas SuperH Ethernet") adding SH771x support,
>> however the SH771x manual doesn't have the RPADIR register described and,
>> moreover, tells why the padding insertion must not be used. The newer SoC
>> manuals do have RPADIR documented, though with somewhat different layout --
>> update the *enum* according to these manuals...
>>
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> Thanks for your patch!
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
>> --- net-next.orig/drivers/net/ethernet/renesas/sh_eth.h
>> +++ net-next/drivers/net/ethernet/renesas/sh_eth.h
>> @@ -403,8 +403,7 @@ enum DESC_I_BIT {
>>
>> /* RPADIR */
>> enum RPADIR_BIT {
>> - RPADIR_PADS1 = 0x20000, RPADIR_PADS0 = 0x10000,
>> - RPADIR_PADR = 0x0003f,
>> + RPADIR_PADS = 0x1f0000, RPADIR_PADR = 0xffff,
>
> Perhaps add some comments?
>
> RPADIR_PADS = 0x1f0000; /* Padding Size (insert N bytes of padding) */
> RPADIR_PADR = 0xffff; /* Padding Slot (insert padding at byte N) */
It would be nice but inconsistent with what we do for the other registers...
>> };
>
> Note that none of the RPADIR enums are actually used.
I'd surely noted that. :-)
> Gr{oetje,eeting}s,
>
> Geert
>
MBR, Sergei
next prev parent reply other threads:[~2018-06-26 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 20:34 [PATCH 0/2] sh_eth: RPADIR related clean-ups Sergei Shtylyov
2018-06-25 20:36 ` [PATCH 1/2] sh_eth: fix *enum* RPADIR_BIT Sergei Shtylyov
2018-06-26 7:25 ` Geert Uytterhoeven
2018-06-26 10:37 ` Sergei Shtylyov [this message]
2018-06-25 20:37 ` [PATCH 2/2] sh_eth: remove sh_eth_cpu_data::rpadir_value Sergei Shtylyov
2018-06-26 7:25 ` Geert Uytterhoeven
2018-06-26 14:16 ` [PATCH 0/2] sh_eth: RPADIR related clean-ups David Miller
2018-06-26 15:42 ` [PATCH net-next] sh_eth: fix *enum* {A|M}PR_BIT Sergei Shtylyov
2018-06-26 16:18 ` Geert Uytterhoeven
2018-06-28 7:02 ` David Miller
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=e9cd4d85-36ed-b829-ba7a-ccebec306f1d@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.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