On Wed, Aug 21, 2024 at 08:42:02AM -0300, Fabio Estevam wrote: > Print the error code in the pca953x_write_regs() and pca953x_read_regs() > functions to help debugging. May be, or may be better to use (implement?) proper filters for regmap tracepoints? In that case we may drop all these noisy messages and leave only the fatal ones. -- With Best Regards, Andy Shevchenko
Re: [PATCH] gpio: pca953x: Print the error code on read/write failures
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] gpio: pca953x: Print the error code on read/write failures
- From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxx>
- Date: Fri, 23 Aug 2024 18:25:54 +0300
- In-reply-to: <20240821114202.2072220-1-festevam@gmail.com>
- Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
- References: <20240821114202.2072220-1-festevam@gmail.com>
- References:
- [PATCH] gpio: pca953x: Print the error code on read/write failures
- From: Fabio Estevam
- [PATCH] gpio: pca953x: Print the error code on read/write failures
- Prev by Date: Re: [PATCH v1] drivers/pinctrl/renesas: Switch to use kmemdup_array()
- Next by Date: Re: [PATCH v1] pinctrl: nomadik: Use kmemdup_array instead of kmemdup for multiple allocation
- Previous by thread: Re: [PATCH] gpio: pca953x: Print the error code on read/write failures
- Next by thread: [PATCH 1/4] gpio: ath79: order headers alphabetically
- Index(es):
 |