From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Jiawen Wu <jiawenwu@trustnetic.com>,
netdev@vger.kernel.org, andrew@lunn.ch, linux@armlinux.org.uk,
jarkko.nikula@linux.intel.com, olteanv@gmail.com,
hkallweit1@gmail.com, linux-i2c@vger.kernel.org,
linux-gpio@vger.kernel.org, mengyuanlou@net-swift.com
Subject: Re: [PATCH net-next v4 2/8] i2c: designware: Add driver support for Wangxun 10Gb NIC
Date: Mon, 1 May 2023 21:28:04 +0300 [thread overview]
Message-ID: <ZFAEtI+UgPWGbJMH@smile.fi.intel.com> (raw)
In-Reply-To: <20230425140859.q23mhtsk5zoc2t3d@intel.intel>
On Tue, Apr 25, 2023 at 04:08:59PM +0200, Andi Shyti wrote:
> > > #define MODEL_MSCC_OCELOT BIT(8)
> > > #define MODEL_BAIKAL_BT1 BIT(9)
> > > #define MODEL_AMD_NAVI_GPU BIT(10)
> > > +#define MODEL_WANGXUN_SP BIT(11)
> > > #define MODEL_MASK GENMASK(11, 8)
> >
> > Yeah, maybe next one will need to transform this from bitfield to plain number.
>
> You mean this?
No, only MODEL_XXX bits.
> -#define ACCESS_INTR_MASK BIT(0)
> -#define ACCESS_NO_IRQ_SUSPEND BIT(1)
> -#define ARBITRATION_SEMAPHORE BIT(2)
> -
> -#define MODEL_MSCC_OCELOT BIT(8)
> -#define MODEL_BAIKAL_BT1 BIT(9)
> -#define MODEL_AMD_NAVI_GPU BIT(10)
> -#define MODEL_MASK GENMASK(11, 8)
> +#define ACCESS_INTR_MASK 0x00
> +#define ACCESS_NO_IRQ_SUSPEND 0x01
> +#define ARBITRATION_SEMAPHORE 0x02
> +
> +#define MODEL_MSCC_OCELOT 0x08
> +#define MODEL_BAIKAL_BT1 0x09
> +#define MODEL_AMD_NAVI_GPU 0x0a
> +#define MODEL_MASK 0x78
>
> I actually like more bitfield to plain numbers.
Too limited. For model we get 16 out of 4 bits, which is much better and as you
see we have a trend.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-05-01 18:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 4:56 [PATCH net-next v4 0/8] TXGBE PHYLINK support Jiawen Wu
2023-04-22 4:56 ` [PATCH net-next v4 1/8] net: txgbe: Add software nodes to support phylink Jiawen Wu
2023-04-23 19:47 ` Simon Horman
2023-04-22 4:56 ` [PATCH net-next v4 2/8] i2c: designware: Add driver support for Wangxun 10Gb NIC Jiawen Wu
2023-04-22 16:25 ` Andy Shevchenko
2023-04-23 2:31 ` Jiawen Wu
2023-04-24 13:28 ` 'Andy Shevchenko'
2023-04-24 2:39 ` Jiawen Wu
2023-04-25 14:08 ` Andi Shyti
2023-05-01 18:28 ` Andy Shevchenko [this message]
2023-04-22 4:56 ` [PATCH net-next v4 3/8] net: txgbe: Register I2C platform device Jiawen Wu
2023-04-25 15:06 ` Andi Shyti
2023-04-25 15:16 ` Andi Shyti
2023-04-22 4:56 ` [PATCH net-next v4 4/8] net: txgbe: Add SFP module identify Jiawen Wu
2023-04-22 4:56 ` [PATCH net-next v4 5/8] net: txgbe: Support GPIO to SFP socket Jiawen Wu
2023-04-22 4:56 ` [PATCH net-next v4 6/8] net: pcs: Add 10GBASE-R mode for Synopsys Designware XPCS Jiawen Wu
2023-05-02 8:01 ` Russell King (Oracle)
2023-04-22 4:56 ` [PATCH net-next v4 7/8] net: txgbe: Implement phylink pcs Jiawen Wu
2023-04-22 4:56 ` [PATCH net-next v4 8/8] net: txgbe: Support phylink MAC layer Jiawen Wu
2023-04-23 19:57 ` Simon Horman
2023-04-24 1:49 ` Jiawen Wu
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=ZFAEtI+UgPWGbJMH@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jiawenwu@trustnetic.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.