From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Thu, 20 Aug 2020 20:08:33 -0400 Subject: [PATCH v2 01/10] spi: dw: Convert calls to debug to log_* In-Reply-To: References: <20200807144317.282868-1-seanga2@gmail.com> <20200807144317.282868-2-seanga2@gmail.com> Message-ID: <20200821000833.GY20605@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Aug 20, 2020 at 03:36:31PM +0200, Marek Vasut wrote: > On 8/20/20 3:26 PM, Simon Glass wrote: > > On Fri, 7 Aug 2020 at 08:43, Sean Anderson wrote: > >> > >> This allows different log levels to be enabled or disabled depending on the > >> desired level of verbosity. In particular, it allows for general debug > >> information to be printed while excluding more verbose logging which may > >> interfere with timing. > >> > >> Signed-off-by: Sean Anderson > >> --- > >> > >> Changes in v2: > >> - New > >> > >> drivers/spi/designware_spi.c | 33 ++++++++++++++++----------------- > >> 1 file changed, 16 insertions(+), 17 deletions(-) > >> > > > > Reviewed-by: Simon Glass > > NAK, please use dev_dbg() instead. For the record, Marek and I (and Sean) had talked a bit on IRC. These messages being log_xxx() and not dev_xx() instead make the more functionally useful as dev_xxx() converts to printf() and messes with the timing. log_xxx() puts them in the buffer and will not break the timing. Marek objects to the fundamentals that dev_xxx() does not function like it does in Linux (and please correct me if you feel I'm mis-representing your views). This could be solved by plumbing dev_xxx() to use log_xxx() if LOG is enabled automagically. I don't see transitions like that as blocking for this patch, Marek does. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: