[lkml]   [2011]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] msm: add single-wire serial bus interface (SSBI) driver
On Tue, 22 Feb 2011, David Brown wrote:

> On Tue, Feb 22 2011, Nicolas Pitre wrote:
> > And if someone else comes up with a SSBI interface, then it will be much
> > easier to notice the already existing driver if it is in the driver
> > directory rather than somewhere else in some unrelated (from that
> > person's pov) obscure directory.
> Well, I'm fairly sure that nobody would be making an SSBI interface, but
> point taken.

It's not necessarily the SSBI interface per se that is interesting to
other people, but rather the fact that the code driving it might be
relying upon generic kernel infrastructure, such as driver or bus
registration, interrupt requests, resource allocation, etc.

> So what kinds of things constitute drivers versus arch-specific code?
> Currently, iommu drivers seem to be sprinkled throughout arch.

Yes, and so are clock source and clock event "drivers". Some things
fall into a gray area and this is not always clear what the proper
location is for them. But as a rule of thumb you should follow what
most other people did, and if there is no example to follow then just go
with drivers/msm/ by default which should be a pretty safe bet.


 \ /
  Last update: 2011-02-23 04:23    [W:0.027 / U:1.808 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site