From: Greg Ungerer <gerg@uclinux.org>
To: Fugang Duan <fugang.duan@nxp.com>, Fabio Estevam <festevam@gmail.com>
Cc: Troy Kisky <troy.kisky@boundarydevices.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] net: fec: stop the "rcv is not +last, " error messages
Date: Thu, 31 Mar 2016 11:59:14 +1000 [thread overview]
Message-ID: <56FC8472.6010005@uclinux.org> (raw)
In-Reply-To: <VI1PR0401MB1855458E0B31502D1C112AF6FF990@VI1PR0401MB1855.eurprd04.prod.outlook.com>
Hi Andy,
On 31/03/16 11:41, Fugang Duan wrote:
> From: Fabio Estevam <festevam@gmail.com> Sent: Thursday, March 31, 2016 2:37 AM
>> To: Greg Ungerer <gerg@uclinux.org>
>> Cc: Troy Kisky <troy.kisky@boundarydevices.com>; netdev@vger.kernel.org
>> Subject: Re: [PATCH] net: fec: stop the "rcv is not +last, " error messages
>>
>> Hi Greg,
>>
>> On Wed, Mar 30, 2016 at 12:24 AM, Greg Ungerer <gerg@uclinux.org> wrote:
>>> Hi Troy,
>>>
>>> Commit 55cd48c8 ('net: fec: stop the "rcv is not +last, " error
>>> messages') adds a write to a register that is not present in all
>>> implementations of the FEC hardware module. None of the ColdFire SoC
>>> parts with the FEC module have the FTRL (0x1b0) register.
>>>
>>> Does this need a quirk flag to key access to this register of?
>>> Or can you piggyback on the FEC_QUIRK_HAS_RACC flag?
>>
>> Would the change below work on Coldfire?
>>
>> --- a/drivers/net/ethernet/freescale/fec_main.c
>> +++ b/drivers/net/ethernet/freescale/fec_main.c
>> @@ -943,8 +943,8 @@ fec_restart(struct net_device *ndev)
>> else
>> val &= ~FEC_RACC_OPTIONS;
>> writel(val, fep->hwp + FEC_RACC);
>> - }
>> writel(PKT_MAXBUF_SIZE, fep->hwp + FEC_FTRL);
>> + }
>> #endif
>>
>> /*
>
> Fabio, we cannot do it like this that may cause confused for the quirk flag "FEC_QUIRK_HAS_RACC".
>
>
> Hi, Greg,
>
> The header file fec.h define the FEC_FTRL as below, if ColdFire SoC has no this register, we may remove the define in here and define the register according to SOC type. For example, it is ColdFire Soc, define it as 0xFFF. Is it feasible ?
>
> #if defined(CONFIG_M523x) || defined(CONFIG_M527x) || defined(CONFIG_M528x) || \
> defined(CONFIG_M520x) || defined(CONFIG_M532x) || defined(CONFIG_ARM)
> ...
> #define FEC_FTRL 0x1b0
> ...
> #else
> ...
> #endif
Sure you could do that. But... you still have to be careful
with references to it in fec_main.c. They will need be conditional
on existence of FEC_FTRL, otherwise you break compilation.
Even if you define it to some bogus value we still don't
want the code actually writing to it.
Regards
Greg
next prev parent reply other threads:[~2016-03-31 1:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 3:24 [PATCH] net: fec: stop the "rcv is not +last, " error messages Greg Ungerer
2016-03-30 17:04 ` Troy Kisky
2016-03-30 18:37 ` Fabio Estevam
2016-03-31 1:17 ` Greg Ungerer
2016-03-31 10:58 ` Fabio Estevam
2016-03-31 1:41 ` Fugang Duan
2016-03-31 1:59 ` Greg Ungerer [this message]
2016-03-31 10:56 ` Fabio Estevam
2016-04-01 1:37 ` Fugang Duan
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=56FC8472.6010005@uclinux.org \
--to=gerg@uclinux.org \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=troy.kisky@boundarydevices.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;
as well as URLs for NNTP newsgroup(s).