From: Stephen Boyd <sboyd@codeaurora.org> To: Bjorn Andersson <bjorn.andersson@sonymobile.com> Cc: Andy Gross <agross@codeaurora.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 1/3] soc: qcom: smd: Represent channel layout in structures Date: Tue, 1 Sep 2015 10:51:02 -0700 [thread overview] Message-ID: <55E5E586.3060905@codeaurora.org> (raw) In-Reply-To: <20150901045502.GB13472@usrtlx11787.corpusers.net> On 08/31/2015 09:55 PM, Bjorn Andersson wrote: > On Mon 31 Aug 18:39 PDT 2015, Stephen Boyd wrote: > >> The rx and tx channel info are laid out in memory next to each >> other, and there are two types of channel info structures, byte >> based and word based. We have 4 pointers to these info >> structures, when we really only need two to point to the >> different types of structures. Encapsulate the byte based and word >> based tx/rx structures in a "full channel" structure that >> describes the layout of memory and reduces the number of pointers >> in the smd channel structure by two. >> > Saving the extra pointer doesn't feel like worth the change, but > representing the pair of info structs as one sounds like a reasonable > cleanup. Agreed. > > Reviewed-by: Bjorn Andersson <bjorn.andersson@sonymobile.com> >> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org> >> --- >> drivers/soc/qcom/smd.c | 61 +++++++++++++++++++++++++++----------------------- >> 1 file changed, 33 insertions(+), 28 deletions(-) >> >> diff --git a/drivers/soc/qcom/smd.c b/drivers/soc/qcom/smd.c >> index edd9d9a37238..c16547b85e05 100644 >> --- a/drivers/soc/qcom/smd.c >> +++ b/drivers/soc/qcom/smd.c >> @@ -65,7 +65,9 @@ >> */ >> >> struct smd_channel_info; >> +struct smd_full_channel_info; > I would have called this "smd_channel_info_pair"... Sure I'll make the change and add your Reviewed-by. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/3] soc: qcom: smd: Represent channel layout in structures Date: Tue, 1 Sep 2015 10:51:02 -0700 [thread overview] Message-ID: <55E5E586.3060905@codeaurora.org> (raw) In-Reply-To: <20150901045502.GB13472@usrtlx11787.corpusers.net> On 08/31/2015 09:55 PM, Bjorn Andersson wrote: > On Mon 31 Aug 18:39 PDT 2015, Stephen Boyd wrote: > >> The rx and tx channel info are laid out in memory next to each >> other, and there are two types of channel info structures, byte >> based and word based. We have 4 pointers to these info >> structures, when we really only need two to point to the >> different types of structures. Encapsulate the byte based and word >> based tx/rx structures in a "full channel" structure that >> describes the layout of memory and reduces the number of pointers >> in the smd channel structure by two. >> > Saving the extra pointer doesn't feel like worth the change, but > representing the pair of info structs as one sounds like a reasonable > cleanup. Agreed. > > Reviewed-by: Bjorn Andersson <bjorn.andersson@sonymobile.com> >> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org> >> --- >> drivers/soc/qcom/smd.c | 61 +++++++++++++++++++++++++++----------------------- >> 1 file changed, 33 insertions(+), 28 deletions(-) >> >> diff --git a/drivers/soc/qcom/smd.c b/drivers/soc/qcom/smd.c >> index edd9d9a37238..c16547b85e05 100644 >> --- a/drivers/soc/qcom/smd.c >> +++ b/drivers/soc/qcom/smd.c >> @@ -65,7 +65,9 @@ >> */ >> >> struct smd_channel_info; >> +struct smd_full_channel_info; > I would have called this "smd_channel_info_pair"... Sure I'll make the change and add your Reviewed-by. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-09-01 17:51 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-01 1:39 [PATCH 0/3] qcom smd big endian support Stephen Boyd 2015-09-01 1:39 ` Stephen Boyd 2015-09-01 1:39 ` [PATCH 1/3] soc: qcom: smd: Represent channel layout in structures Stephen Boyd 2015-09-01 1:39 ` Stephen Boyd 2015-09-01 1:39 ` Stephen Boyd 2015-09-01 4:55 ` Bjorn Andersson 2015-09-01 4:55 ` Bjorn Andersson 2015-09-01 4:55 ` Bjorn Andersson 2015-09-01 17:51 ` Stephen Boyd [this message] 2015-09-01 17:51 ` Stephen Boyd 2015-09-01 17:51 ` Stephen Boyd 2015-09-01 1:39 ` [PATCH 2/3] soc: qcom: smd: Use __iowrite32_copy() instead of open-coding it Stephen Boyd 2015-09-01 1:39 ` Stephen Boyd 2015-09-01 4:59 ` Bjorn Andersson 2015-09-01 4:59 ` Bjorn Andersson 2015-09-01 4:59 ` Bjorn Andersson 2015-09-01 18:03 ` Stephen Boyd 2015-09-01 18:03 ` Stephen Boyd 2015-09-01 18:03 ` Stephen Boyd 2015-09-01 20:30 ` Stephen Boyd 2015-09-01 20:30 ` Stephen Boyd 2015-09-01 20:30 ` Stephen Boyd 2015-09-01 1:39 ` [PATCH 3/3] soc: qcom: smd: Handle big endian CPUs Stephen Boyd 2015-09-01 1:39 ` Stephen Boyd 2015-09-01 5:06 ` Bjorn Andersson 2015-09-01 5:06 ` Bjorn Andersson 2015-09-01 5:06 ` Bjorn Andersson 2015-09-01 18:04 ` Stephen Boyd 2015-09-01 18:04 ` Stephen Boyd 2015-09-01 18:04 ` Stephen Boyd
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=55E5E586.3060905@codeaurora.org \ --to=sboyd@codeaurora.org \ --cc=agross@codeaurora.org \ --cc=bjorn.andersson@sonymobile.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.