[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aedc760b-ca4d-031d-6797-4f0a1ab2d5d7@intel.com>
Date: Wed, 1 Feb 2023 11:35:48 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Jithu Joseph <jithu.joseph@...el.com>, hdegoede@...hat.com,
markgross@...nel.org
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
gregkh@...uxfoundation.org, rostedt@...dmis.org,
ashok.raj@...el.com, tony.luck@...el.com,
linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org,
patches@...ts.linux.dev, ravi.v.shankar@...el.com,
thiago.macieira@...el.com, athenas.jimenez.gonzalez@...el.com,
sohil.mehta@...el.com
Subject: Re: [PATCH 4/5] platform/x86/intel/ifs: Implement Array BIST test
On 1/31/23 15:43, Jithu Joseph wrote:
> +union ifs_array {
> + u64 data;
> + struct {
> + u32 array_bitmask :32;
> + u32 array_bank :16;
> + u32 rsvd :15;
> + u32 ctrl_result :1;
> + };
> +};
Why bother with a bitfield? Just do:
union ifs_array {
u64 data;
struct {
u32 array_bitmask;
u16 array_bank;
u16 flags;
};
};
Then you only need to mask 'ctrl_result' out of flags. You don't need
any crazy macros.
Powered by blists - more mailing lists