From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-106113.protonmail.ch (mail-106113.protonmail.ch [79.135.106.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 66A5F3F3270; Tue, 4 Aug 2026 14:35:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=79.135.106.113 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785854145; cv=none; b=nIJuFbJX7dWOCFZPnIYEBo02Hqju4ly9yYNUtVpPygZjaVjBFUUYYJTfc9NH0BssAfdg8llVVGFw5cDAIBfoHf/eanUcGvZV9isZtd3dU1DINDoKxmrB8reGj+YnNFyiGMCKZgdlFP0KbZq3Kn2dTD8Ju40y7uus81/zN2Npog0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785854145; c=relaxed/simple; bh=klPzKzrG3VbkJnJUHINxPqEMDHhiQvV/o/b3ZahuIrM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=WzaIQAxuPwCsruJKd8uFk4ZE6b8ZeLCJoOcCPR988RV8aN8F8HxX4q87qpVJIc05YCYruVJl4N8yNRzmroDh5xHMUhMwFJ5i4U7f8N/SaGQaiotzgyWqCLvEbjbrJjT1h0d5qBeuLg64W1l2RrR9r+6pfOfT/6Hu2NBs9ZB2byg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=geanix.com; spf=pass smtp.mailfrom=geanix.com; dkim=pass (2048-bit key) header.d=geanix.com header.i=@geanix.com header.b=Kl01eEYG; arc=none smtp.client-ip=79.135.106.113 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=geanix.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=geanix.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=geanix.com header.i=@geanix.com header.b="Kl01eEYG" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=geanix.com; s=protonmail3; t=1785854133; x=1786113333; bh=89HwBQw+GSLg6utOGg8Ydnn1rVuwDCSYF9R+2PaebFM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID:From:To: Cc:Date:Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=Kl01eEYG7Cg8mqEfsQyBekxDBv1/bQTCWwP7yaM1uaXnv4JPRVoT6q+wFhy22trQH FPXPQePyxMz6sPHjaEQ404mtHUzdN2GD2XYKdjGq0iq3ezUS8nn+tLr3xqxNA22gK9 MJPKzGmmhaDVOlKnZ9YrEQixF6Pcl3Cm7eCKIK9YvNSStw6tt50kQ9fJoGSxr7axq7 S7tJDiqRuDC5YtP1BMHqcp6dJSeCz/pDMdeOpzIOf3v9L3wlxP37JTrP7hhBU3lKHS 7jqpUDrDVFq4m8qw1xBACIwt8OMJMBlkUh8n+gokNYQhyuFCvW4zW2NtPklG2b8C/k ReFTw+hD27jOw== X-Pm-Submission-Id: 4hDx0c2CrRz2Scps From: Esben Haabendal To: "Jonathan Cameron" Cc: "Krzysztof Kozlowski" , "David Lechner" , Nuno =?utf-8?Q?S=C3=A1?= , "Andy Shevchenko" , "Rob Herring" , "Krzysztof Kozlowski" , "Conor Dooley" , "Nikita Travkin" , "Maslov Dmitry" , , , Subject: Re: [PATCH v2 2/4] dt-bindings: iio: light: ltr501: Add ltr329 compatible In-Reply-To: <20260719023830.5f99d335@jic23-huawei> (Jonathan Cameron's message of "Sun, 19 Jul 2026 02:38:41 +0100") References: <20260715-liteon-ltr329-v2-0-d18af55edab5@geanix.com> <20260715-liteon-ltr329-v2-2-d18af55edab5@geanix.com> <20260716-adept-kraken-of-calibration-cddebc@quoll> <9Ekqt5M10zvl-oDffITzNkebHtnMwG2Z_kIEqGL-cokgqKRyNyFxqCB5wZZelUe9dEO9EWhjqt59zBsqU7jMbg==@protonmail.internalid> <20260719023830.5f99d335@jic23-huawei> Date: Tue, 04 Aug 2026 16:35:27 +0200 Message-ID: <87ldamar80.fsf@geanix.com> User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain "Jonathan Cameron" writes: > On Thu, 16 Jul 2026 16:14:55 +0000 > Esben Haabendal wrote: > >> On Thursday, 16 July 2026 at 10:07, Krzysztof Kozlowski wrote: >> >> > On Wed, Jul 15, 2026 at 02:27:24PM +0200, Esben Haabendal wrote: >> > > LTR-329ALS-01 is an ambient light sensor similar to LTR-303ALS-01, but >> > > without interrupt support. >> > > >> > > Signed-off-by: Esben Haabendal >> > > --- >> > > Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml | 1 + >> > > 1 file changed, 1 insertion(+) >> > > >> > > diff --git a/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml b/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml >> > > index ab9bb68dd736..76e81eba7ea4 100644 >> > > --- a/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml >> > > +++ b/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml >> > > @@ -19,6 +19,7 @@ properties: >> > > - liteon,ltr559 >> > > - liteon,ltr301 >> > > - liteon,ltr303 >> > > + - liteon,ltr329 >> > >> > Do not grow lists at the end, they are ordered alphanumerically to avoid >> > conflicts. >> >> Placing the new entry at the top would produce a rather strangely order list: >> >> ltr329 >> ltr501 >> ltr559 >> ltr301 >> ltr329 >> >> Should I add a patch sorting the entire list to avoid this kind of >> confusion in the future? > > Please do a precursor patch for that Also do it for the id tables in the driver. Ok. Sorting ltr501_id and ltr501_of_match should be trivial. But what about ltr501_chip_info_tbl (and the anonymous enum used to index it, should they be sorted as well? And ltr301 being 0 instead of ltr501, the original device the driver was written for? /Esben