Netdev List
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <brandon.streiff@ni.com>, <harini.katakam@xilinx.com>,
	<Nicolas.Ferre@microchip.com>, <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<michal.simek@xilinx.com>, <harinikatakamlinux@gmail.com>
Subject: Re: [RFC PATCH] net: macb: Apply RXUBR workaround only to versions with errata
Date: Thu, 29 Nov 2018 10:00:22 +0000	[thread overview]
Message-ID: <88ca959b-6fed-8afb-e433-6a21e17ec067@microchip.com> (raw)
In-Reply-To: <5b550305-ff96-fdf6-883e-b6ae69ad3124@ni.com>



On 28.11.2018 23:09, Brandon Streiff wrote:
> On 11/23/2018 3:59 AM, Harini Katakam wrote:
>> +/* Errata mask bits */
>> +#define MACB_ERRATA_RXLOCKUP			0x00000001
>> +
>>  /* LSO settings */
>>  #define MACB_LSO_UFO_ENABLE			0x01
>>  #define MACB_LSO_TSO_ENABLE			0x02
>> @@ -1085,6 +1088,7 @@ struct macb_config {
>>  			    struct clk **rx_clk);
>>  	int	(*init)(struct platform_device *pdev);
>>  	int	jumbo_max_len;
>> +	u32	errata;
>>  };
>>  
>>  struct tsu_incr {
>> @@ -1214,6 +1218,8 @@ struct macb {
>>  
>>  	int	rx_bd_rd_prefetch;
>>  	int	tx_bd_rd_prefetch;
>> +
>> +	u32 errata;
>>  };
> 
> Hi Harini,
> 
> Could this be made into simpler by instead adding a caps bit, named
> (perhaps) MACB_CAPS_BUGGY_RXUBR or MACB_CAPS_NEEDS_RXUBR_RESETS or
> something?
> 
> That would save needing to add a new u32 field into the macb_config and
> macb structs (both of which already have this caps field).
> 

I avoid duplicating these fields from struct macb_config to struct macb I
would start to move macb_config part of struct macb as a const * member
(see [1]).


[1]
https://github.com/linux4sam/linux-at91/commit/8c588136189148d79c4078c55da2242a2ba2b8d3#diff-921c839dba439fd502a24aed0845dc9d

  parent reply	other threads:[~2018-11-29 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23  9:59 [RFC PATCH] net: macb: Apply RXUBR workaround only to versions with errata Harini Katakam
2018-11-28 21:09 ` Brandon Streiff
2018-11-29  5:13   ` Harini Katakam
2018-11-29 10:00   ` Claudiu.Beznea [this message]
2018-11-29 10:21 ` Claudiu.Beznea
2018-11-29 10:38   ` Harini Katakam
2018-11-29 10:43     ` Claudiu.Beznea

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=88ca959b-6fed-8afb-e433-6a21e17ec067@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=brandon.streiff@ni.com \
    --cc=davem@davemloft.net \
    --cc=harini.katakam@xilinx.com \
    --cc=harinikatakamlinux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --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