[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240304084824.y42djaciaeq5gqz3@DEN-DL-M31836.microchip.com>
Date: Mon, 4 Mar 2024 09:48:24 +0100
From: Horatiu Vultur - M31836 <Horatiu.Vultur@...rochip.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Arun Ramadoss - I17769 <Arun.Ramadoss@...rochip.com>, "andrew@...n.ch"
<andrew@...n.ch>, "linux@...linux.org.uk" <linux@...linux.org.uk>,
"hkallweit1@...il.com" <hkallweit1@...il.com>, "wojciech.drewek@...el.com"
<wojciech.drewek@...el.com>, "davem@...emloft.net" <davem@...emloft.net>,
"pabeni@...hat.com" <pabeni@...hat.com>, "edumazet@...gle.com"
<edumazet@...gle.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, UNGLinuxDriver
<UNGLinuxDriver@...rochip.com>
Subject: Re: [PATCH net-next v2 2/2] net: phy: micrel: lan8814 cable
improvement errata
The 03/02/2024 19:40, Jakub Kicinski wrote:
>
> On Fri, 1 Mar 2024 08:27:57 +0100 Horatiu Vultur - M31836 wrote:
> > > > +#define LAN8814_PD_CONTROLS 0x9d
> > > > +#define LAN8814_PD_CONTROLS_PD_MEAS_TIME_MASK_ GENMASK(3, 0)
> > > > +#define LAN8814_PD_CONTROLS_PD_MEAS_TIME_VAL_ 0xb
> > >
> > > nitpick: TIME_VAL macro is very generic if it can end with specific
> > > like TIME_VAL_100M or something similar will gives more readability.
> >
> > Actually I prefer to keep it like this the name if it is possible..
> > Because the VAL_ represents the value and MASK_ represents the mask
> > value. Therefore the actual bits name of the register is
> > LAN8814_PD_CONTROLS_PD_MEAS_TIME.
> >
> > I am trying to have a naming convetion about how to define names in this
> > file:
> > <TARGET>_<REG_NAME>_<REG_BITS_NAME>
>
> Why the trailing underscores, tho?
That is not really needed. I will update this in the next version.
>
--
/Horatiu
Powered by blists - more mailing lists