On 14.12.2012 18:21, Stephen Warren wrote: > On 12/13/2012 11:09 PM, Terje Bergström wrote: >> They want to get the global data by getting drvdata of their parent. > > There's no reason that /has/ to be so; they can get any information from > wherever it is, rather than trying to require it to be somewhere it isn't. Exactly, this was also my solution. >> The dummy device is not their parent - host1x is. There's no >> connection between the dummy and the real client devices. > > It's quite possible for the client devices to ask their actual parent > (host1x) for the tegradrm struct device *, by calling a host1x API, and > have host1x implement that API by returning the dummy/virtual device > that it created. That should be just 1-2 lines of code to implement in > host1x, plus maybe a couple more to correctly return -EPROBE_DEFERRED > when appropriate. My solution was to just have one global, and an getter for the global. Instead of drvdata, the pointer is retrieved with the getter. No need for dummy device, or passing points between host1x and tegradrm. Terje -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
