From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BD8C2CEDDBD for ; Fri, 11 Oct 2024 07:04:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date: MIME-Version:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=jJS99CP66Czeek9OTXCx0i7J11bJHXKEYklS5RBKyCc=; b=o3mpHlh4bhOEFlJixIeaMpU/FN XsW+jSCFUK0PlQehZ5btk/5N407vzFof+Gj/sCXWc9o44OYbNlMowNsN83QvEu1csZ69K76k7TiK5 luPtX0NURa8UMvzZ7B6ublpxj887/2heNiDihcobRHbciGQZlDsLkgmr323uF12zcOuQck6xnOKrd ob9T38MjwPUilfD4NgfSfiGZQV/MXBnX2n+Cm+GCM9W2RtyQezAHjh6odGzNEg/ypURB8MEbKdPvA 5w6IVj+qzGaXL2n+jr4iSs5gJ+wTuL/zZcXbQwNKYzRWMxiCwqOXlQMgt9WS6LIW9ZBSEh/O81ae1 AhAj8O4A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1sz9hU-0000000FUBH-4AsZ; Fri, 11 Oct 2024 07:04:36 +0000 Received: from mail.manjaro.org ([2a01:4f8:c0c:51f3::1]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1sz9ZK-0000000FSo2-0oc2; Fri, 11 Oct 2024 06:56:12 +0000 MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=manjaro.org; s=2021; t=1728629767; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jJS99CP66Czeek9OTXCx0i7J11bJHXKEYklS5RBKyCc=; b=vo+V9xE8SzMr8AIcvJX9/oxaqhH6UG+OkajEt5hqd1d71I9zxln6wUOYYMmhFlhzPIi5fv tGBRPIjlimg2rdOCw/te1SNpxgyWMkXKRfUt23EP/DeSoDjsoJvyhNW4xh3sz0rkWYJfXk xaEhBNHNb7FvFoGS4Co/N4392UfAjP6G2SToAFpcrmBfHST2dBEk9CJstMJHlBo6YsGVS5 zJfZouacvTiE/L9IRFVxsfshIUjjABcKLHUUBW4pJE724ES61dPWu7c8SrVcvJLuXi+mqp y6Z7Q5gkPjTivhVZervWUWYpduaFRuBvzga1wkmVpl0DGN9wqWK8qBmyUk98sA== Date: Fri, 11 Oct 2024 08:56:07 +0200 From: Dragan Simic To: =?UTF-8?Q?Heiko_St=C3=BCbner?= Cc: linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org Subject: Re: [PATCH] arm64: dts: rockchip: Add dtsi file for RK3399S SoC variant In-Reply-To: <46729153.fMDQidcC6G@diego> References: <59c524a9a12465c21e01b779b42749fae148c41d.1728482151.git.dsimic@manjaro.org> <46729153.fMDQidcC6G@diego> Message-ID: X-Sender: dsimic@manjaro.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Authentication-Results: ORIGINATING; auth=pass smtp.auth=dsimic@manjaro.org smtp.mailfrom=dsimic@manjaro.org X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241010_235610_557756_D70C27EB X-CRM114-Status: GOOD ( 11.66 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello Heiko, On 2024-10-10 22:24, Heiko Stübner wrote: > Am Mittwoch, 9. Oktober 2024, 16:06:00 CEST schrieb Dragan Simic: >> The way the introduced RK3399S SoC variant dtsi file (rk3399s.dtsi) is >> named >> diverges from the way the two already present RK3399 SoC variant dtsi >> files >> (rk3399-op1.dtsi and rk3399-t.dtsi) are named, but that simply follows >> the >> commonly used and/or the official RK3399 SoC variant names. > > This is my only gripe with this ;-) . > > I.e. looking through simple google, the rk3399t also seems to be > written > without "-" most of the time. > > Though for me it would make the most sense to just go with "rk3399-s" > here for some sort of clear style between -s -t and -op1 Believe it or not, the inconsistency of having no dash before the "s" has bothered me too. :) Let's add the dash, which I'll do in the v2.