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 94E19C433FE for ; Mon, 6 Dec 2021 18:06:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346503AbhLFSJf (ORCPT ); Mon, 6 Dec 2021 13:09:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42808 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229880AbhLFSJd (ORCPT ); Mon, 6 Dec 2021 13:09:33 -0500 Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BEEAFC0613F8 for ; Mon, 6 Dec 2021 10:06:04 -0800 (PST) Received: by mail-wr1-x42f.google.com with SMTP id a9so24137898wrr.8 for ; Mon, 06 Dec 2021 10:06:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=9Eu38/3+9tGaMWfLccEWOU7ckpzNuZ1dJmEA2K5P3hE=; b=ksxUHhx7E++eESp3gUhlMdMaGTidNIZ352BtBhdadLYt7T5/NJK57OHZyxUZjAyGaP mCIstqO91Jc0+TZf7n2sSnOR1/qLlpXGg7MQcCOdJgU8mWeieClu/MgYD8XB33Jjx86M Xmsl0gsbKeFA7bwQ9zQXt34+COopKchDvJsJXl/3LnWCTyntVAUZkrT/N2mV6yLMER3S 4grd6yjDMd69uTF/3Pg8v+aokAPb4MZexwleNiJkZT6LZpC6ygAtPb4lRv9D1T3ayecX 51/inhYFnSq08l0J4cvpcyMUaRD0AlBdkGKiePhv1JNgMC8/W4yOIar/8o4pTCyhCZJ9 WJ8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=9Eu38/3+9tGaMWfLccEWOU7ckpzNuZ1dJmEA2K5P3hE=; b=jEA+Kfad6YHSEv1wGOdV6+awsn26aB1ZQCgyszIPIQBkqQx/11mfM4uIYuZbml/KID 7jXDEVwqbKgWdmggX8ilpucNbut1y7ELFWwKjUsXTxxmZ5jRz2ZuIqpnczlkr6+bmQop WgVwlKhvQGBkmtS2IL1Xkt4hiiH+wSvcFXFYGD9YcPBZgewPIzJUcbeJZQegbPEx+OLM PNuIbijrWbfjifKpWLh5ijc1BI9N32n6w/wphAQhXOTEpuHJ2ot2SdmElWmv46Kd020E OSA+VKF4j3mfL9xeYX7WBm6ekkkLKsE+GqXQwlVC1gOd/uH7tiU7N+Eb+YAgMdUVMDpx h1Jg== X-Gm-Message-State: AOAM531Xr2cc8DKJjDTIk6Swu59kv++hc99xxhJ21YCYB9v2NXrNTKgP zMQ2WkX2Of2k0IZf8xcP4jtmIA== X-Google-Smtp-Source: ABdhPJyeP9mmGnfPC2VzFGb6kW3kaXKtwf/c9ade3X5hh72uFYdGSbs1CnzHMgnUQ5bQquvSyJDstg== X-Received: by 2002:adf:f001:: with SMTP id j1mr44911077wro.351.1638813963287; Mon, 06 Dec 2021 10:06:03 -0800 (PST) Received: from localhost (laubervilliers-658-1-213-31.w90-63.abo.wanadoo.fr. [90.63.244.31]) by smtp.gmail.com with ESMTPSA id 9sm15728052wry.0.2021.12.06.10.06.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Dec 2021 10:06:02 -0800 (PST) From: Kevin Hilman To: Christian Hewitt , Rob Herring , Mark Rutland , Neil Armstrong , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Christian Hewitt , Benoit Masson Subject: Re: [RFC PATCH 0/9] arm64: dts: meson: add support for aac2xx devices In-Reply-To: <20211130060523.19161-1-christianshewitt@gmail.com> References: <20211130060523.19161-1-christianshewitt@gmail.com> Date: Mon, 06 Dec 2021 19:06:02 +0100 Message-ID: <7hilw14nhx.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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... 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. 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 3FE59C433F5 for ; Mon, 6 Dec 2021 18:06:37 +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:MIME-Version:Message-ID:Date:References :In-Reply-To:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=yIkg+po1giaDhBV+gQOcCv3y8UKn4eeRLnr+BuoADe0=; b=qY/Mbfn7QEEgES uovRRy11LiMYwCW0TkzLG128+Nou/2gMnjy0VN83ttdweoJQSNazKcGASXnBM5m2iOZm0VtMA+yhv rbxzAsehw12f7o7/BqAL6xx4bzIu+M/7uU2VRos86vnYBO7TkM4Pds2460m2WyZduZC4nec2ATZ22 A2Fa18NJJFz1iWfqi2sYrMATg4TPKvBPuY8J/8JeZkZytTT+E+bKQdnLInIYweOYtRcozS1vJk4+b KYlmdHX253SvKbFHK8FoHhvDNUfTj4MtGTwOb1mRZpf5/JlnaxhPv2kR9+WeeesgmNA6dqr8oW81x CZl/rDd0DPooh6KVxFww==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1muINj-005DPu-Ud; Mon, 06 Dec 2021 18:06:32 +0000 Received: from mail-wr1-x431.google.com ([2a00:1450:4864:20::431]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1muINJ-005DEU-Ok for linux-amlogic@lists.infradead.org; Mon, 06 Dec 2021 18:06:10 +0000 Received: by mail-wr1-x431.google.com with SMTP id u17so16870216wrt.3 for ; Mon, 06 Dec 2021 10:06:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=9Eu38/3+9tGaMWfLccEWOU7ckpzNuZ1dJmEA2K5P3hE=; b=ksxUHhx7E++eESp3gUhlMdMaGTidNIZ352BtBhdadLYt7T5/NJK57OHZyxUZjAyGaP mCIstqO91Jc0+TZf7n2sSnOR1/qLlpXGg7MQcCOdJgU8mWeieClu/MgYD8XB33Jjx86M Xmsl0gsbKeFA7bwQ9zQXt34+COopKchDvJsJXl/3LnWCTyntVAUZkrT/N2mV6yLMER3S 4grd6yjDMd69uTF/3Pg8v+aokAPb4MZexwleNiJkZT6LZpC6ygAtPb4lRv9D1T3ayecX 51/inhYFnSq08l0J4cvpcyMUaRD0AlBdkGKiePhv1JNgMC8/W4yOIar/8o4pTCyhCZJ9 WJ8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=9Eu38/3+9tGaMWfLccEWOU7ckpzNuZ1dJmEA2K5P3hE=; b=loUfa0l7x1yyS7+1dlCSrwHIuuPzj5UasKMWlZmU03kjEUGCOzrPNefwMJ5aN9vCEw jNMEOG3brzpnu82p1l9pOZPH30q1hF7bsa7oBKmSJRZtIRfd8zUuhDJ0RPvarqFQ+g0r 1iF2JxcF2uFa//dMcUk8FoPXPZQhQ/5S28Mkxff/qYk2PXRWYJ55/aKaiXMCtoA4rklk riyKPmqJ2Mw5ps6rAcVxtSRkNV4JrlxtgGuK3hw7L+R+Ku9tgLTa7hPV1YsNgrv0Z900 lAWkrHMbyGDfggjCz4io+ddSGxf5WJpusUjLQwQ/R79Yr6dxPJlp7/Fxunt/HgFEPOXe 9amQ== X-Gm-Message-State: AOAM533DMJQIFhZzzUdMkTer6N9ztsVIK7HHqPFjoka2aFs4ulI6ULVx cZlUP4lz/S3T+2KEJ3fmR9hrDw== X-Google-Smtp-Source: ABdhPJyeP9mmGnfPC2VzFGb6kW3kaXKtwf/c9ade3X5hh72uFYdGSbs1CnzHMgnUQ5bQquvSyJDstg== X-Received: by 2002:adf:f001:: with SMTP id j1mr44911077wro.351.1638813963287; Mon, 06 Dec 2021 10:06:03 -0800 (PST) Received: from localhost (laubervilliers-658-1-213-31.w90-63.abo.wanadoo.fr. [90.63.244.31]) by smtp.gmail.com with ESMTPSA id 9sm15728052wry.0.2021.12.06.10.06.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Dec 2021 10:06:02 -0800 (PST) From: Kevin Hilman To: Christian Hewitt , Rob Herring , Mark Rutland , Neil Armstrong , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Christian Hewitt , Benoit Masson Subject: Re: [RFC PATCH 0/9] arm64: dts: meson: add support for aac2xx devices In-Reply-To: <20211130060523.19161-1-christianshewitt@gmail.com> References: <20211130060523.19161-1-christianshewitt@gmail.com> Date: Mon, 06 Dec 2021 19:06:02 +0100 Message-ID: <7hilw14nhx.fsf@baylibre.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211206_100605_879410_C3977911 X-CRM114-Status: GOOD ( 11.28 ) 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 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... 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. 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 0A91EC433F5 for ; Mon, 6 Dec 2021 18:08:30 +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:MIME-Version:Message-ID:Date:References :In-Reply-To:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=ZC0Xwmucw1hLgv7PzFfUKToQ8HnRjM8J7wGPLykUHAY=; b=rc9RO6lVmSflLF pn55sQ7OmcYqqTnysWV/Bs1mEGIQzpdE+/Dr70dzD7aM9mTZuBS5O0bFoggUGNsZ1fQMLzTqOb0HN iF5IOnGrvBh6hB5LMiSoa1rFxOIjwoVCFK1s3K9goaGQNSJDH8+J8Z9LLoArr+JB9uinKhsQGHDtQ FvcQMOPeyGe7WAXa69L1CWxdKs07F5T7pbFgkJ4lDA2SuuExkGbLYRE65OuBSRnRQTTX/RG/I7DdF RUHOTkbCramKZcoHWg9icQE256aFqNA/SPFOtuUeTbjoXqy9dJ6/atcFOMUgVniUGDaf4AKXTuz+Y 2YfJNeJCqtKco6TJwj0w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1muINs-005DQa-QE; Mon, 06 Dec 2021 18:06:42 +0000 Received: from mail-wr1-x435.google.com ([2a00:1450:4864:20::435]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1muINJ-005DEP-Ox for linux-arm-kernel@lists.infradead.org; Mon, 06 Dec 2021 18:06:10 +0000 Received: by mail-wr1-x435.google.com with SMTP id d24so24339818wra.0 for ; Mon, 06 Dec 2021 10:06:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=9Eu38/3+9tGaMWfLccEWOU7ckpzNuZ1dJmEA2K5P3hE=; b=ksxUHhx7E++eESp3gUhlMdMaGTidNIZ352BtBhdadLYt7T5/NJK57OHZyxUZjAyGaP mCIstqO91Jc0+TZf7n2sSnOR1/qLlpXGg7MQcCOdJgU8mWeieClu/MgYD8XB33Jjx86M Xmsl0gsbKeFA7bwQ9zQXt34+COopKchDvJsJXl/3LnWCTyntVAUZkrT/N2mV6yLMER3S 4grd6yjDMd69uTF/3Pg8v+aokAPb4MZexwleNiJkZT6LZpC6ygAtPb4lRv9D1T3ayecX 51/inhYFnSq08l0J4cvpcyMUaRD0AlBdkGKiePhv1JNgMC8/W4yOIar/8o4pTCyhCZJ9 WJ8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=9Eu38/3+9tGaMWfLccEWOU7ckpzNuZ1dJmEA2K5P3hE=; b=7AA/CKPJ9YydbrUj7grK2RDLNjF9VDzYYPdP5Ztj9VnrPE9rvpHOL4BiDr0F+HXZYl 7NhOEOECC3E62UpllX3fbpo14xcwt4xESuop2WQqiEDg7+j2J/nklAAs6y6S32v8nooI 2WNHqKCzVwEwoULCHCgsHYcrmaprU2+TvG05E/6EaHhGF9cHI2WxavXrceXU8MSFQ7jj jMfrztImKuQ490/aDN9iVtnVa9pYknsc4Bot6XbqCxW7r6OjI7MW7BtFYDeAmASmw6HZ RhoSL2FGHlZWeTudNrO5GUMrMHSaiG+j7v19WIeJdgXAEWd7j3ymQ6NEsc8s/bU6axG1 UtuQ== X-Gm-Message-State: AOAM530p3QX9jxhqEbLNz0Xd3j1nPHPlZp4ptRnOKGS+cjs2hYO0SecV 7tMmAUY4BKC+hFPqQjlxQQVnsA== X-Google-Smtp-Source: ABdhPJyeP9mmGnfPC2VzFGb6kW3kaXKtwf/c9ade3X5hh72uFYdGSbs1CnzHMgnUQ5bQquvSyJDstg== X-Received: by 2002:adf:f001:: with SMTP id j1mr44911077wro.351.1638813963287; Mon, 06 Dec 2021 10:06:03 -0800 (PST) Received: from localhost (laubervilliers-658-1-213-31.w90-63.abo.wanadoo.fr. [90.63.244.31]) by smtp.gmail.com with ESMTPSA id 9sm15728052wry.0.2021.12.06.10.06.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Dec 2021 10:06:02 -0800 (PST) From: Kevin Hilman To: Christian Hewitt , Rob Herring , Mark Rutland , Neil Armstrong , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Christian Hewitt , Benoit Masson Subject: Re: [RFC PATCH 0/9] arm64: dts: meson: add support for aac2xx devices In-Reply-To: <20211130060523.19161-1-christianshewitt@gmail.com> References: <20211130060523.19161-1-christianshewitt@gmail.com> Date: Mon, 06 Dec 2021 19:06:02 +0100 Message-ID: <7hilw14nhx.fsf@baylibre.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211206_100605_878415_8FF4FB44 X-CRM114-Status: GOOD ( 12.77 ) 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 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... 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. Kevin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel