* H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> [190213 06:36]: > > Am 13.02.2019 um 01:41 schrieb Tony Lindgren <tony@xxxxxxxxxxx>: > > No doubt it's a mess.. I'm only suggesting a generic driver that > > manages standard Linux resources like regulators, clocks and > > interrupts and provides 2d acceleration for sgx540 based on what > > we already have at drivers/gpu/drm/gma500/accel_2d.c. The idea > > being that it might then also make dealing with the rest of the > > sgx blobs a bit easier hopefully. > > Well, ok. > > So you suggest that we e.g. take the omap SoC support in > > http://git.goldelico.com/?p=letux-kernel.git;a=tree;f=drivers/staging/pvr/1.14.3699939/eurasia_km/services4/system/omap;h=09ff9c9112dd7e8f7316ba5f1e022dcb824c2ce4;hb=1d5b6a91eca80168c37ecb66157e675d28666652 > > and make an "eurasia_km / services4 / system / generic" out of > it using the 2d functions? So here's a copy of what I just suggested on the pyra mailing list thread for the device drivers needed for kernel: 1. SoC glue device (power, clocks, dma maybe) 2. SGX glue device for shared resources 3.1 2d accelerated driver 3.2 3d sgx blob driver This is assuming the 2d and 3d parts are a separate device inside the sgx like you're saying. > Please take a look into especially sysconfig.c and SysInitialise() > which does the lion's share of initialization if it can be rewritten > to become generic. OK yeah I have no idea about the sgx internals currently. But I can try to help with the SoC glue layer parts, how to organize the various device driver components, and the dts binding parts. Regards, Tony
