Searched hist:a98b1e78 (Results 1 – 5 of 5) sorted by relevance
| /openbmc/linux/drivers/gpu/drm/etnaviv/ |
| H A D | Kconfig | a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
|
| H A D | etnaviv_drv.h | a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
|
| H A D | etnaviv_gpu.h | a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
|
| H A D | etnaviv_drv.c | a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
|
| H A D | etnaviv_gpu.c | a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
a98b1e78 Thu Apr 19 08:55:40 CDT 2018 Lucas Stach <l.stach@pengutronix.de> drm/etnaviv: remove register logging
I'm not aware of any case where tracing GPU register manipulation at the
kernel level would have been useful. It only adds more indirections and
adds to the code size.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
|