On Thu, Dec 20, 2012 at 08:01:43PM +0200, Terje Bergstr?m wrote: > On 20.12.2012 19:55, Stephen Warren wrote: > > So it's fine for the tegradrm driver to manipulate the tegradrm > > (virtual) device's drvdata pointer. > > > > It's not fine for tegradrm to manipulate the drvdata pointer of other > > devices; the host1x children. The drvdata pointer for other devices is > > reserved for those devices' driver's use only. > > They're all tegradrm drivers, so tegradrm can manipulate its drvdata. > The other simple way is global pointer. Let's aim now for a simple > solution, and if later we find out it causes problems, let's fix it then.
The problem with your proposed solution is that, even any of Stephen's valid objections aside, it won't work. Once the tegra-drm module is unloaded, the driver's data will be left in the current state and the link to the dummy device will be lost. I don't think waiting for things to fail is the right option here. If we can make out this problem now, then now is the time to fix it. No excuses. And quite frankly given how all the various host1x components are interlinked I think having a single function that gets the DRM dummy device for DRM-related clients isn't that bad. Thierry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121220/e8b4be4e/attachment.pgp>
