From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752038AbdBMJyi (ORCPT ); Mon, 13 Feb 2017 04:54:38 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:38189 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751836AbdBMJyh (ORCPT ); Mon, 13 Feb 2017 04:54:37 -0500 Date: Mon, 13 Feb 2017 10:54:34 +0100 (CET) From: Thomas Gleixner To: Marc Zyngier cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, Christoffer Dall , Jason Cooper , Eric Auger Subject: Re: [RFC PATCH 03/33] irqchip/gic-v3-its: Refactor command encoding In-Reply-To: <1484648454-21216-4-git-send-email-marc.zyngier@arm.com> Message-ID: References: <1484648454-21216-1-git-send-email-marc.zyngier@arm.com> <1484648454-21216-4-git-send-email-marc.zyngier@arm.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 17 Jan 2017, Marc Zyngier wrote: > +static void its_mask_encode(u64 *raw_cmd, u64 val, int h, int l) I'd rather name h/l in a way which makes it clear that they are describing a bit range. msb/lsb perhaps. > +{ > + u64 mask = GENMASK_ULL(h, l); New line missing here. > + *raw_cmd &= ~mask; > + *raw_cmd |= (val << l) & mask; > +} > + > static void its_encode_cmd(struct its_cmd_block *cmd, u8 cmd_nr) > { > - cmd->raw_cmd[0] &= ~0xffULL; > - cmd->raw_cmd[0] |= cmd_nr; > + its_mask_encode(&cmd->raw_cmd[0], cmd_nr, 7, 0); I assume that the manual provides a name for these bit ranges. Wouldn't it be helpful to use them in these functions? Looks good otherwise. Thanks, tglx