Received: by 2002:a05:7208:9594:b0:7e:5202:c8b4 with SMTP id gs20csp1197362rbb; Mon, 26 Feb 2024 01:38:30 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCW31jyktQ3tOEQDJw7w86oW0VROL796s0ikqSA2cVjG3Lq5b25bCLK1KmlZWGz07Qid75HfVlXTwnknEW/lkbXu5LiUkZM/EbB7P1swyw== X-Google-Smtp-Source: AGHT+IEEyTt6f/B4pYnxEFexbu6BFXq9hNFvouZd+QzmDO4IQSJ2wcjcImnzkskHS/B327EG+rm9 X-Received: by 2002:a05:6a00:1d10:b0:6e4:74d9:6f0f with SMTP id a16-20020a056a001d1000b006e474d96f0fmr8333532pfx.0.1708940309970; Mon, 26 Feb 2024 01:38:29 -0800 (PST) Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id u9-20020a634549000000b005d8bf0a91besi3417159pgk.276.2024.02.26.01.38.29 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 26 Feb 2024 01:38:29 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-80993-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@collabora.com header.s=mail header.b=aA8uGwp8; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-80993-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-80993-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=QUARANTINE) header.from=collabora.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 01A3F2866D8 for ; Mon, 26 Feb 2024 09:38:13 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id C426D6A34B; Mon, 26 Feb 2024 08:58:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b="aA8uGwp8" Received: from madrid.collaboradmins.com (madrid.collaboradmins.com [46.235.227.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7A2E36A01D; Mon, 26 Feb 2024 08:58:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=46.235.227.194 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708937936; cv=none; b=ZuDIehA4W97Kl/RxBM0vH5YkM/NxMd9TdGha4bOX9lwxEMqg4mGYK+E65cz6jL+sjmSQnWB254t5mp2ZMNxH9qRMiTihzK/G21FNIPyknGcEmBCJhlrKOtQeJiWrIq5j5E+BkbahXZVhmUtfKnZi1wEXVSRqPfZOlewOz8IXZZA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708937936; c=relaxed/simple; bh=zA+oV5eE+DmShaJT1CXXXguSc4DEhYwAp7s4CFKkF0o=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=OhOE0hFE+6BFSAqAzn6ZGSBtgMnPug5C5tmWVevGjRfJBIMc6T5j5iJ2iwCb0Cq8isCcFrASPGs1gAxvidFSGFhUtVhWyblynKfx/vngPilHG6mKLaXkQywjHxqmJCiuKG+QHmWbAJj7KyL3SvvsbFcC4ajSpneyMoV3oAYtPqk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=collabora.com; spf=pass smtp.mailfrom=collabora.com; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b=aA8uGwp8; arc=none smtp.client-ip=46.235.227.194 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=collabora.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=collabora.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1708937932; bh=zA+oV5eE+DmShaJT1CXXXguSc4DEhYwAp7s4CFKkF0o=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=aA8uGwp869N8HPs53Dbrhv5TAOQyPWeletOZpIgGJej5mp2Z/Rac/vS0W3UADwGUY xM2sRbgvAqkOQATrLpIY3jmEdc7/lpMXhzBojYi18xxS/O1KrxA5EcXipyVs0iMXA/ 4j5reS+ZPazRQL3Ae/mCUGNz/DWkCGQSJdxaypTUNL0wTMXCiNhpOoZpLdCbYB8b6N EEPh0CoSBf5LX52E5torJD9FdTfPwZaqTpxP9yZeLXeG2GYevQfku14TcJb4mj66pi w9dB4CWHMGlPRXh30bOgI8HNrI3gf/MCugUZ2NSpPoaY/asafk2JC+DYs5aV8/ZjX/ cL3vrJRP4DsbQ== Received: from [100.113.186.2] (cola.collaboradmins.com [195.201.22.229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kholk11) by madrid.collaboradmins.com (Postfix) with ESMTPSA id 7BBF6378207B; Mon, 26 Feb 2024 08:58:51 +0000 (UTC) Message-ID: <9c114a61-ad19-4852-96c8-dbcbe8d8e38c@collabora.com> Date: Mon, 26 Feb 2024 09:58:50 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH V2 4/4] arm64: dts: mediatek: Add Cudy WR3000 V1 Content-Language: en-US To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Matthias Brugger , Rob Herring , Krzysztof Kozlowski , Conor Dooley Cc: Chen-Yu Tsai , Hsin-Yi Wang , =?UTF-8?Q?N=C3=ADcolas_F_=2E_R_=2E_A_=2E_Prado?= , Heiko Stuebner , Jernej Skrabec , Chris Morgan , Linus Walleij , Sean Wang , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= References: <20240223101709.30072-1-zajec5@gmail.com> <20240223101709.30072-5-zajec5@gmail.com> From: AngeloGioacchino Del Regno In-Reply-To: <20240223101709.30072-5-zajec5@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Il 23/02/24 11:17, Rafał Miłecki ha scritto: > From: Rafał Miłecki > > Cudy WR3000 V1 is an MT7981B (AKA Filogic 820) based wireless router. It > has 256 MiB of RAM, some LEDs & buttons and (not described yet) 4 > Ethernet ports. > > There is one slightly uncommon LED with a label of globe icon described > in the Quick Installation Guide as having 2 meanings: > 1. "Not connected to the Internet" > 2. "Connected to the Internet" > > Vendor designed it to light up when some Internet-accessible IP can be > reached. This change will be follow by an attempt to define some > predefined FUNCTION for it. Can we please try to add that predefined function before adding this devicetree which would anyway be modified again to use that new definition? That just makes more sense... ..if you can't get the new definition picked, I will take this one as is, but please try that first. Cheers, Angelo