Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp6270013rwl; Thu, 29 Dec 2022 09:56:59 -0800 (PST) X-Google-Smtp-Source: AMrXdXvLl1pzftQjzLs9+IcaKqz9nWkS22fc7gb3q0r0GavanqRIGrlRFvippaJ7IbLQZusxCCeA X-Received: by 2002:a17:906:b00c:b0:7c4:fa17:7202 with SMTP id v12-20020a170906b00c00b007c4fa177202mr24089548ejy.33.1672336619803; Thu, 29 Dec 2022 09:56:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672336619; cv=none; d=google.com; s=arc-20160816; b=omCpjF9WbYFacivrUbrOnWVR1ug0KwuqFAnOTudruG/j8URNdyXyAoY/ehB2fwGoF3 JIUHYDR2c3nc8JuswwUHyqD+Frjw5M99KqmrZllM+fxGDCK2gnCRiBJjxRkHeu6wQK3k fFL11VZcV9ht9f01n8zlJ7wKrIGCLdXOyOfg8N9IzLYzaPpPHciBhhGJMSkqEHA0xBkh PUjyqckwEaQAuGqiIMzZXLFkfTypGuNv4q9mXoYodqDWUlx+N7NnZqnj1ROseuFaPVBm gOg23wYh0XdLr+yRHlucd4bTlEQzKQmUcHZ15pGekNfAKhfzIjilMGrfRO5iWV+/rwND xeBA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:mail-followup-to:message-id:subject:cc:to:from:date; bh=C2HrTxhZmx38GQC51LOWpp50sOO0DOc7u60idukPXhA=; b=N5o6TjX2uQxTBgR/2C/+5J3GvwfwoD+9V1kDdCR+YjOBJY+d/aYcjRxt3uZOz0/lOa CBXCuNtcqXcKAF2T8dTTzmoWflWm9Tppl8Vq0o7N7jlHi4Z1BKdLfRGNjcdCt7cXbh1t cto8bdxhf77BZJDgnaOlVnSrOaE55vSlpD+opVI6wWOkBYC+92YXMWsTYS5WVBcfPDgn Ya43DXUDav5axuMwI9aeJSRzPhdy+XpS+R6IlAJ9J0Cg6+wGfxopbcxg+HJoE9Qh0R/L ablUupR6QuQQqSF9Xtd0DqE4H5WJaTJmWtiNq8OjQRgKG0InqG9kkwErZ7gLeHZnL5gr d3yg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id xc3-20020a170907074300b007825337afeesi15847205ejb.273.2022.12.29.09.56.45; Thu, 29 Dec 2022 09:56:59 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233504AbiL2RWD (ORCPT + 62 others); Thu, 29 Dec 2022 12:22:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49490 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233814AbiL2RWA (ORCPT ); Thu, 29 Dec 2022 12:22:00 -0500 Received: from relay04.th.seeweb.it (relay04.th.seeweb.it [IPv6:2001:4b7a:2000:18::165]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EB6CE140A8 for ; Thu, 29 Dec 2022 09:21:58 -0800 (PST) Received: from SoMainline.org (94-211-6-86.cable.dynamic.v4.ziggo.nl [94.211.6.86]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by m-r1.th.seeweb.it (Postfix) with ESMTPSA id 6181A1F98E; Thu, 29 Dec 2022 18:21:55 +0100 (CET) Date: Thu, 29 Dec 2022 18:21:48 +0100 From: Marijn Suijten To: Bjorn Andersson Cc: phone-devel@vger.kernel.org, Andy Gross , Rob Herring , ~postmarketos/upstreaming@lists.sr.ht, AngeloGioacchino Del Regno , Konrad Dybcio , Martin Botka , Jami Kettunen , Lux Aliaga , Konrad Dybcio , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/3] arm64: dts: qcom: sm6125: QUPs, SPI and Seine I2C buses Message-ID: <20221229172148.2hcmi7uypwlnxmhu@SoMainline.org> Mail-Followup-To: Marijn Suijten , Bjorn Andersson , phone-devel@vger.kernel.org, Andy Gross , Rob Herring , ~postmarketos/upstreaming@lists.sr.ht, AngeloGioacchino Del Regno , Konrad Dybcio , Martin Botka , Jami Kettunen , Lux Aliaga , Konrad Dybcio , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20221216233408.1283581-1-marijn.suijten@somainline.org> <20221229171301.7sjbyvqpn3qjwexu@builder.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221229171301.7sjbyvqpn3qjwexu@builder.lan> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022-12-29 11:13:01, Bjorn Andersson wrote: > On Sat, Dec 17, 2022 at 12:34:05AM +0100, Marijn Suijten wrote: > > Introduce Qualcomm Universal Peripheral support on SM6125 and define all > > known SPI and I2C Serial Engines. On Sony Seine PDX201 all I2C buses > > with known-connected hardware are enabled for future hardware mapping, > > together with the respective GPI DMA 0 and QUP 0. > > > > Changes since v1: > > - Un-downstream pinctrl mapping: > > - Remove nested mux {} / config {}; > > - Remove useless comments; > > - Remove unreferenced pinctrl states; > > - Use qup14 pinctrl function name instead of unknown qup_14; > > - Reword commit message; > > - Add iommus to QUP nodes now that this series depends on apps_smmu to > > be available; > > - Reorder all properties to match other SoCs; > > - Reorder/intersperse QUP nodes with GPI DMA nodes to maintain sorting > > by address; > > - Reorder SPI nodes to fit in with I2C nodes, restoring sorting by > > address too; > > - Use QCOM_GPI_* constants; > > - Adhere to 3 instead of 5 dma cells for gpi_dma. > > > > v1: https://lore.kernel.org/all/20221001185628.494884-1-martin.botka@somainline.org/T/#u > > > > Depends on: > > - SM6125 APPS SMMU: https://lore.kernel.org/linux-arm-msm/20221216215819.1164973-1-marijn.suijten@somainline.org/T/#u > > - SM6125 GPI DMA: https://lore.kernel.org/linux-arm-msm/20221216231528.1268447-1-marijn.suijten@somainline.org/T/#u > > Please, in the future, when you have dependencies between your dts > patches, send them together so I don't need to go on a treasure hunt in > my mailbox to figure out which order to apply things... I was quite confident separating out "unrelated" patches in separate series was preferred, especially when dependencies are marked explicitly like this... what changed? (Aside that, would I then call this a v4+v2+v2?) - Marijn