public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Gerald Loacker <gerald.loacker@wolfvision.net>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Jakob Hauser <jahau@rocketmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
	Michael Riesch <michael.riesch@wolfvision.net>
Subject: Re: [PATCH v5 3/3] iio: magnetometer: add ti tmag5273 driver
Date: Wed, 30 Nov 2022 19:43:05 +0200	[thread overview]
Message-ID: <Y4eWKdJXOR7hJTF3@smile.fi.intel.com> (raw)
In-Reply-To: <ef3ec278-d9dd-4318-5b8a-d0ed363fbaab@wolfvision.net>

On Wed, Nov 30, 2022 at 05:32:10PM +0100, Gerald Loacker wrote:
> Am 30.11.2022 um 16:31 schrieb Andy Shevchenko:
> > On Wed, Nov 30, 2022 at 03:53:56PM +0100, Gerald Loacker wrote:

...

> >> +	switch (data->devid) {
> >> +	case TMAG5273_MANUFACTURER_ID:
> >> +		/*
> >> +		 * The device name matches the orderable part number. 'x' stands
> >> +		 * for A, B, C or D devices, which have different I2C addresses.
> >> +		 * Versions 1 or 2 (0 and 3 is reserved) stands for different
> >> +		 * magnetic strengths.
> >> +		 */
> >> +		snprintf(data->name, sizeof(data->name), "tmag5273x%1u", data->version);
> >> +		if (data->version < 1 || data->version > 2)
> >> +			dev_warn(data->dev, "Unsupported device %s\n", data->name);
> >> +		return 0;
> >> +	default:
> > 
> >> +		dev_warn(data->dev, "Unknown device ID 0x%x\n", data->devid);
> >> +		return 0;
> > 
> > And we still continue?! Wouldn't be a problem if that ID drastically changed in
> > terms of programming model and may actually be broken by a wrong sequence?
> 
> It was suggested by Jonathan to just print a warning instead of
> returning with -ENODEV. Reason was "Often manufacturers spin new
> versions of chips that are compatible enough that we give them a
> fallback compatible in device tree.". For me this makes sense.

Ah, I see. Maybe adding a comment summarizing above?

> >> +	}

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2022-11-30 17:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 14:53 [PATCH v5 0/3] add ti tmag5273 driver Gerald Loacker
2022-11-30 14:53 ` [PATCH v5 1/3] iio: add struct declaration for iio types Gerald Loacker
2022-11-30 14:53 ` [PATCH v5 2/3] dt-bindings: iio: magnetometer: add ti tmag5273 documentation file Gerald Loacker
2022-11-30 14:53 ` [PATCH v5 3/3] iio: magnetometer: add ti tmag5273 driver Gerald Loacker
2022-11-30 15:31   ` Andy Shevchenko
2022-11-30 16:32     ` Gerald Loacker
2022-11-30 17:43       ` Andy Shevchenko [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=Y4eWKdJXOR7hJTF3@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gerald.loacker@wolfvision.net \
    --cc=jahau@rocketmail.com \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.riesch@wolfvision.net \
    --cc=nikita.yoush@cogentembedded.com \
    --cc=robh+dt@kernel.org \
    /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