driver core: add probe error check helper
Subsystems (4)
A message that is not in the archive (sent off-list or not yet received): CGME20200629112247eucas1p2f5a1c0a4ffe3a2571658646a7b369cfd@eucas1p2.samsung.com
v7 cover driver core: add probe error check helper
Hi All,
Thanks for comments.
Changes since v6:
- removed leftovers from old naming scheme in commit descritions,
- added R-Bs.
Changes since v5:
- removed patch adding macro, dev_err_probe(dev, PTR_ERR(ptr), ...) should be used instead,
- added dev_dbg logging in case of -EPROBE_DEFER,
- renamed functions and vars according to comments,
- extended docs,
- cosmetics.
Original message (with small adjustments):
Recently I took some time to re-check error handling in drivers probe code, and I have noticed that number of incorrect resource acquisition error handling increased and there are no other propositions which can cure the situation.
So I have decided to resend my old proposition of probe_err helper which should simplify resource acquisition error handling, it also extend it with adding defer probe reason to devices_deferred debugfs property, which should improve debugging experience for developers/testers.
I have also added two patches showing usage and benefits of the helper.
My dirty/ad-hoc cocci scripts shows that this helper can be used in at least 2700 places saving about 3500 lines of code.
Regards
Andrzej
Andrzej Hajda (4):
driver core: add device probe log helper
driver core: add deferring probe reason to devices_deferred property drm/bridge/sii8620: fix resource acquisition error handling drm/bridge: lvds-codec: simplify error handling
drivers/base/base.h | 3 ++ drivers/base/core.c | 46 ++++++++++++++++++++++++++++ drivers/base/dd.c | 23 +++++++++++++- drivers/gpu/drm/bridge/lvds-codec.c | 10 ++---- drivers/gpu/drm/bridge/sil-sii8620.c | 21 ++++++------- include/linux/device.h | 3 ++ 6 files changed, 86 insertions(+), 20 deletions(-)
Signature · 6 lines
2.17.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v7 1/4 driver core: add device probe log helper
During probe every time driver gets resource it should usually check for error printk some message if it is not -EPROBE_DEFER and return the error. This pattern is simple but requires adding few lines after any resource acquisition code, as a result it is often omitted or implemented only partially.dev_err_probe helps to replace such code sequences with simple call, so code:
if (err != -EPROBE_DEFER) dev_err(dev, ...); return err; becomes: return dev_err_probe(dev, err, ...);
--- drivers/base/core.c | 42 ++++++++++++++++++++++++++++++++++++++++++ include/linux/device.h | 3 +++ 2 files changed, 45 insertions(+)
drivers/base/core.c +42 -0
@@ -3953,6 +3953,48 @@ define_dev_printk_level(_dev_info, KERN_INFO);#endif +/** +* dev_err_probe - probe error check and log helper +* @dev: the pointer to the struct device +* @err: error value to test +* @fmt: printf-style format string +* @...: arguments as specified in the format string +* +* This helper implements common pattern present in probe functions for error +* checking: print debug or error message depending if the error value is +* -EPROBE_DEFER and propagate error upwards. +* It replaces code sequence: +* if (err != -EPROBE_DEFER) +* dev_err(dev, ...); +* else +* dev_dbg(dev, ...); +* return err; +* with +* return dev_err_probe(dev, err, ...); +* +* Returns @err. +* +*/ +int dev_err_probe (const struct device *dev,int err,const char *fmt, ...) +{ +struct va_format vaf; +va_list args; + +va_start (args, fmt); + vaf.fmt = fmt; + vaf.va = &args; + +if (err != -EPROBE_DEFER ) +dev_err (dev,"error %d: %pV" , err, &vaf); +else +dev_dbg (dev,"error %d: %pV" , err, &vaf); + +va_end (args); + +return err; +} +EXPORT_SYMBOL_GPL (dev_err_probe); +static inline bool fwnode_is_primary (struct fwnode_handle *fwnode) {return fwnode && !IS_ERR (fwnode->secondary);
include/linux/device.h +3 -0
@@ -964,6 +964,9 @@ void device_link_remove(void *consumer, struct device *supplier);void device_links_supplier_sync_state_pause (void );void device_links_supplier_sync_state_resume (void ); +extern __printf(3, 4) +int dev_err_probe(const struct device *dev, int err, const char *fmt, ...); + /* Create alias, so I can be autoloaded. */ #define MODULE_ALIAS_CHARDEV(major,minor) \ MODULE_ALIAS("char-major-" __stringify(major) "-" __stringify(minor))
Signature · 6 lines
2.17.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v7 1/4] driver core: add device probe log helper
Quoted 8 lines · Andrzej Hajda
During probe every time driver gets resource it should usually check for error printk some message if it is not -EPROBE_DEFER and return the error. This pattern is simple but requires adding few lines after any resource acquisition code, as a result it is often omitted or implemented only partially.
dev_err_probehelps to replace such code sequences with simple call, so code:
Quoted 5 lines
if (err != -EPROBE_DEFER)
dev_err(dev, ...);
return err;
becomes:
return dev_err_probe(dev, err, ...);FWIW,
(I'm fine with current code, though, consider below comments)
Quoted 37 lines
Signed-off-by Andrzej Hajda <[email protected]>Reviewed-by Rafael J. Wysocki <[email protected]>--- drivers/base/core.c | 42 ++++++++++++++++++++++++++++++++++++++++++ include/linux/device.h | 3 +++ 2 files changed, 45 insertions(+)drivers/base/core.c +22
-0@@ -3953,6 +3953,48 @@ define_dev_printk_level(_dev_info, KERN_INFO);#endif +/** +* dev_err_probe - probe error check and log helper +* @dev: the pointer to the struct device +* @err: error value to test +* @fmt: printf-style format string +* @...: arguments as specified in the format string +* +* This helper implements common pattern present in probe functions for error +* checking: print debug or error message depending if the error value is +* -EPROBE_DEFER and propagate error upwards. +* It replaces code sequence: +* if (err != -EPROBE_DEFER) +* dev_err(dev, ...); +* else +* dev_dbg(dev, ...); +* return err; +* with +* return dev_err_probe(dev, err, ...); +* +* Returns @err. +* +*/
drivers/base/core.c define_dev_printk_level(_dev_info, KERN_INFO); · line 3987
Quoted 10 lines
drivers/base/core.c +10
-0+int dev_err_probe (const struct device *dev,int err,const char *fmt, ...) +{ +struct va_format vaf; +va_list args; + +va_start (args, fmt); + vaf.fmt = fmt; + vaf.va = &args; + +if (err != -EPROBE_DEFER )
Perhaps positive conditional.
drivers/base/core.c define_dev_printk_level(_dev_info, KERN_INFO); · line 3990
Quoted 3 lines
drivers/base/core.c +3
-0+dev_err (dev,"error %d: %pV" , err, &vaf); + else + dev_dbg(dev, "error %d: %pV", err, &vaf);
Perhaps {} to be added here.
Quoted 27 lines
drivers/base/core.c +7
-0+ +va_end (args); + +return err; +} +EXPORT_SYMBOL_GPL (dev_err_probe); +static inline bool fwnode_is_primary (struct fwnode_handle *fwnode) {return fwnode && !IS_ERR (fwnode->secondary);include/linux/device.h +3
-1@@ -964,6 +964,9 @@ void device_link_remove(void *consumer, struct device *supplier);void device_links_supplier_sync_state_pause (void );void device_links_supplier_sync_state_resume (void ); +extern __printf(3, 4) +int dev_err_probe(const struct device *dev, int err, const char *fmt, ...); + /* Create alias, so I can be autoloaded. */ #define MODULE_ALIAS_CHARDEV(major,minor) \ MODULE_ALIAS("char-major-" __stringify(major) "-" __stringify(minor)) --2.17.1
Signature · 6 lines
With Best Regards, Andy Shevchenko _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v8 2/5 driver core: add deferring probe reason to devices_deferred property
/sys/kernel/debug/devices_deferred property contains list of deferred devices. This list does not contain reason why the driver deferred probe, the patch improves it.
The natural place to set the reason is dev_err_probe function introduced recently, ie. if dev_err_probe will be called with -EPROBE_DEFER instead of printk the message will be attached to a deferred device and printed when user reads devices_deferred property.
---
v8:
- improved commit message
--- drivers/base/base.h | 3 +++ drivers/base/core.c | 8 ++++++-- drivers/base/dd.c | 23 ++++++++++++++++++++++- 3 files changed, 31 insertions(+), 3 deletions(-)
drivers/base/base.h +3 -0
@@ -93,6 +93,7 @@ struct device_private {struct klist_node knode_class;struct list_head deferred_probe;struct device_driver *async_driver; +char *deferred_probe_reason;struct device *device; u8 dead:1; };
@@ -134,6 +135,8 @@ extern void device_release_driver_internal(struct device *dev,extern void driver_detach (struct device_driver *drv);extern int driver_probe_device (struct device_driver *drv,struct device *dev);extern void driver_deferred_probe_del (struct device *dev); +extern void device_set_deferred_probe_reson (const struct device *dev, +struct va_format *vaf);static inline int driver_match_device (struct device_driver *drv,struct device *dev) {
drivers/base/core.c +6 -2
@@ -3963,6 +3963,8 @@ define_dev_printk_level(_dev_info, KERN_INFO);* This helper implements common pattern present in probe functions for error * checking: print debug or error message depending if the error value is * -EPROBE_DEFER and propagate error upwards. +* In case of -EPROBE_DEFER it sets also defer probe reason, which can be +* checked later by reading devices_deferred debugfs attribute. * It replaces code sequence: * if (err != -EPROBE_DEFER) * dev_err(dev, ...);
@@ -3984,10 +3986,12 @@ int dev_err_probe(const struct device *dev, int err, const char *fmt, ...) vaf.fmt = fmt; vaf.va = &args; -if (err != -EPROBE_DEFER ) +if (err != -EPROBE_DEFER ) {dev_err (dev,"error %d: %pV" , err, &vaf); -else + }else { +device_set_deferred_probe_reson (dev, &vaf);dev_dbg (dev,"error %d: %pV" , err, &vaf); + }va_end (args);
drivers/base/dd.c +22 -1
@@ -27,6 +27,7 @@#include <linux/async.h> #include <linux/pm_runtime.h> #include <linux/pinctrl/devinfo.h> +#include <linux/slab.h> #include "base.h" #include "power/power.h"
@@ -136,6 +137,8 @@ void driver_deferred_probe_del(struct device *dev)if (!list_empty (&dev->p->deferred_probe)) {dev_dbg (dev,"Removed from deferred list\n" );list_del_init (&dev->p->deferred_probe); +kfree (dev->p->deferred_probe_reason); + dev->p->deferred_probe_reason =NULL ; }mutex_unlock (&deferred_probe_mutex); }
@@ -211,6 +214,23 @@ void device_unblock_probing(void)driver_deferred_probe_trigger (); } +/** +* device_set_deferred_probe_reson() - Set defer probe reason message for device +* @dev: the pointer to the struct device +* @vaf: the pointer to va_format structure with message +*/ +void device_set_deferred_probe_reson (const struct device *dev,struct va_format *vaf) +{ +const char *drv =dev_driver_string (dev); + +mutex_lock (&deferred_probe_mutex); + +kfree (dev->p->deferred_probe_reason); + dev->p->deferred_probe_reason =kasprintf (GFP_KERNEL ,"%s: %pV" , drv, vaf); + +mutex_unlock (&deferred_probe_mutex); +} +/* * deferred_devs_show() - Show the devices in the deferred probe pending list. */
@@ -221,7 +241,8 @@ static int deferred_devs_show(struct seq_file *s, void *data)mutex_lock (&deferred_probe_mutex);list_for_each_entry (curr, &deferred_probe_pending_list, deferred_probe) -seq_printf (s,"%s\n" ,dev_name (curr->device)); +seq_printf (s,"%s\t%s" ,dev_name (curr->device), + curr->device->p->deferred_probe_reason ?:"\n" );mutex_unlock (&deferred_probe_mutex);
Signature · 6 lines
2.17.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Greg Kroah-Hartman
maintainerRe: [PATCH v8 2/5] driver core: add deferring probe reason to devices_deferred property
Quoted 8 lines · Andrzej Hajda
/sys/kernel/debug/devices_deferredproperty contains list of deferred devices. This list does not contain reason why the driver deferred probe, the patch improves it.
The natural place to set the reason isdev_err_probefunction introduced recently, ie. ifdev_err_probewill be called with -EPROBE_DEFER instead of printk the message will be attached to a deferred device and printed when user readsdevices_deferredproperty.
Quoted 8 lines
Signed-off-by Andrzej Hajda <[email protected]>Reviewed-by Mark Brown <[email protected]>Reviewed-by Javier Martinez Canillas <[email protected]>Reviewed-by Andy Shevchenko <[email protected]>Reviewed-by Rafael J. Wysocki <[email protected]>---
v8:
- improved commit message
I'm totally confused by this series. Can you resend the whole thing, as a full series, not just random individual patches in the series incremented? It's a pain to try to fish them all out as to which is the "latest" with all of the needed reviewed by lines :(
thanks,
greg k-h
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v8 2/5] driver core: add deferring probe reason to devices_deferred property
Quoted 17 lines · Greg Kroah-Hartman
Quoted 8 lines · Andrzej Hajda
/sys/kernel/debug/devices_deferredproperty contains list of deferred devices. This list does not contain reason why the driver deferred probe, the patch improves it.
The natural place to set the reason isdev_err_probefunction introduced recently, ie. ifdev_err_probewill be called with -EPROBE_DEFER instead of printk the message will be attached to a deferred device and printed when user readsdevices_deferredproperty.Quoted 8 lines
Signed-off-by Andrzej Hajda <[email protected]>Reviewed-by Mark Brown <[email protected]>Reviewed-by Javier Martinez Canillas <[email protected]>Reviewed-by Andy Shevchenko <[email protected]>Reviewed-by Rafael J. Wysocki <[email protected]>---
v8:
- improved commit message
Quoted 4 lines
I'm totally confused by this series. Can you resend the whole thing, as a full series, not just random individual patches in the series incremented? It's a pain to try to fish them all out as to which is the "latest" with all of the needed reviewed by lines :(
v7 is the latest except this one,which contains only commit message change.
Anyway I will send v8 to make things simple.
Regards
Andrzej
Quoted 9 lines
thanks,
greg k-h
_______________________________________________
dri-devel mailing list
[email protected]
https://protect2.fireeye.com/v1/url?k=563dadd0-0bf16175-563c269f-0cc47a30d446-7237066d193b28b5&q=1&e=54779b9e-347e-4d0c-9845-da31d4cce7e4&u=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fdri-devel
Re: [PATCH v7 1/4] driver core: add device probe log helper
In reply to Andrzej HajdaQuoted 5 lines · Andrzej Hajda
During probe every time driver gets resource it should usually check for error printk some message if it is not -EPROBE_DEFER and return the error. This pattern is simple but requires adding few lines after any resource acquisition code, as a result it is often omitted or implemented only partially.
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v7 2/4 driver core: add deferring probe reason to devices_deferred property
In reply to Andrzej Hajda/sys/kernel/debug/devices_deferred property contains list of deferred devices. This list does not contain reason why the driver deferred probe, the patch improves it.
The natural place to set the reason is dev_err_probe function introduced recently, ie. if dev_err_probe will be called with -EPROBE_DEFER instead of printk the message will be attached to deferred device and printed when user read devices_deferred property.
--- drivers/base/base.h | 3 +++ drivers/base/core.c | 8 ++++++-- drivers/base/dd.c | 23 ++++++++++++++++++++++- 3 files changed, 31 insertions(+), 3 deletions(-)
drivers/base/base.h +3 -0
@@ -93,6 +93,7 @@ struct device_private {struct klist_node knode_class;struct list_head deferred_probe;struct device_driver *async_driver; +char *deferred_probe_reason;struct device *device; u8 dead:1; };
@@ -134,6 +135,8 @@ extern void device_release_driver_internal(struct device *dev,extern void driver_detach (struct device_driver *drv);extern int driver_probe_device (struct device_driver *drv,struct device *dev);extern void driver_deferred_probe_del (struct device *dev); +extern void device_set_deferred_probe_reson (const struct device *dev, +struct va_format *vaf);static inline int driver_match_device (struct device_driver *drv,struct device *dev) {
drivers/base/core.c +6 -2
@@ -3963,6 +3963,8 @@ define_dev_printk_level(_dev_info, KERN_INFO);* This helper implements common pattern present in probe functions for error * checking: print debug or error message depending if the error value is * -EPROBE_DEFER and propagate error upwards. +* In case of -EPROBE_DEFER it sets also defer probe reason, which can be +* checked later by reading devices_deferred debugfs attribute. * It replaces code sequence: * if (err != -EPROBE_DEFER) * dev_err(dev, ...);
@@ -3984,10 +3986,12 @@ int dev_err_probe(const struct device *dev, int err, const char *fmt, ...) vaf.fmt = fmt; vaf.va = &args; -if (err != -EPROBE_DEFER ) +if (err != -EPROBE_DEFER ) {dev_err (dev,"error %d: %pV" , err, &vaf); -else + }else { +device_set_deferred_probe_reson (dev, &vaf);dev_dbg (dev,"error %d: %pV" , err, &vaf); + }va_end (args);
drivers/base/dd.c +22 -1
@@ -27,6 +27,7 @@#include <linux/async.h> #include <linux/pm_runtime.h> #include <linux/pinctrl/devinfo.h> +#include <linux/slab.h> #include "base.h" #include "power/power.h"
@@ -136,6 +137,8 @@ void driver_deferred_probe_del(struct device *dev)if (!list_empty (&dev->p->deferred_probe)) {dev_dbg (dev,"Removed from deferred list\n" );list_del_init (&dev->p->deferred_probe); +kfree (dev->p->deferred_probe_reason); + dev->p->deferred_probe_reason =NULL ; }mutex_unlock (&deferred_probe_mutex); }
@@ -211,6 +214,23 @@ void device_unblock_probing(void)driver_deferred_probe_trigger (); } +/** +* device_set_deferred_probe_reson() - Set defer probe reason message for device +* @dev: the pointer to the struct device +* @vaf: the pointer to va_format structure with message +*/ +void device_set_deferred_probe_reson (const struct device *dev,struct va_format *vaf) +{ +const char *drv =dev_driver_string (dev); + +mutex_lock (&deferred_probe_mutex); + +kfree (dev->p->deferred_probe_reason); + dev->p->deferred_probe_reason =kasprintf (GFP_KERNEL ,"%s: %pV" , drv, vaf); + +mutex_unlock (&deferred_probe_mutex); +} +/* * deferred_devs_show() - Show the devices in the deferred probe pending list. */
@@ -221,7 +241,8 @@ static int deferred_devs_show(struct seq_file *s, void *data)mutex_lock (&deferred_probe_mutex);list_for_each_entry (curr, &deferred_probe_pending_list, deferred_probe) -seq_printf (s,"%s\n" ,dev_name (curr->device)); +seq_printf (s,"%s\t%s" ,dev_name (curr->device), + curr->device->p->deferred_probe_reason ?:"\n" );mutex_unlock (&deferred_probe_mutex);
Signature · 6 lines
2.17.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v7 2/4] driver core: add deferring probe reason to devices_deferred property
Quoted 7 lines · Andrzej Hajda
/sys/kernel/debug/devices_deferredproperty contains list of deferred devices. This list does not contain reason why the driver deferred probe, the patch improves it.
The natural place to set the reason isdev_err_probefunction introduced recently, ie. ifdev_err_probewill be called with -EPROBE_DEFER instead of printk the message will be attached to deferred device and printed when user readdevices_deferred
to a deferred
reads
Quoted 1 line
property.
...
drivers/base/core.c int dev_err_probe(const struct device *dev, int err, const char *fmt, ...) · line 3990
Quoted 7 lines
drivers/base/core.c +1
-1@@ -3984,10 +3986,12 @@ int dev_err_probe(const struct device *dev, int err, const char *fmt, ...) vaf.fmt = fmt; vaf.va = &args; -if (err != -EPROBE_DEFER ) +if (err != -EPROBE_DEFER ) {
Why not positive conditional? (Okay, I'm fine with either in this case)
drivers/base/core.c int dev_err_probe(const struct device *dev, int err, const char *fmt, ...) · line 3994
Quoted 6 lines
drivers/base/core.c +3
-1dev_err (dev,"error %d: %pV" , err, &vaf); - else + }else { +device_set_deferred_probe_reson (dev, &vaf);dev_dbg (dev,"error %d: %pV" , err, &vaf); + }
To reduce churn, you may move {} addition to the first patch.
...
drivers/base/dd.c static int deferred_devs_show(struct seq_file *s, void *data) · line 245
Quoted 4 lines
drivers/base/dd.c +2
-1list_for_each_entry (curr, &deferred_probe_pending_list, deferred_probe) -seq_printf (s,"%s\n" ,dev_name (curr->device)); +seq_printf (s,"%s\t%s" ,dev_name (curr->device), + curr->device->p->deferred_probe_reason ?:"\n" );
Hmm... "\t" will be dangling in the latter case.
Signature · 6 lines
With Best Regards, Andy Shevchenko _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v7 2/4] driver core: add deferring probe reason to devices_deferred property
Quoted 10 lines · Andy Shevchenko
Quoted 6 lines · Andrzej Hajda
/sys/kernel/debug/devices_deferredproperty contains list of deferred devices. This list does not contain reason why the driver deferred probe, the patch improves it.
The natural place to set the reason isdev_err_probefunction introduced recently, ie. ifdev_err_probewill be called with -EPROBE_DEFER instead of printk the message will be attached to deferred device and printed when user readdevices_deferredto a deferred
reads
OK, thx.
Quoted 11 lines
Quoted 2 lines
property.
...
drivers/base/core.c int dev_err_probe(const struct device *dev, int err, const char *fmt, ...) · line 3989
Quoted 6 lines
drivers/base/core.c +1
-1@@ -3984,10 +3986,12 @@ int dev_err_probe(const struct device *dev, int err, const char *fmt, ...) vaf.fmt = fmt; vaf.va = &args; -if (err != -EPROBE_DEFER ) +if (err != -EPROBE_DEFER ) {Why not positive conditional? (Okay, I'm fine with either in this case)
I put more natural branch 1st.
Quoted 8 lines
drivers/base/core.c int dev_err_probe(const struct device *dev, int err, const char *fmt, ...) · line 3994
Quoted 7 lines
drivers/base/core.c +3
-1dev_err (dev,"error %d: %pV" , err, &vaf); - else + }else { +device_set_deferred_probe_reson (dev, &vaf);dev_dbg (dev,"error %d: %pV" , err, &vaf); + }To reduce churn, you may move {} addition to the first patch.
But then I need to explain why it is there :)
Quoted 8 lines
...
drivers/base/dd.c static int deferred_devs_show(struct seq_file *s, void *data) · line 245
Quoted 4 lines
list_for_each_entry(curr, &deferred_probe_pending_list, deferred_probe)drivers/base/dd.c +2
-1-seq_printf (s,"%s\n" ,dev_name (curr->device)); +seq_printf (s,"%s\t%s" ,dev_name (curr->device), + curr->device->p->deferred_probe_reason ?:"\n" );Hmm... "\t" will be dangling in the latter case
Hmm, I followed your advice [1] :)
[1]:
https://www.mail-archive.com/[email protected]/msg1787370.html
Regards
Andrzej
Quoted 1 line
Re: [PATCH v7 2/4] driver core: add deferring probe reason to devices_deferred property
Quoted 14 lines · Andrzej Hajda
Quoted 10 lines · Andy Shevchenko
Quoted 6 lines · Andrzej Hajda
/sys/kernel/debug/devices_deferredproperty contains list of deferred devices. This list does not contain reason why the driver deferred probe, the patch improves it.
The natural place to set the reason isdev_err_probefunction introduced recently, ie. ifdev_err_probewill be called with -EPROBE_DEFER instead of printk the message will be attached to deferred device and printed when user readdevices_deferredto a deferred
reads
OK, thx.
Quoted 2 lines
Quoted 2 lines
property.
...
Quoted 11 lines
Quoted 5 lines
drivers/base/dd.c static int deferred_devs_show(struct seq_file *s, void *data) · line 245
Quoted 4 lines
list_for_each_entry(curr, &deferred_probe_pending_list, deferred_probe)drivers/base/dd.c +2
-1-seq_printf (s,"%s\n" ,dev_name (curr->device)); +seq_printf (s,"%s\t%s" ,dev_name (curr->device), + curr->device->p->deferred_probe_reason ?:"\n" );Hmm... "\t" will be dangling in the latter case
Hmm, I followed your advice [1] :)
[1]:
https://www.mail-archive.com/[email protected]/msg1787370.html
Ah, indeed :-)
Okay, as I said I'm fine with the code. Since it's debugfs, we are fine.
Signature · 6 lines
With Best Regards, Andy Shevchenko _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v7 3/4 drm/bridge/sii8620: fix resource acquisition error handling
In reply to Andrzej HajdaIn case of error during resource acquisition driver should print error message only in case it is not deferred probe, using dev_err_probe helper solves the issue. Moreover it records defer probe reason for debugging.
--- drivers/gpu/drm/bridge/sil-sii8620.c | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-)
drivers/gpu/drm/bridge/sil-sii8620.c +9 -12
@@ -2299,10 +2299,9 @@ static int sii8620_probe(struct i2c_client *client,INIT_LIST_HEAD (&ctx->mt_queue); ctx->clk_xtal =devm_clk_get (dev,"xtal" ); -if (IS_ERR (ctx->clk_xtal)) { -dev_err (dev,"failed to get xtal clock from DT\n" ); -return PTR_ERR (ctx->clk_xtal); - } +if (IS_ERR (ctx->clk_xtal)) +return dev_err_probe (dev,PTR_ERR (ctx->clk_xtal), +"failed to get xtal clock from DT\n" );if (!client->irq) {dev_err (dev,"no irq provided\n" );
@@ -2313,16 +2312,14 @@ static int sii8620_probe(struct i2c_client *client, sii8620_irq_thread,IRQF_TRIGGER_HIGH |IRQF_ONESHOT , "sii8620", ctx); -if (ret <0 ) { -dev_err (dev,"failed to install IRQ handler\n" ); -return ret; - } +if (ret <0 ) +return dev_err_probe (dev, ret, +"failed to install IRQ handler\n" ); ctx->gpio_reset =devm_gpiod_get (dev,"reset" ,GPIOD_OUT_HIGH ); -if (IS_ERR (ctx->gpio_reset)) { -dev_err (dev,"failed to get reset gpio from DT\n" ); -return PTR_ERR (ctx->gpio_reset); - } +if (IS_ERR (ctx->gpio_reset)) +return dev_err_probe (dev,PTR_ERR (ctx->gpio_reset), +"failed to get reset gpio from DT\n" ); ctx->supplies[0 ].supply ="cvcc10" ; ctx->supplies[1 ].supply ="iovcc18" ;
Signature · 6 lines
2.17.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v7 4/4 drm/bridge: lvds-codec: simplify error handling
In reply to Andrzej HajdaUsing dev_err_probe code has following advantages:
- shorter code,
- recorded defer probe reason for debugging,
- uniform error code logging.
--- drivers/gpu/drm/bridge/lvds-codec.c | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-)
drivers/gpu/drm/bridge/lvds-codec.c +3 -7
@@ -71,13 +71,9 @@ static int lvds_codec_probe(struct platform_device *pdev) lvds_codec->connector_type = (uintptr_t )of_device_get_match_data (dev); lvds_codec->powerdown_gpio =devm_gpiod_get_optional (dev,"powerdown" ,GPIOD_OUT_HIGH ); -if (IS_ERR (lvds_codec->powerdown_gpio)) { -int err =PTR_ERR (lvds_codec->powerdown_gpio); - -if (err != -EPROBE_DEFER ) -dev_err (dev,"powerdown GPIO failure: %d\n" , err); -return err; - } +if (IS_ERR (lvds_codec->powerdown_gpio)) +return dev_err_probe (dev,PTR_ERR (lvds_codec->powerdown_gpio), +"powerdown GPIO failure\n" );/* Locate the panel DT node. */ panel_node =of_graph_get_remote_node (dev->of_node,1 ,0 );
Signature · 6 lines
2.17.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel