[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <535521A0.5050706@codeaurora.org>
Date: Mon, 21 Apr 2014 09:48:16 -0400
From: Christopher Covington <cov@...eaurora.org>
To: Andy Gross <agross@...eaurora.org>
CC: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-arm-msm@...r.kernel.org,
Santosh Shilimkar <santosh.shilimkar@...com>,
Kumar Gala <galak@...eaurora.org>,
linux-arm-kernel@...ts.infradead.org,
Olof Johansson <olof@...om.net>
Subject: Re: [PATCH 0/4] Introduce drivers/soc and add QCOM GSBI driver
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists