From: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>,
Luca Weiss <luca.weiss@fairphone.com>
Cc: "Jorijn van der Graaf" <jorijnvdgraaf@catcrafts.net>,
"Jonathan Cameron" <jic23@kernel.org>,
linux-iio@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
devicetree@vger.kernel.org, "Kees Cook" <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] iio: light: stk3310: support the Sensortek STK36C61
Date: Tue, 1 Sep 2026 04:55:02 +0200 [thread overview]
Message-ID: <20260901025502.231703-1-jorijnvdgraaf@catcrafts.net> (raw)
In-Reply-To: <apYqUv_uuqZlhtOh@debian-BULLSEYE-live-builder-AMD64>
On Mon, Aug 31, 2026 at 10:28:50PM -0300, Marcelo Schmitt wrote:
> Never mind, I completely missed the point of it having a preliminary datasheet.
> It might be sensible to try to estimate if the final version will keep the same
> name and PDT_ID.
On the name: the Fairphone 6 repair document's block diagram labels
the part "3IN1 ALPS/RGB sensor/STK36C61", without the A ([1], page
107), while the LCSC and JLCPCB listings carry the -A name. The
diagram is provenance rather than proof because the same page
misrenders two other part names and I have not read the package
marking itself.
The driver name would follow the existing family convention either
way: this driver already binds the four STK3311 variants (STK3311,
-A, -S34, -X), each with its own chip ID in stk3310_chip_ids, under
the single name "stk3311".
On the ID: the published sheet says 0x93, Luca's 0.9.2 revision says
0x95, and the part in the phone reads 0x95. stk3310_chip_ids is a
flat accept-list, so if a final sheet moved the ID again it would be
added alongside, not swapped.
Luca, can you confirm which part is actually in the device, the
STK36C61 or the STK36C61-A?
[1] https://www.fairphone.com/wp-content/uploads/2025/08/Fairphone-Gen.-6_-Information-on-how-to-repair-dispose-of-and-recycle-EN-NL-FR-DE.pdf
Thanks,
Jorijn
next prev parent reply other threads:[~2026-09-01 2:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 17:54 [PATCH v2 0/5] iio: light: stk3310: per-chip match data and STK36C61 support Jorijn van der Graaf
2026-08-26 17:54 ` [PATCH v2 1/5] iio: light: stk3310: lower-case the i2c device ID names Jorijn van der Graaf
2026-08-26 18:03 ` sashiko-bot
2026-08-27 6:45 ` Andy Shevchenko
2026-08-26 17:54 ` [PATCH v2 2/5] dt-bindings: iio: light: stk33xx: document the Sensortek STK36C61 Jorijn van der Graaf
2026-08-26 17:54 ` [PATCH v2 3/5] iio: light: stk3310: move the data registers into the channel address Jorijn van der Graaf
2026-08-26 18:07 ` sashiko-bot
2026-08-27 6:47 ` Andy Shevchenko
2026-08-26 17:54 ` [PATCH v2 4/5] iio: light: stk3310: add per-chip match data Jorijn van der Graaf
2026-08-26 18:03 ` sashiko-bot
2026-08-27 7:47 ` Andy Shevchenko
2026-08-26 17:54 ` [PATCH v2 5/5] iio: light: stk3310: support the Sensortek STK36C61 Jorijn van der Graaf
2026-08-27 7:53 ` Andy Shevchenko
2026-08-28 4:18 ` Marcelo Schmitt
2026-08-28 15:47 ` Jorijn van der Graaf
2026-08-30 15:03 ` Marcelo Schmitt
2026-08-30 20:19 ` Jorijn van der Graaf
2026-08-31 7:53 ` Luca Weiss
2026-09-01 0:54 ` Marcelo Schmitt
2026-09-01 1:28 ` Marcelo Schmitt
2026-09-01 2:55 ` Jorijn van der Graaf [this message]
2026-09-01 6:57 ` Luca Weiss
2026-08-30 23:48 ` [PATCH v2 0/5] iio: light: stk3310: per-chip match data and STK36C61 support 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=20260901025502.231703-1-jorijnvdgraaf@catcrafts.net \
--to=jorijnvdgraaf@catcrafts.net \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=gustavoars@kernel.org \
--cc=jic23@kernel.org \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=marcelo.schmitt1@gmail.com \
--cc=nuno.sa@analog.com \
--cc=robh@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