Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761018AbaJDACn (ORCPT ); Fri, 3 Oct 2014 20:02:43 -0400 Received: from seldrel01.sonyericsson.com ([212.209.106.2]:13551 "EHLO seldrel01.sonyericsson.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760993AbaJDACk (ORCPT ); Fri, 3 Oct 2014 20:02:40 -0400 Date: Fri, 3 Oct 2014 17:02:50 -0700 From: Bjorn Andersson To: Stephen Boyd CC: Kumar Gala , Andy Gross , Arnd Bergmann , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-arm-msm@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Grant Likely , Ian Campbell , Lee Jones , Liam Girdwood , Mark Brown , Mark Rutland , Pawel Moll , Rob Herring , Samuel Ortiz Subject: Re: [RFC 5/7] soc: qcom: Add Shared Memory Driver Message-ID: <20141004000249.GD28481@sonymobile.com> References: <1412037291-16880-1-git-send-email-bjorn.andersson@sonymobile.com> <1412037291-16880-6-git-send-email-bjorn.andersson@sonymobile.com> <542DD3DA.1010909@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <542DD3DA.1010909@codeaurora.org> User-Agent: Mutt/1.5.22 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 02 Oct 15:38 PDT 2014, Stephen Boyd wrote: > On 09/29/14 17:34, Bjorn Andersson wrote: > > + > > +#define GET_RX_CHANNEL_INFO(channel, param) \ > > + (channel->rx_info_word ? \ > > + channel->rx_info_word->param : \ > > + channel->rx_info->param) > > + > > +#define GET_TX_CHANNEL_INFO(channel, param) \ > > + (channel->rx_info_word ? \ > > + channel->tx_info_word->param : \ > > + channel->tx_info->param) > > + > > +#define SET_RX_CHANNEL_INFO(channel, param, value) \ > > + (channel->rx_info_word ? \ > > + (channel->rx_info_word->param = value) : \ > > + (channel->rx_info->param = value)) > > + > > +#define SET_TX_CHANNEL_INFO(channel, param, value) \ > > + (channel->rx_info_word ? \ > > Drive-by review: Should this be tx_info_word? Given that it works I > wonder why not just have a flag indicating if we should use word aligned > read/write vs. byte aligned. > You're right, that should be tx - but from the way things both channels will always be of the same type, so it will simply work. I had a separate flag, but instead of having 4 members in the struct to indicate if I was dealing with word aligned access I had 5. So I dropped it. > > + (channel->tx_info_word->param = value) : \ > > + (channel->tx_info->param = value)) > > + > Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/