All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Zangerl <az@breathe-safe.com>
To: Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org, Tomasz Duszynski <tduszyns@gmail.com>
Subject: iio: pressure: ms5611: ms5611_prom_is_valid false negative bug [PATCH]
Date: Mon, 18 Sep 2023 09:52:20 +1000	[thread overview]
Message-ID: <922-1694994740.375607@iEuc.VJY0.oC_q> (raw)

[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]

the ms5611 driver falsely rejects lots of MS5607-02BA03-50 chips
with "PROM integrity check failed" because it doesn't accept a prom crc
value of zero as legitimate.

according to the datasheet for this chip (and the manufacturer's
application note about the prom crc), none of the possible
values for the crc are excluded - but the current code
in ms5611_prom_is_valid() ends with

return crc_orig != 0x0000 && crc == crc_orig

datasheet: https://www.te.com/commerce/DocumentDelivery/DDEController?Action=srchrtrv&DocNm=MS5607-02BA03&DocType=Data+Sheet&DocLang=English
application note: https://www.te.com/commerce/DocumentDelivery/DDEController?Action=srchrtrv&DocNm=AN520_C-code_example_for_MS56xx&DocType=SS&DocLang=EN

i've discussed this whith the original author of the driver (tomasz
duszynski) and he indicated that at that time (2015) he was dealing with
some faulty chip samples which returned blank data under some
circumstances and/or followed example code which indicated crc zero
being bad (i can't find any traces of any such online, however).

as far as i can tell this exception should not be applied anymore; we've
got a few hundred custom boards here with this chip where large numbers
of the prom have a legitimate crc value 0, and do work fine, but which the
current driver code wrongly rejects.

(i can provide some example prom dumps if required.)

the attached tiny patch is against 4.19. but that
section of the code is unchanged up to and including 6.6. 


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-ms5611-crc-zero-is-valid-and-should-not-be-rejected.patch --]
[-- Type: text/x-diff, Size: 783 bytes --]

From 653b5cf063e07d126e67386b152e4e76d4f8c1dc Mon Sep 17 00:00:00 2001
From: Alexander Zangerl <az@breathe-safe.com>
Date: Mon, 18 Sep 2023 09:44:00 +1000
Subject: [PATCH] ms5611: crc zero is valid and should not be rejected

---
 drivers/iio/pressure/ms5611_core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/iio/pressure/ms5611_core.c b/drivers/iio/pressure/ms5611_core.c
index 5c7a734ede54..9980c6f3335e 100644
--- a/drivers/iio/pressure/ms5611_core.c
+++ b/drivers/iio/pressure/ms5611_core.c
@@ -79,7 +79,7 @@ static bool ms5611_prom_is_valid(u16 *prom, size_t len)
 
 	crc = (crc >> 12) & 0x000F;
 
-	return crc_orig != 0x0000 && crc == crc_orig;
+	return crc == crc_orig;
 }
 
 static int ms5611_read_prom(struct iio_dev *indio_dev)
-- 
2.30.2


[-- Attachment #3: Signature --]
[-- Type: text/plain, Size: 175 bytes --]

Best Regards,
Alexander Zangerl
IT Engineer

-- 
P +61 7 3276 7833 | M +61 415 482 341
E az@breathe-safe.com | W breathe-safe.com.au
A 62 Mica Street, Carole Park, 4300, QLD


             reply	other threads:[~2023-09-17 23:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 23:52 Alexander Zangerl [this message]
2023-09-18 11:05 ` iio: pressure: ms5611: ms5611_prom_is_valid false negative bug [PATCH] Jonathan Cameron
2023-09-20  0:01   ` [PATCH v1] iio: pressure: ms5611: ms5611_prom_is_valid false negative bug Alexander Zangerl
2023-09-30 17:37     ` Jonathan Cameron

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=922-1694994740.375607@iEuc.VJY0.oC_q \
    --to=az@breathe-safe.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=tduszyns@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.