From: Kumar Gala <galak@codeaurora.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Use of drivers/platform and matching include?
Date: Thu, 3 Oct 2013 09:45:38 -0500 [thread overview]
Message-ID: <BC1C47B3-5412-4829-A1D9-AAB04694D1CC@codeaurora.org> (raw)
As we look at upstreaming more support for the Qualcomm MSM SoCs there are a number of drivers or library like routines that are unique to the MSM platform, we are thinking that putting them under:
drivers/platform/qcom/
would make sense. In addition there are headers that might need to get shared with drivers in other locations so I wanted to see what the take was on introducing:
include/linux/platform/qcom/
An example driver would be the means we utilize to communicate memory regions between various HW blocks on the SoC. So a video/media core driver might need access to a header/functions from the memory region driver.
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2013-10-03 14:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 14:45 Kumar Gala [this message]
2013-10-03 15:27 ` Greg Kroah-Hartman
2013-10-03 16:21 ` Kumar Gala
2013-10-03 16:25 ` Greg Kroah-Hartman
2013-10-03 16:38 ` Kumar Gala
2013-10-03 16:46 ` Olof Johansson
2013-10-03 17:09 ` Greg Kroah-Hartman
2013-10-03 17:54 ` Olof Johansson
2013-10-04 11:18 ` Catalin Marinas
2013-10-04 11:50 ` Russell King - ARM Linux
2013-10-04 11:43 ` Russell King - ARM Linux
2013-10-04 12:03 ` Catalin Marinas
2013-10-04 11:41 ` Russell King - ARM Linux
2013-10-04 13:22 ` Greg Kroah-Hartman
2013-10-04 16:48 ` Olof Johansson
2013-10-04 19:29 ` Santosh Shilimkar
2013-10-05 17:13 ` Greg Kroah-Hartman
2013-10-08 0:26 ` Rohit Vaswani
2013-10-08 2:19 ` Greg Kroah-Hartman
2013-10-07 6:48 ` Andi Shyti
2013-10-08 17:57 ` Rohit Vaswani
2013-10-09 6:04 ` Andi Shyti
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=BC1C47B3-5412-4829-A1D9-AAB04694D1CC@codeaurora.org \
--to=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 \
/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
all inboxes | Powered by JetHome®