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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C27CBC433F5 for ; Tue, 11 Oct 2022 18:59:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229818AbiJKS7g (ORCPT ); Tue, 11 Oct 2022 14:59:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48474 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229757AbiJKS73 (ORCPT ); Tue, 11 Oct 2022 14:59:29 -0400 Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 923F188DC2 for ; Tue, 11 Oct 2022 11:59:27 -0700 (PDT) Received: by mail-qk1-x734.google.com with SMTP id d13so2785204qko.5 for ; Tue, 11 Oct 2022 11:59:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=0wCN5RZ+L8i/oN57QmIvmcE2DqsyjZQyxM8LL5Wvecw=; b=OYOpwA00168+Sn1npw1oL58Fo+MJaQyLFCqVdGdf7vXkNFi5pgDHeSYPE265v1fk3U 43cUJtNVbasO+3J8ihdCrso3YZH+bnE97UgGQ+WJjjFdrITLESiIYyCVUuLH9IWdZQyJ +koIQr96yAJFGMwL99V3TmFC//4vyOQcXDoWqPklpIRVAivPFyT0IWAX2HdH7Zc6CUxz Cgf+zeA+6PeM8xj8bzTnIfnfvQ5a/QDGI4MxHIHPX97wz0remhhzrHMohvtAIPfLo4ET j0Gw2MOzKHFNiqpXycHEwEKkAuyJd9GrUdzArT3sOGgiq2ihXRyAoBwf0EeXn6kcEfT4 9IzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=0wCN5RZ+L8i/oN57QmIvmcE2DqsyjZQyxM8LL5Wvecw=; b=zSo1Kx1vKUlZpz4VLbTFltMGm+0LT9yKBpQ1LqGXj0CJz2QSZUMK8uGUZr3xPO3jTC Mdpc07Yurl4fei/AdOEVxY92Q1Udc3AUln1CQw1Yo40tBP3PIyhuLRaW0k+rldkf5hKH nZnlqwdWx/g9a+cHW5U+NSAy8AXLlji0/RryWIsITnS6GqK3sYrCG2wR8EOflRwDElXX xyvWltHBNPnKBmp7iUBgQZ/MyjVD3hnvjqg5t/Crhv8xlXYKilyE2cVvKkIO16iuiRAg /CHqCHGAnqyQx6gQBrOut4nnR6R22oOLkZl7wM+BILXPqe1zVUsijksPL7K4m5trvsyL 6SNA== X-Gm-Message-State: ACrzQf2rDJIrH/JZswVt9A3iwxVy6UrViB3WvYmkB6TiAdZMZDUAQHYw dXdFyu4WaX6De9qvdXuUVV07Mg== X-Google-Smtp-Source: AMsMyM6Bn+yZ7GM457z+pCMlyEfivAVrDfm1n7o3H+EW0SKcPQs+s0LIDrkPQj1pe2vx0w6xMzD1bw== X-Received: by 2002:a05:620a:6017:b0:6ce:3c51:66b9 with SMTP id dw23-20020a05620a601700b006ce3c5166b9mr18110981qkb.605.1665514766652; Tue, 11 Oct 2022 11:59:26 -0700 (PDT) Received: from [192.168.1.57] (cpe-72-225-192-120.nyc.res.rr.com. [72.225.192.120]) by smtp.gmail.com with ESMTPSA id c2-20020ac87dc2000000b0039a8b075248sm4688296qte.14.2022.10.11.11.59.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 11 Oct 2022 11:59:25 -0700 (PDT) Message-ID: Date: Tue, 11 Oct 2022 14:57:13 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.2 Subject: Re: [PATCH 03/19] arm64: dts: qcom: qdru1000: Add tlmm nodes Content-Language: en-US To: Melody Olvera , Andy Gross , Bjorn Andersson , Rob Herring , Krzysztof Kozlowski Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20221001030656.29365-1-quic_molvera@quicinc.com> <20221001030656.29365-4-quic_molvera@quicinc.com> <7674b756-75d5-6ca3-d4fe-c54bd92a3fd7@quicinc.com> From: Krzysztof Kozlowski In-Reply-To: <7674b756-75d5-6ca3-d4fe-c54bd92a3fd7@quicinc.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/10/2022 14:48, Melody Olvera wrote: > > > On 10/1/2022 2:14 AM, Krzysztof Kozlowski wrote: >> On 01/10/2022 05:06, Melody Olvera wrote: >>> Add tlmm node for the QDU1000 and QRU1000 SoCs and the uart pin >>> configuration. >> The patchset should be squashed with previous. There is no point in >> bringing support piece by piece. You can bring support in steps if you >> submissions are separate in time. But if you have everything ready - >> your patch must be complete and bisectable. > To be clear, does it make more sense to submit the base dt first, then submit each > driver with all the dt changes as one patchset? No, because you have DTS ready. There is no incremental work here. Best regards, Krzysztof