|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [RFC PATCH v1 11/12] Arm: GICv3: Define macros to read/write 64 bit
On 10/21/22 18:31, Ayan Kumar Halder wrote: Hi Ayan Maybe you wanted to write sth like (((u64)readl_relaxed((c) + 4) << 32) | readl_relaxed(c))readl_relaxed returns a u32 value so no byteorder conversions are needed at this stage. Also, you need to add parentheses around macro parameter c because an operator performs on it. #define writeb_relaxed(v,c) __raw_writeb(v,c)#define writew_relaxed(v,c) __raw_writew((__force u16) cpu_to_le16(v),c) #define writel_relaxed(v,c) __raw_writel((__force u32) cpu_to_le32(v),c) +#define writeq_relaxed(v,c) writel_relaxed(((uint64_t)v&0xffffffff), c); \ + writel_relaxed((((uint64_t)v)>>32), (c+4));#define readb(c) ({ u8 __v = readb_relaxed(c); __iormb(); __v; }) And writel_relaxed((u32)v, c); writel_relaxed((u32)((v) >> 32), (c) + 4);v is already u64 and writel_relaxed() expects a u32. Here as well, you need to add parentheses around macro parameter c because an operator performs on it. I am wondering if the parts of the register need to be accessed in a specific order. -- Xenia
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |