From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brown Subject: Re: [PATCH 0/7] Move Qualcomm gpio drivers into drivers dir Date: Fri, 27 May 2011 14:19:21 -0700 Message-ID: <8yar57j6duu.fsf@huya.qualcomm.com> References: <1305755453-31112-1-git-send-email-davidb@codeaurora.org> <20110527031319.GH5032@ponder.secretlab.ca> <8yad3j46r97.fsf@huya.qualcomm.com> <8ya8vts6qzn.fsf@huya.qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from wolverine02.qualcomm.com ([199.106.114.251]:9125 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752499Ab1E0VTZ (ORCPT ); Fri, 27 May 2011 17:19:25 -0400 In-Reply-To: (Nicolas Pitre's message of "Fri, 27 May 2011 15:31:47 -0400 (EDT)") Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Nicolas Pitre Cc: Grant Likely , Daniel Walker , Bryan Huntsman , Russell King , Thomas Gleixner , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org On Fri, May 27 2011, Nicolas Pitre wrote: > On Fri, 27 May 2011, David Brown wrote: >> On Fri, May 27 2011, David Brown wrote: >> > On Thu, May 26 2011, Grant Likely wrote: >> >> On Wed, May 18, 2011 at 02:50:46PM -0700, David Brown wrote: >> >>> This patch series moves the Qualcomm MSM gpio device drivers into the >> >>> drivers/gpio directory. >> >>> >> >>> The MSM's have two flavors of gpio driver. The one for the newer >> >>> v7-based chips is a bit cleaner, and can just be moved. The one for >> >>> the older v6-based chips took some cleanup to get rid of numerous >> >>> ifdefs based on the particular machine. Both drivers can now be >> >>> selected and will be used on appropriate targets. >> >>> >> >>> There is still a minor entanglement with the MSM-specific gpiomux >> >>> code. This will be cleaned up as MSM moves to use pinmux. >> >>> >> >>> David Brown (7): >> >>> msm: gpio: Remove unsupported devices >> >>> msm: Remove chip-ifdefs for GPIO io mappings >> >>> msm: gpio: Remove chip-specific register definitions >> >>> msm: gpio: Remove ifdefs on gpio chip registers >> >>> msm: gpiomux: Move public API to public header >> >>> gpio_msm: Move Qualcomm v6 MSM driver into drivers >> >>> gpio_msm: Move Qualcomm MSM v2 gpio driver into drivers >> >> >> >> What's the status of this series. I only got cc'd on the last two >> >> patches; did you want me to pick up the whole lot, or is it being >> >> merged via the msm tree? >> > >> > Let me send out an update, incorporating the suggestions. I need to >> > rebase these changes off of the current MSM code, since the msm-next >> > tree contains changes that aren't going into the merge window because of >> > extra ARM scrutiny. >> > >> >> Alternately, if there is a git branch with these patches in it, then I >> >> can merge that instead of applying individually. >> > >> > I'll send you a pull request after I send out the updates. >> >> Oh, and in case it isn't clear, I wasn't expecting these to make it into >> this merge window. > > Why not? They haven't been tested in linux-next for one, but more importantly, I have to redo them to not include the msm-core changes that aren't going to be going in. I'm probably not going to be able to get to this until next week. David -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. From mboxrd@z Thu Jan 1 00:00:00 1970 From: davidb@codeaurora.org (David Brown) Date: Fri, 27 May 2011 14:19:21 -0700 Subject: [PATCH 0/7] Move Qualcomm gpio drivers into drivers dir In-Reply-To: (Nicolas Pitre's message of "Fri, 27 May 2011 15:31:47 -0400 (EDT)") References: <1305755453-31112-1-git-send-email-davidb@codeaurora.org> <20110527031319.GH5032@ponder.secretlab.ca> <8yad3j46r97.fsf@huya.qualcomm.com> <8ya8vts6qzn.fsf@huya.qualcomm.com> Message-ID: <8yar57j6duu.fsf@huya.qualcomm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, May 27 2011, Nicolas Pitre wrote: > On Fri, 27 May 2011, David Brown wrote: >> On Fri, May 27 2011, David Brown wrote: >> > On Thu, May 26 2011, Grant Likely wrote: >> >> On Wed, May 18, 2011 at 02:50:46PM -0700, David Brown wrote: >> >>> This patch series moves the Qualcomm MSM gpio device drivers into the >> >>> drivers/gpio directory. >> >>> >> >>> The MSM's have two flavors of gpio driver. The one for the newer >> >>> v7-based chips is a bit cleaner, and can just be moved. The one for >> >>> the older v6-based chips took some cleanup to get rid of numerous >> >>> ifdefs based on the particular machine. Both drivers can now be >> >>> selected and will be used on appropriate targets. >> >>> >> >>> There is still a minor entanglement with the MSM-specific gpiomux >> >>> code. This will be cleaned up as MSM moves to use pinmux. >> >>> >> >>> David Brown (7): >> >>> msm: gpio: Remove unsupported devices >> >>> msm: Remove chip-ifdefs for GPIO io mappings >> >>> msm: gpio: Remove chip-specific register definitions >> >>> msm: gpio: Remove ifdefs on gpio chip registers >> >>> msm: gpiomux: Move public API to public header >> >>> gpio_msm: Move Qualcomm v6 MSM driver into drivers >> >>> gpio_msm: Move Qualcomm MSM v2 gpio driver into drivers >> >> >> >> What's the status of this series. I only got cc'd on the last two >> >> patches; did you want me to pick up the whole lot, or is it being >> >> merged via the msm tree? >> > >> > Let me send out an update, incorporating the suggestions. I need to >> > rebase these changes off of the current MSM code, since the msm-next >> > tree contains changes that aren't going into the merge window because of >> > extra ARM scrutiny. >> > >> >> Alternately, if there is a git branch with these patches in it, then I >> >> can merge that instead of applying individually. >> > >> > I'll send you a pull request after I send out the updates. >> >> Oh, and in case it isn't clear, I wasn't expecting these to make it into >> this merge window. > > Why not? They haven't been tested in linux-next for one, but more importantly, I have to redo them to not include the msm-core changes that aren't going to be going in. I'm probably not going to be able to get to this until next week. David -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.