linux-kernel - Re: Use of drivers/platform and matching include?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131003152715.GA15931@kroah.com>
Date:	Thu, 3 Oct 2013 08:27:15 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Kumar Gala <galak@...eaurora.org>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-arm-msm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: Use of drivers/platform and matching include?

On Thu, Oct 03, 2013 at 09:45:38AM -0500, Kumar Gala wrote:
> 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/

What type of drivers are these?  Shouldn't they really go under the
specific driver type directory instead?

> 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.

Isn't there arch-specific include directories already that are good for
stuff like this?

thanks,

greg k-h
--
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/