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 3551BC61DA4 for ; Fri, 24 Feb 2023 12:53:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229611AbjBXMxh (ORCPT ); Fri, 24 Feb 2023 07:53:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51714 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230092AbjBXMxg (ORCPT ); Fri, 24 Feb 2023 07:53:36 -0500 Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5215130B36 for ; Fri, 24 Feb 2023 04:53:23 -0800 (PST) Received: by mail-wm1-x332.google.com with SMTP id ay29-20020a05600c1e1d00b003e9f4c2b623so2062731wmb.3 for ; Fri, 24 Feb 2023 04:53:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=B43T0AEPZJigOIS/UyBFbfsmEoemf/SiYcHZlZbArDU=; b=OGkN0CXJsVpWhKLUzO+2J2EP6C2ZwB2OfxpxnFiy9L1Ff+oeVtGaepYwATvJ1ZZ2pK hufBlMrsd5ufeluzrEuT2G6PrqLLHAaEj7ri3YUxeIxkHrE4IoovPC7ZgmmfsffFQqsU l8WMxxt1p91VeqyXKQpa+1NBGX/TvqdlWA1ebvxb9jJqb6nd7OETN5acxdOZrwT3LeJk AjMddVKub+kRR/yfFld6Vgb0sXEcu2Ij3T+7YWPVi+pE0jTucksi8gBObYgLYBoMHyP1 kcctMIK+wi9WUWr86QW7tJUK09EBVwTMFmx2p4HG9FEJPMBfQ7KrVOifpmLjKTqhTveX stXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=B43T0AEPZJigOIS/UyBFbfsmEoemf/SiYcHZlZbArDU=; b=DROSLqU4YFOGO9iYFva+pr0H6cToqJMx6xwnV5EkbP9WkvUpQcmRErEx3sqr+lgIxw chF3RtJ0BRt+CUyLZr5KZrbobKl8J2oh64cR5U87S3lUe8JZi/acPAzeabXPfyqwQsK8 b8A7ejXlF40TOtk4kojW2jXKGm3H7L+qXbU/RNfq83rNJRnY16/IZc0NnfzsrjgGsPP/ MMpskVC4nAmFDNU9L2u5n1e6LbPZAbD/tykKsOeabXX+t5RniZtgRSe4/Cbk8mUr0wQi 6BlyV4Qp076SfrACIpLFmUHTTM0bYu9YugeO8+e7iDjHCgqhIPMnMfHUEzt43svZmJFJ T5nQ== X-Gm-Message-State: AO0yUKW0VY1ktiEqkJHKmIWVP+k9WwFmRPYKTkJ7JVB5cg9R8qpIBOQC 5To2E1Hepw0VG+9kT703Apbkzg== X-Google-Smtp-Source: AK7set+9lbd6dHt3hcDH3Rll7jbmvT9hwcj+WcM08mZeJj4pNOSU1eN9J5AAw4Qd2Tb4Iivb4brDXw== X-Received: by 2002:a05:600c:348f:b0:3ea:f132:63d8 with SMTP id a15-20020a05600c348f00b003eaf13263d8mr2323258wmq.5.1677243201812; Fri, 24 Feb 2023 04:53:21 -0800 (PST) Received: from [192.168.1.20] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id f5-20020a1c6a05000000b003dfe5190376sm2713538wmc.35.2023.02.24.04.53.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Feb 2023 04:53:21 -0800 (PST) Message-ID: <9a25020c-de26-5c1d-f7ff-c2dbb38d3872@linaro.org> Date: Fri, 24 Feb 2023 13:53:19 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH 2/2] ARM: dts: mvebu: add device tree for IIJ SA-W2 appliance Content-Language: en-US To: INAGAKI Hiroshi , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: andrew@lunn.ch, gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com, arnd@arndb.de, olof@lixom.net, soc@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org References: <20230223132502.2045-1-musashino.open@gmail.com> <20230223132502.2045-2-musashino.open@gmail.com> <76395d89-1c56-12b2-b6f7-e77603019b70@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 24/02/2023 13:28, INAGAKI Hiroshi wrote: >>> + >>> +/ { >>> + model = "IIJ SA-W2"; >>> + compatible = "iij,sa-w2", "marvell,armada380"; >> It would be nice to start documenting the board compatibles, at least >> for new boards. > > So...how do I do that? Start with something like this for Marvell: https://lore.kernel.org/all/20230222203847.2664903-2-colin.foster@in-advantage.com/ But maybe someone already started it for Marvell? Marvell SoC maintainers might help here to coordinate to avoid duplicated work. Best regards, Krzysztof