Searched hist:e291d298 (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/drivers/gpu/drm/fsl-dcu/ |
H A D | fsl_dcu_drm_crtc.c | e291d298 Wed Nov 18 18:50:55 CST 2015 Stefan Agner <stefan@agner.ch> drm/fsl-dcu: remove regmap return value checks
It is not common to do regmap return value checks, especially not for memory mapped device. We can rule out most error returns since the conditions are static and we know they are ok (e.g. offset aligned to register stride). Also without proper error handling they are not really valuable for the user. Hence remove most of them.
The check in the interrupt handler is worth keeping since a volatile register won't be readable in case register caching is still enabled.
Signed-off-by: Stefan Agner <stefan@agner.ch> e291d298 Wed Nov 18 18:50:55 CST 2015 Stefan Agner <stefan@agner.ch> drm/fsl-dcu: remove regmap return value checks It is not common to do regmap return value checks, especially not for memory mapped device. We can rule out most error returns since the conditions are static and we know they are ok (e.g. offset aligned to register stride). Also without proper error handling they are not really valuable for the user. Hence remove most of them. The check in the interrupt handler is worth keeping since a volatile register won't be readable in case register caching is still enabled. Signed-off-by: Stefan Agner <stefan@agner.ch>
|
H A D | fsl_dcu_drm_plane.c | e291d298 Wed Nov 18 18:50:55 CST 2015 Stefan Agner <stefan@agner.ch> drm/fsl-dcu: remove regmap return value checks
It is not common to do regmap return value checks, especially not for memory mapped device. We can rule out most error returns since the conditions are static and we know they are ok (e.g. offset aligned to register stride). Also without proper error handling they are not really valuable for the user. Hence remove most of them.
The check in the interrupt handler is worth keeping since a volatile register won't be readable in case register caching is still enabled.
Signed-off-by: Stefan Agner <stefan@agner.ch> e291d298 Wed Nov 18 18:50:55 CST 2015 Stefan Agner <stefan@agner.ch> drm/fsl-dcu: remove regmap return value checks It is not common to do regmap return value checks, especially not for memory mapped device. We can rule out most error returns since the conditions are static and we know they are ok (e.g. offset aligned to register stride). Also without proper error handling they are not really valuable for the user. Hence remove most of them. The check in the interrupt handler is worth keeping since a volatile register won't be readable in case register caching is still enabled. Signed-off-by: Stefan Agner <stefan@agner.ch>
|
H A D | fsl_dcu_drm_drv.c | e291d298 Wed Nov 18 18:50:55 CST 2015 Stefan Agner <stefan@agner.ch> drm/fsl-dcu: remove regmap return value checks
It is not common to do regmap return value checks, especially not for memory mapped device. We can rule out most error returns since the conditions are static and we know they are ok (e.g. offset aligned to register stride). Also without proper error handling they are not really valuable for the user. Hence remove most of them.
The check in the interrupt handler is worth keeping since a volatile register won't be readable in case register caching is still enabled.
Signed-off-by: Stefan Agner <stefan@agner.ch> e291d298 Wed Nov 18 18:50:55 CST 2015 Stefan Agner <stefan@agner.ch> drm/fsl-dcu: remove regmap return value checks It is not common to do regmap return value checks, especially not for memory mapped device. We can rule out most error returns since the conditions are static and we know they are ok (e.g. offset aligned to register stride). Also without proper error handling they are not really valuable for the user. Hence remove most of them. The check in the interrupt handler is worth keeping since a volatile register won't be readable in case register caching is still enabled. Signed-off-by: Stefan Agner <stefan@agner.ch>
|