Linux IIO development
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: David Lechner <dlechner@baylibre.com>,
	nuno.sa@analog.com,  linux-iio@vger.kernel.org
Cc: Michael Hennerich <Michael.Hennerich@analog.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Andy Shevchenko <andy@kernel.org>
Subject: Re: [PATCH 2/2] iio: dac: adi-axi-dac: Turn dev_info() into dev_dbg()
Date: Wed, 03 Dec 2025 16:31:40 +0000	[thread overview]
Message-ID: <d19cbb170e066eb00c4f4066b2596e34ddb7b09f.camel@gmail.com> (raw)
In-Reply-To: <44640683-de26-492f-a7ef-6af4a61518f3@baylibre.com>

On Wed, 2025-12-03 at 10:14 -0600, David Lechner wrote:
> On 12/3/25 10:10 AM, Nuno Sá wrote:
> > On Wed, 2025-12-03 at 10:05 -0600, David Lechner wrote:
> > > On 12/3/25 9:53 AM, Nuno Sá via B4 Relay wrote:
> > > > From: Nuno Sá <nuno.sa@analog.com>
> > > > 
> > > > We should not abuse logging and logging a successful probe is clearly
> > > > abuse. Turn it into dev_dbg().
> > > > 
> > > > If it turns out the IP version is that relevant we can make it easy to
> > > > get through a new debugfs interface later on.
> > > > 
> > > > Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> > > > ---
> > > >  drivers/iio/dac/adi-axi-dac.c | 8 ++++----
> > > >  1 file changed, 4 insertions(+), 4 deletions(-)
> > > > 
> > > > diff --git a/drivers/iio/dac/adi-axi-dac.c b/drivers/iio/dac/adi-axi-dac.c
> > > > index 0c7b62f5357d..f536158beb4c 100644
> > > > --- a/drivers/iio/dac/adi-axi-dac.c
> > > > +++ b/drivers/iio/dac/adi-axi-dac.c
> > > > @@ -1000,10 +1000,10 @@ static int axi_dac_probe(struct platform_device *pdev)
> > > >  						"cannot create device.");
> > > >  	}
> > > >  
> > > > -	dev_info(&pdev->dev, "AXI DAC IP core (%d.%.2d.%c) probed\n",
> > > > -		 ADI_AXI_PCORE_VER_MAJOR(ver),
> > > > -		 ADI_AXI_PCORE_VER_MINOR(ver),
> > > > -		 ADI_AXI_PCORE_VER_PATCH(ver));
> > > > +	dev_dbg(&pdev->dev, "AXI DAC IP core (%d.%.2d.%c) probed\n",
> > > 
> > > Didn't ADI HDL versioning policy change to semver so that the last number
> > > is no longer necessarily an ASCII character?
> > > 
> > > We could probably change this to %d.%.d.%d while here.
> > 
> > Honestly, I'm not sure how that settled up. I'll check and if that's the case I can change it.
> > But then it will be a bit messy with older IPs. Maybe moving this into debugfs and handle the
> > format
> > there would make sense.
> > 
> > - Nuno Sá
> > 
> > > 
> 
> If it was still an ASCII value, it would just look like an unusually
> high bug fix number, but I don't think that hurts much. I don't think
> we need to go as far as changing it to debugfs. It should be pretty
> obvious if that is the case and people can figure out how to convert
> the number to a character.
> 

Alright, but (unlike the spi_engine) it seems this core is still using the old format [1].

> The dev_err_probe() function in the previous patch in this series
> also has the same issue.

Right!

[1]: https://github.com/analogdevicesinc/hdl/blob/main/library/common/up_dac_common.v#L128
- Nuno Sá

      parent reply	other threads:[~2025-12-03 16:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 15:53 [PATCH 0/2] iio: dac: adi-axi-dac: Minor cleanups Nuno Sá via B4 Relay
2025-12-03 15:53 ` [PATCH 1/2] iio: dac: adi-axi-dac: Make use of dev_err_probe() Nuno Sá via B4 Relay
2025-12-03 16:06   ` David Lechner
2025-12-03 16:29     ` Nuno Sá
2025-12-07 17:33       ` David Lechner
2025-12-03 15:53 ` [PATCH 2/2] iio: dac: adi-axi-dac: Turn dev_info() into dev_dbg() Nuno Sá via B4 Relay
2025-12-03 16:05   ` David Lechner
2025-12-03 16:10     ` Nuno Sá
2025-12-03 16:14       ` David Lechner
2025-12-03 16:17         ` Andy Shevchenko
2025-12-03 16:31         ` Nuno Sá [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d19cbb170e066eb00c4f4066b2596e34ddb7b09f.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox