Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp660113rwr; Fri, 5 May 2023 03:08:13 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ50KccldbX0s8aziCttp7ULROPcMGKfJZ6AgzQK7v7jeDyxZmCFkdkNzaM+pYy+PAoJdYRH X-Received: by 2002:a17:902:7c07:b0:1a8:bc5:4912 with SMTP id x7-20020a1709027c0700b001a80bc54912mr751948pll.52.1683281293156; Fri, 05 May 2023 03:08:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683281293; cv=none; d=google.com; s=arc-20160816; b=iFk3Jym+vVooXzh4exehUGDUtt2W1qFDngqGEuzDvHE6nNkVFBshvbZvYKKU0BBH2f +6Q1BPIBJUMSgo7cJOAyD7mRaFaK3rxz0g+eDERX6Y9mm3yuLHc8qiwzJcpbkzbBbi7j HBVj1iNtLDp7ulyQ4t0+S79bFgCOFQptNPXfuJuXn45jwfXUfocLGz8Ew1aeYBPj4BOT pZxzIxR+i7c0n79mzyLPWtRUTmBa6pd1OfmQdWBtAt7HWp+hV/FYZr5nIfLftPQ/y3UD xwEdRaFE6KFcCQRlriR82MSzzFS6+xzEFI2RHRJ3hyzRpOl28jq1GUsxNukzK7PI1qnB KEsw== 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:message-id:subject:cc:to:from:date; bh=Ct5cIGg/ztSG8SFg7pff4ZCDC/uSYBNXlBMvH92NzUo=; b=ByCbkWIfvK9PhCrjuJ/xKW3vAREsmb1rrcP8jUUwAM1Za4Umze9bNbiUgOYT+kODM+ OrQg7ml9gQXVcm/2d4C7nwf0R9T7H9m1CVLi/2P3JWaPCg/G562ejajUaK4yRyIBFfL4 NXzAvjP7yWG0XtmDEDE1AGYf1ChVfrWwEDUW5C5vY/SwQ47O2ESy8WS7EkOuI/VSBQbw ZRJq70KE37CaJX2dtIP4a2RLm+inPKU6F+6R6tYL3ibW9FDl9Hd1/awVgHYyz4nhvHbh 1KV7hgwZMnzIMkk4q8ik1MFzuItD0ZNKBpsdICsHhjIZRAJvxHzlLsljBveAYfsQOlE1 bplA== 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 r9-20020a1709028bc900b001aaea258805si1336352plo.134.2023.05.05.03.07.56; Fri, 05 May 2023 03:08:13 -0700 (PDT) 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 S231797AbjEEJjp (ORCPT + 99 others); Fri, 5 May 2023 05:39:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45732 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231800AbjEEJjk (ORCPT ); Fri, 5 May 2023 05:39:40 -0400 Received: from muru.com (muru.com [72.249.23.125]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 5C1681A109; Fri, 5 May 2023 02:39:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 5848F80FC; Fri, 5 May 2023 09:39:31 +0000 (UTC) Date: Fri, 5 May 2023 12:39:30 +0300 From: Tony Lindgren To: Nishanth Menon Cc: Wadim Egorov , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-hardening@vger.kernel.org, upstream@lists.phytec.de, vigneshr@ti.com, kristo@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, keescook@chromium.org, tony.luck@intel.com, gpiccoli@igalia.com Subject: Re: [PATCH 2/2] arm64: dts: ti: Add basic support for phyBOARD-Lyra-AM625 Message-ID: <20230505093930.GS14287@atomide.com> References: <20230504140143.1425951-1-w.egorov@phytec.de> <20230504140143.1425951-2-w.egorov@phytec.de> <20230504142643.pkzsftrsrqph4vql@banked> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230504142643.pkzsftrsrqph4vql@banked> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham 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 * Nishanth Menon [230504 14:33]: > Just wondering: if the carrier board can easily work with different > SoMs.. in which case, we could do overlay to create the som + carrier > overlay to create rdk dtb - this might allow the scheme to scale to > additional SoMs and carrier combinations.. and the SoM dtb could be > sufficient for something like a bootloader. It might be best to limit the overlay usage to devices that might see dual use on the carrier board.. Not sure if setting up the entire carrier board makes sense as an overlay :) Not sure if folks want to debug boot issues on a remote server for example if an overlay is needed to boot with Ethernet :) Regards, Tony