20 Dec
2012
20 Dec
'12
6:01 p.m.
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.
Terje