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 6D75DC761A6 for ; Tue, 21 Mar 2023 18:45:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230400AbjCUSpk (ORCPT ); Tue, 21 Mar 2023 14:45:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59880 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230325AbjCUSpi (ORCPT ); Tue, 21 Mar 2023 14:45:38 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2CDE053DB9 for ; Tue, 21 Mar 2023 11:44:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1679424281; 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: in-reply-to:in-reply-to:references:references; bh=fuPq/q/n2UQFDBdFIY9AeffBgLt18anlB8x0yQm2Zg0=; b=XZSqe98b6WChSiaryKeA87umPzxTeG/mZuwxpLrG4wuPkiB47K/evk1/9Ne+8z+UpWbFTI 1ZSVQYSS2LXsl8qEgbaDOndAfk6I3lh7hKlIkHfUmS1OOAqmrf1ZBcgmnbGFzvm3tCGf7g gTMTw9DfZKXVevLhvLC2TTtwJfFm188= Received: from mail-qk1-f198.google.com (mail-qk1-f198.google.com [209.85.222.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-157-QcOaHFloM4e6i-dKX8l4Bg-1; Tue, 21 Mar 2023 14:44:40 -0400 X-MC-Unique: QcOaHFloM4e6i-dKX8l4Bg-1 Received: by mail-qk1-f198.google.com with SMTP id 195-20020a3705cc000000b00746a3ab9426so948984qkf.20 for ; Tue, 21 Mar 2023 11:44:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679424279; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=fuPq/q/n2UQFDBdFIY9AeffBgLt18anlB8x0yQm2Zg0=; b=uv8O5+7hGZoJIbU1J6pVMsHiHbVC1NdpdtCj5SPg6yRSVHTITz/MxJeRjqS1S9flnM /LejG0KyUvZQe54jAqAG9Fe5cY5kI+lg+T+GAYXPiDZqmVcflo1fAF6hnVbZwzzf4YoT nhNeaRgY4aPUaleigrao/1py+ulQ4s3Xgc9KcVDyMW049kwWnF35Zk0VWJrjgtq0554R 4UMLxN3/Ujj5wW2h4d4JR4nHHyNVMRHL8rQsGhae5gVO4jAUi8C5Kz43aQ5AXFnCLryd or9V0ktkXr4x6O/y3s88Vw1tNr/plA4PkTnPN83smWk4vY4ha5OdhquCinyMHGGXaT42 omiw== X-Gm-Message-State: AO0yUKVZvj8jo4rOSyqjzrx/y98mTQAM/dzy1+djSkKEw/wkgMNLjmQS E5Nqykai75/GqrCVnDu6br7CFd3IBk2G9LD2NiXYwQ27T/isy3Ks5WbqW3+E8flWwvSAYfLkAQr TwFbArwgp9L+KAVps9LqTZL1t X-Received: by 2002:a05:622a:314:b0:3db:9289:6946 with SMTP id q20-20020a05622a031400b003db92896946mr1944721qtw.0.1679424279511; Tue, 21 Mar 2023 11:44:39 -0700 (PDT) X-Google-Smtp-Source: AK7set90RizWeWzAQuOQOBvfTCwkzx+74B8QQPTScDsieskr674HwVX05tKIvLoFJq5kExR+Z/9F5w== X-Received: by 2002:a05:622a:314:b0:3db:9289:6946 with SMTP id q20-20020a05622a031400b003db92896946mr1944696qtw.0.1679424279210; Tue, 21 Mar 2023 11:44:39 -0700 (PDT) Received: from halaney-x13s (104-53-165-62.lightspeed.stlsmo.sbcglobal.net. [104.53.165.62]) by smtp.gmail.com with ESMTPSA id 2-20020a05620a040200b006f9f3c0c63csm9793316qkp.32.2023.03.21.11.44.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 21 Mar 2023 11:44:38 -0700 (PDT) Date: Tue, 21 Mar 2023 13:44:35 -0500 From: Andrew Halaney To: Jakub Kicinski Cc: linux-kernel@vger.kernel.org, agross@kernel.org, andersson@kernel.org, konrad.dybcio@linaro.org, davem@davemloft.net, edumazet@google.com, pabeni@redhat.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, vkoul@kernel.org, bhupesh.sharma@linaro.org, mturquette@baylibre.com, sboyd@kernel.org, peppe.cavallaro@st.com, alexandre.torgue@foss.st.com, joabreu@synopsys.com, mcoquelin.stm32@gmail.com, richardcochran@gmail.com, linux@armlinux.org.uk, veekhee@apple.com, tee.min.tan@linux.intel.com, mohammad.athari.ismail@intel.com, jonathanh@nvidia.com, ruppala@nvidia.com, bmasney@redhat.com, andrey.konovalov@linaro.org, linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, ncai@quicinc.com, jsuraj@qti.qualcomm.com, hisunil@quicinc.com, echanude@redhat.com Subject: Re: [PATCH net-next v2 00/12] Add EMAC3 support for sa8540p-ride Message-ID: <20230321184435.5pqkjp4adgn6cpxy@halaney-x13s> References: <20230320221617.236323-1-ahalaney@redhat.com> <20230320202802.4e7dc54c@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230320202802.4e7dc54c@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 20, 2023 at 08:28:02PM -0700, Jakub Kicinski wrote: > On Mon, 20 Mar 2023 17:16:05 -0500 Andrew Halaney wrote: > > This is a forward port / upstream refactor of code delivered > > downstream by Qualcomm over at [0] to enable the DWMAC5 based > > implementation called EMAC3 on the sa8540p-ride dev board. > > > > From what I can tell with the board schematic in hand, > > as well as the code delivered, the main changes needed are: > > > > 1. A new address space layout for /dwmac5/EMAC3 MTL/DMA regs > > 2. A new programming sequence required for the EMAC3 base platforms > > > > This series makes those adaptations as well as other housekeeping items > > such as converting dt-bindings to yaml, adding clock descriptions, etc. > > > > [0] https://git.codelinaro.org/clo/la/kernel/ark-5.14/-/commit/510235ad02d7f0df478146fb00d7a4ba74821b17 > > > > v1: https://lore.kernel.org/netdev/20230313165620.128463-1-ahalaney@redhat.com/ > > At a glance 1-4,8-12 need to go via networking, 5 via clock tree, > and 6,7 via ARM/Qualcomm. > > AFAICT there are no strong (compile) dependencies so we can each merge > our chunk and they will meet in Linus's tree? If so please repost just > the networking stuff for net-next, and the other bits to respective > trees, as separate series. > That makes sense to me, thanks for the advice. The only note is that 5 (the clk patch) is depended on by 6/7 to compile (they use the header value in 5)... So I'll keep those together! So all in all it will be the dt-binding changes + stmmac changes in one series for networking, and the clock + devicetree changes via ARM/Qualcomm if I am following properly. I'll go that route for v3 and link here (just to make finding the split easier) unless someone objects (got some time as I need to refactor based on series feedback)! Thanks, Andrew