Pkshih <pkshih@xxxxxxxxxxx> writes:
> On Tue, 2018-05-29 at 08:18 +0300, Kalle Valo wrote:
>> <pkshih@xxxxxxxxxxx> writes:
>>
>> > From: Ping-Ke Shih <pkshih@xxxxxxxxxxx>
>> >
>> > The format of C2H data is ID(1 byte) + Length(1 byte) + value, and it is
>> > more readable to use macros to access C2H data.
>> >
>> > Signed-off-by: Ping-Ke Shih <pkshih@xxxxxxxxxxx>
>>
>> [...]
>>
>> > --- a/drivers/net/wireless/realtek/rtlwifi/wifi.h
>> > +++ b/drivers/net/wireless/realtek/rtlwifi/wifi.h
>> > @@ -177,6 +177,11 @@ enum rtl_c2h_evt_v2 {
>> > C2H_V2_CCX_RPT = 0x0F,
>> > };
>> >
>> > +#define GET_C2H_CMD_ID(c2h) ({u8 *__c2h = c2h; __c2h[0]; })
>> > +#define GET_C2H_SEQ(c2h) ({u8 *__c2h = c2h; __c2h[1]; })
>> > +#define C2H_DATA_OFFSET 2
>> > +#define GET_C2H_DATA_PTR(c2h) ({u8 *__c2h = c2h; &__c2h[C2H_DATA_OFFSET]; })
>>
>> These macros are not really pretty, a proper static inline function
>> would be a much better choise. But I'm planning to apply this patch
>> anyway, I don't think it's a blocker but a good idea to cleanup later.
>>
>> And rtlwifi really should get away with this foo[0] and foo[1] style of
>> buffers and switch to proper structs (foo->bar and foo->koo).
>
> Thanks for your review and suggestion.
>
> Because C2H data is little endian order, the struct will look like
> struct foo {
> #ifdef __LITTLE_ENDIAN
> u8 bar:4;
> u8 koo:4;
> #else
> u8 koo:4;
> u8 bar:4;
> #endif
> }
With u8 you don't need endian check, right? I would assume that with
both little and big endian bar and koo would be in the same place.
> Is this a linux convention?
Earlier bitfields were disliked but nowadays they seem to be have become
more acceptable. But I think the preferred way still is something like
this (using u32 and 16 bit fields):
struct foo {
__le32 koobar;
}
#define RTLWIFI_BAR_MASK GENMASK(15, 0)
#define RTLWIFI_KOO_MASK GENMASK(31, 16)
bar = FIELD_GET(RTLWIFI_BAR_MASK, __le32_to_cpu(foo->koobar));
koo = FIELD_GET(RTLWIFI_KOO_MASK, __le32_to_cpu(foo->koobar));
Of course there can be other good ways to do the same, others can chime
in about those, but this is how I would do it.
--
Kalle Valo
