From: Christopher Covington <cov@codeaurora.org>
To: Andy Gross <agross@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Kumar Gala <galak@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 0/4] Introduce drivers/soc and add QCOM GSBI driver
Date: Mon, 21 Apr 2014 09:48:16 -0400 [thread overview]
Message-ID: <535521A0.5050706@codeaurora.org> (raw)
In-Reply-To: <1398058244-14099-1-git-send-email-agross@codeaurora.org>
Hi Andy,
On 04/21/2014 01:30 AM, Andy Gross wrote:
> The first patch in this set adds the drivers/soc directory and all the necessary
> plumbing. These changes were discussed at the kernel summit and also were
> introduced in an earlier patch set from Santosh Shilimkar.
>
> Reference the following set of patches:
> https://lkml.org/lkml/2014/2/28/567
In that thread, Olof wrote, "The code [going into drivers/soc] isn't the pure
drivers. Those we find homes for."
https://lkml.org/lkml/2014/3/2/123
> The remaining patches add the QCOM GSBI (General Serial Bus Interface) driver,
> device tree binding information for both the GSBI and child node interaction,
> and lastly a patch to fix the current MSM serial driver to work correctly with
> the GSBI changes.
It's not obvious to me what makes the GSBI driver "impure" and unfit for say
drivers/bus. Could you perhaps include a brief explanation?
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-04-21 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 5:30 [PATCH 0/4] Introduce drivers/soc and add QCOM GSBI driver Andy Gross
2014-04-21 5:30 ` [PATCH 1/4] soc: Placeholder files for drivers/soc Andy Gross
2014-04-21 5:30 ` [PATCH 2/4] soc: qcom: Add GSBI driver Andy Gross
2014-04-21 16:54 ` Josh Cartwright
2014-04-21 17:11 ` Andy Gross
2014-04-21 17:26 ` Josh Cartwright
2014-04-21 5:30 ` [PATCH 3/4] soc: qcom: Add device tree binding for GSBI Andy Gross
2014-04-21 16:55 ` Kumar Gala
2014-04-21 5:30 ` [PATCH 4/4] tty: serial: msm: Remove direct access to GSBI Andy Gross
2014-04-21 13:48 ` Christopher Covington [this message]
2014-04-21 16:21 ` [PATCH 0/4] Introduce drivers/soc and add QCOM GSBI driver Andy Gross
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=535521A0.5050706@codeaurora.org \
--to=cov@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=santosh.shilimkar@ti.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).