Hi Jorijn, On Tue Sep 1, 2026 at 4:55 AM CEST, Jorijn van der Graaf wrote: > 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?
The BOM I'm viewing clearly states "STK36C61-A". Regards Luca > > [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
