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 CA0C6C433EF for ; Wed, 8 Dec 2021 08:20:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244734AbhLHIYP (ORCPT ); Wed, 8 Dec 2021 03:24:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39890 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231496AbhLHIYM (ORCPT ); Wed, 8 Dec 2021 03:24:12 -0500 Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BD08DC061746 for ; Wed, 8 Dec 2021 00:20:40 -0800 (PST) Received: by mail-wm1-x329.google.com with SMTP id o29so1189185wms.2 for ; Wed, 08 Dec 2021 00:20:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=1w3QG5L2wJSdawJv13n1fbqmjL3sgSHFT+7XbyAvU6U=; b=55DNvAYxUXa+yKMvFNkcwxQcyuMG4hyrlqdl8GCYFqXE/nvB5hzQFKynb0amMmXyPj gvr6FYs5uEqtTr3S1cxwe8elBx06xxnm+aXZmnSmTpE4iBiqlMFjwG+Li/AZafgjjQ/J kfVWr21Ir4haj+rGGcA+A6kC8FsP9DhwqqdIrnTSjtTK4yLGw15m+Fd/QX/zYcNaeN60 jtM6G0eR3psmmQ/Vrui/nwb1ZCQ7eo7nG2CngnGrj5nFE7X5MYrE/QmSZM/j7QIf17OY st+lLoPx7tEWVC/AA0P3vn93dIiI37Cp8OTaqRFkScrNd9NRbxdAWoF5gSyjRXVXUDfE vffQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=1w3QG5L2wJSdawJv13n1fbqmjL3sgSHFT+7XbyAvU6U=; b=tZQSTsahRNCGycO2j9RJHL8xIcc3bfFasNAPfAzF8Q2VO5I3epl0DACMvnE3afI2uC WvOHPEH7bw4EhfAYHawv3Llg/wVCHGxzITdP+cbG675H2Ky9hViXBhq6lZyqcIJU/bkT 5iAbw/g9dtFDjIpvDW8WBVde28c2+b6HyD5eArUnznwWWsIzLVHIhTQqtZJSQsfa4oSf NlCtCnNY8gQ8D88yRujcb21+eAoNuKjrjwWO8nvdShd97PAykZfrvZ13EJhjri16AqR1 xIpuGeX7hv0Jil4rhNA82C56VSZAHtlxXYdkgDHfSnAxikTezQtHYVlvkLQAtkU6eNqf R/Hw== X-Gm-Message-State: AOAM530YAEjLixHgdZkH11kLkiPmcpHbAL32GzU/9sMhXzgZlxdQl5AL tQxT2ctI1aod1ZK9xK4sbKLmuw== X-Google-Smtp-Source: ABdhPJzG/TNg3Piyp5TseF8rLfJFvZTaZFXGKZz5otMT3tS+daO2oHy7ZCllGK9433G4TB+hyrdAQg== X-Received: by 2002:a7b:c24a:: with SMTP id b10mr14015235wmj.166.1638951639255; Wed, 08 Dec 2021 00:20:39 -0800 (PST) Received: from ?IPv6:2001:861:44c0:66c0:5245:80ea:cf46:35bb? ([2001:861:44c0:66c0:5245:80ea:cf46:35bb]) by smtp.gmail.com with ESMTPSA id i7sm2022410wro.58.2021.12.08.00.20.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Dec 2021 00:20:38 -0800 (PST) Subject: Re: [RFC PATCH 0/9] arm64: dts: meson: add support for aac2xx devices To: Kevin Hilman , Christian Hewitt , Rob Herring , Mark Rutland , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Benoit Masson References: <20211130060523.19161-1-christianshewitt@gmail.com> <7hilw14nhx.fsf@baylibre.com> From: Neil Armstrong Organization: Baylibre Message-ID: Date: Wed, 8 Dec 2021 09:20:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <7hilw14nhx.fsf@baylibre.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/12/2021 19:06, Kevin Hilman wrote: > Christian Hewitt writes: > >> This series adds support for several popular Amlogic S905X3 (SM1) Android >> Set-Top Box devices. Like most Android box devices, they ship in variants >> with multiple RAM, eMMC, WiFi and BT configurations. RAM and eMMC are not >> something we need to consider to get a working boot, but we do need to get >> the correct connectivity spec. > > The reason we don't need to care about RAM differences is because u-boot > takes care of that, and updates the DT nodes accordingly. > > In general, I'm not a fan of leaving these decisions up to u-boot, > but... as an option... For now we always set "safe" values for RAM in DT so it could work even if not the entire memory is configured. Since there is no way to detect this from Linux on ARM64, we have no choice but hoping U-boot sets the right value... > > I'm pondering if we should do the same for the connectivity settings? A > properly configured u-boot already knows if it's an internal/external > PHY, Mbit vs Gbit etc. so in a similar way could enable/disable the > right nodes. > > We could have a single DTS for each of these board families which > has some reasonable defaults, then u-boot would enable/disable nodes > accordingly. Yes it's technically possible, but it puts a larger dependency on the bootloader. Having a lower RAM value is not idea but the system will work, having the wrong PHY setup simply doesn't work. Neil > > Kevin > > 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 E5CFFC433EF for ; Wed, 8 Dec 2021 08:20:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date: Message-ID:From:References:Cc:To:Subject:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Owner; bh=91cMMtiJjGX81I5PHS3xN6g0rfluL28kAE7hKWQ2y/k=; b=kwOkGic79s2drE1pYjuK6s1I1E ApOYTjB42UrFrmqz1ADpcOAGrc99iloCSOWfJ2tDAtKSzGjPweebcPkiyRnafprTukrxhQC2+szEt 3xWKWyDxm0gjhbmQBjuqvHCt/0m+laqU7pfo9tF20OZ4LP0N+yETIavG3EElb7wgLIcHng2lPdh/v WrD/IQJyw/wa1Ut4uqGuFj2HULHDfFs0UyIAAcw7IZCgrUrN5VMI/FhwZQYb9OFv/H4w9wTUJVe4G BmHht5Dhw0Q+yvyVtW5+FAcxpVRgQBzgZtDZxzrMTP+kUmY0vDJ6SoqqfCQrZ0u5zlZDMgmXqlJG8 CBb3r6fQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1musBv-00BgVu-M6; Wed, 08 Dec 2021 08:20:43 +0000 Received: from mail-wm1-x32e.google.com ([2a00:1450:4864:20::32e]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1musBt-00BgV0-4Z for linux-amlogic@lists.infradead.org; Wed, 08 Dec 2021 08:20:42 +0000 Received: by mail-wm1-x32e.google.com with SMTP id g191-20020a1c9dc8000000b0032fbf912885so1204865wme.4 for ; Wed, 08 Dec 2021 00:20:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=1w3QG5L2wJSdawJv13n1fbqmjL3sgSHFT+7XbyAvU6U=; b=55DNvAYxUXa+yKMvFNkcwxQcyuMG4hyrlqdl8GCYFqXE/nvB5hzQFKynb0amMmXyPj gvr6FYs5uEqtTr3S1cxwe8elBx06xxnm+aXZmnSmTpE4iBiqlMFjwG+Li/AZafgjjQ/J kfVWr21Ir4haj+rGGcA+A6kC8FsP9DhwqqdIrnTSjtTK4yLGw15m+Fd/QX/zYcNaeN60 jtM6G0eR3psmmQ/Vrui/nwb1ZCQ7eo7nG2CngnGrj5nFE7X5MYrE/QmSZM/j7QIf17OY st+lLoPx7tEWVC/AA0P3vn93dIiI37Cp8OTaqRFkScrNd9NRbxdAWoF5gSyjRXVXUDfE vffQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=1w3QG5L2wJSdawJv13n1fbqmjL3sgSHFT+7XbyAvU6U=; b=qxU7MDT4i3GKb055Llr/FZOaZFbwBjm4RUqiOWNqdwuxXkq+m4ZHON3i1P4vsMVFY3 lP7G5AxpwxKNqN0cvqs/mhhpqT70l5SQcVAIpWsFOVVnRTKoB2YbWID3lYgL3Vd8B/7l Tr2CFq/ydiVMqWRVgob3hyNbFNiQ8N9ieEC2535/E8zDuVKD28btkBUDt1NmV8aUEEOO S+LUO0/PcNsC+54QLtY7YV0+W1IM0bujPwDviDSVkZ2/CGkGPuZSUHU3d4WrnNk2B1n+ nC77OZVBCF8IKT07fKivE9RM/s0EL6yZfPYRtZJzK8+uu9RPvyNekZxU++dnTYF1lamq Wa3A== X-Gm-Message-State: AOAM530bbBkJSH2H7whi0CRoDxBoWkLxoZQ59LRupW61ddpj2ZUjEgcZ gYMfMtJVJNO/Fur7IFpevNrMgQ== X-Google-Smtp-Source: ABdhPJzG/TNg3Piyp5TseF8rLfJFvZTaZFXGKZz5otMT3tS+daO2oHy7ZCllGK9433G4TB+hyrdAQg== X-Received: by 2002:a7b:c24a:: with SMTP id b10mr14015235wmj.166.1638951639255; Wed, 08 Dec 2021 00:20:39 -0800 (PST) Received: from ?IPv6:2001:861:44c0:66c0:5245:80ea:cf46:35bb? ([2001:861:44c0:66c0:5245:80ea:cf46:35bb]) by smtp.gmail.com with ESMTPSA id i7sm2022410wro.58.2021.12.08.00.20.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Dec 2021 00:20:38 -0800 (PST) Subject: Re: [RFC PATCH 0/9] arm64: dts: meson: add support for aac2xx devices To: Kevin Hilman , Christian Hewitt , Rob Herring , Mark Rutland , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Benoit Masson References: <20211130060523.19161-1-christianshewitt@gmail.com> <7hilw14nhx.fsf@baylibre.com> From: Neil Armstrong Organization: Baylibre Message-ID: Date: Wed, 8 Dec 2021 09:20:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <7hilw14nhx.fsf@baylibre.com> Content-Language: en-US X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211208_002041_208078_4760A668 X-CRM114-Status: GOOD ( 22.48 ) X-BeenThere: linux-amlogic@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-amlogic" Errors-To: linux-amlogic-bounces+linux-amlogic=archiver.kernel.org@lists.infradead.org On 06/12/2021 19:06, Kevin Hilman wrote: > Christian Hewitt writes: > >> This series adds support for several popular Amlogic S905X3 (SM1) Android >> Set-Top Box devices. Like most Android box devices, they ship in variants >> with multiple RAM, eMMC, WiFi and BT configurations. RAM and eMMC are not >> something we need to consider to get a working boot, but we do need to get >> the correct connectivity spec. > > The reason we don't need to care about RAM differences is because u-boot > takes care of that, and updates the DT nodes accordingly. > > In general, I'm not a fan of leaving these decisions up to u-boot, > but... as an option... For now we always set "safe" values for RAM in DT so it could work even if not the entire memory is configured. Since there is no way to detect this from Linux on ARM64, we have no choice but hoping U-boot sets the right value... > > I'm pondering if we should do the same for the connectivity settings? A > properly configured u-boot already knows if it's an internal/external > PHY, Mbit vs Gbit etc. so in a similar way could enable/disable the > right nodes. > > We could have a single DTS for each of these board families which > has some reasonable defaults, then u-boot would enable/disable nodes > accordingly. Yes it's technically possible, but it puts a larger dependency on the bootloader. Having a lower RAM value is not idea but the system will work, having the wrong PHY setup simply doesn't work. Neil > > Kevin > > _______________________________________________ linux-amlogic mailing list linux-amlogic@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-amlogic 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 6F800C433F5 for ; Wed, 8 Dec 2021 08:22:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date: Message-ID:From:References:Cc:To:Subject:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Owner; bh=Cfny6uomRCMnbT7sjXCDNTh+zdZCVU051QoNmrjUuV8=; b=GTS1DrlJBQ9buKB+exhbvydd0U 196vyM1H1TFNKdy9GCNXfnPS6oeQAnf1pFs8pU9OmbLoOmxu+plWqioNMqz+CeyQ0wYqkCdn7yXX0 eVyh6HzeopGndUK7QCcND+n3He8pJEUL28X47XxLzzvx5C81dVdtD2/sv1SERHX6EF1K+gApZZphL Jx94jYT8I9Lz429/+eF7Gl5A4jOnlQobm8diZ8OGcfxsfYRTuLuiDDziRAvhVqNC0xq70I0lsIj7x Yv14Ql+bPgpyjur5NIeuxgUdhBveXTLTfvCWDq9qBuwuNPTEHT584ysYOzXHQxWyrGh2x7DMilpRt w85cdLqg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1musBx-00BgW1-AU; Wed, 08 Dec 2021 08:20:45 +0000 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1musBt-00BgUz-42 for linux-arm-kernel@lists.infradead.org; Wed, 08 Dec 2021 08:20:42 +0000 Received: by mail-wm1-x329.google.com with SMTP id y196so1168629wmc.3 for ; Wed, 08 Dec 2021 00:20:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=1w3QG5L2wJSdawJv13n1fbqmjL3sgSHFT+7XbyAvU6U=; b=55DNvAYxUXa+yKMvFNkcwxQcyuMG4hyrlqdl8GCYFqXE/nvB5hzQFKynb0amMmXyPj gvr6FYs5uEqtTr3S1cxwe8elBx06xxnm+aXZmnSmTpE4iBiqlMFjwG+Li/AZafgjjQ/J kfVWr21Ir4haj+rGGcA+A6kC8FsP9DhwqqdIrnTSjtTK4yLGw15m+Fd/QX/zYcNaeN60 jtM6G0eR3psmmQ/Vrui/nwb1ZCQ7eo7nG2CngnGrj5nFE7X5MYrE/QmSZM/j7QIf17OY st+lLoPx7tEWVC/AA0P3vn93dIiI37Cp8OTaqRFkScrNd9NRbxdAWoF5gSyjRXVXUDfE vffQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=1w3QG5L2wJSdawJv13n1fbqmjL3sgSHFT+7XbyAvU6U=; b=ISYoHiXg9VBTcysk49gDyXek6Rf0B/ae9y0FAogsF0X3pm1tSl/9eFCVW+BTan4zqf aVWDYNjX9i+e+xkkEG+IyynqkeeP0FnRpWzO5/kW2BhzJ07BwDGOv6krDXxPVoDTMnLe Tkg9LsUi9ImREQcglCV6Z889DGuwOWHdpjy1lK8xqY8Js7gPRguogM6/3OeWxHPMLd1T UWfHagwEAgq8Us10s8LqWX7Uet1xKKZp25DW8mo4xWMKD3n7jIMmRzkkT2Y1ldG8PEHd vnvNiL5bfUTR7nwa7OsAf6MkSKGx1NxA5yEGCwuQ56yVqBUDgtJXQym8bHR20edeGM6I y9pA== X-Gm-Message-State: AOAM530GMNA/qA60pikV9KIS1pbF/fcHVr5DgEyju+EPmhxplp4k16HK KlxaIsrgSHgbjvVJAjrPkVcOKg== X-Google-Smtp-Source: ABdhPJzG/TNg3Piyp5TseF8rLfJFvZTaZFXGKZz5otMT3tS+daO2oHy7ZCllGK9433G4TB+hyrdAQg== X-Received: by 2002:a7b:c24a:: with SMTP id b10mr14015235wmj.166.1638951639255; Wed, 08 Dec 2021 00:20:39 -0800 (PST) Received: from ?IPv6:2001:861:44c0:66c0:5245:80ea:cf46:35bb? ([2001:861:44c0:66c0:5245:80ea:cf46:35bb]) by smtp.gmail.com with ESMTPSA id i7sm2022410wro.58.2021.12.08.00.20.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Dec 2021 00:20:38 -0800 (PST) Subject: Re: [RFC PATCH 0/9] arm64: dts: meson: add support for aac2xx devices To: Kevin Hilman , Christian Hewitt , Rob Herring , Mark Rutland , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Benoit Masson References: <20211130060523.19161-1-christianshewitt@gmail.com> <7hilw14nhx.fsf@baylibre.com> From: Neil Armstrong Organization: Baylibre Message-ID: Date: Wed, 8 Dec 2021 09:20:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <7hilw14nhx.fsf@baylibre.com> Content-Language: en-US X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211208_002041_208419_8DD78989 X-CRM114-Status: GOOD ( 23.97 ) 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 06/12/2021 19:06, Kevin Hilman wrote: > Christian Hewitt writes: > >> This series adds support for several popular Amlogic S905X3 (SM1) Android >> Set-Top Box devices. Like most Android box devices, they ship in variants >> with multiple RAM, eMMC, WiFi and BT configurations. RAM and eMMC are not >> something we need to consider to get a working boot, but we do need to get >> the correct connectivity spec. > > The reason we don't need to care about RAM differences is because u-boot > takes care of that, and updates the DT nodes accordingly. > > In general, I'm not a fan of leaving these decisions up to u-boot, > but... as an option... For now we always set "safe" values for RAM in DT so it could work even if not the entire memory is configured. Since there is no way to detect this from Linux on ARM64, we have no choice but hoping U-boot sets the right value... > > I'm pondering if we should do the same for the connectivity settings? A > properly configured u-boot already knows if it's an internal/external > PHY, Mbit vs Gbit etc. so in a similar way could enable/disable the > right nodes. > > We could have a single DTS for each of these board families which > has some reasonable defaults, then u-boot would enable/disable nodes > accordingly. Yes it's technically possible, but it puts a larger dependency on the bootloader. Having a lower RAM value is not idea but the system will work, having the wrong PHY setup simply doesn't work. Neil > > Kevin > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel