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 E5A38C64EC7 for ; Sat, 25 Feb 2023 13:13:08 +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:From:References:Cc:To: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=NpnIGcYN3wvEEIH1VZnbWEbiM/WBV8qAzhlHVohAXvs=; b=sATPNWxyGbUVZS Vw/tI+GkFtjXaSAn3dcAL9nNVMt8rVAlb4kuUW4kanbRevbowYb6jixtaTamjgta2E/sxnEC3fTDH ir/5rNHSoxJfyh/vieoRNWp9WOeqlWFHL8t/+ZNEIbc8r8ZDW7uc0afJ9odbafOXMklMIPF+CW3ZV uEcrf2kHnZXHmBb6N4z5neeFmjA1ybxJ2ZcdNYJKiR38dArK+e1n06/T8ASnw3k7Vu7fqXJg0QeJX KtWF9KL/T6fqnQRFiTyTNJ/YA1OAnciUV+BGUzCnac8rJiz1YaE55zQUvmrGCTDjqvcbt4MHhsdpZ GJivS1AUX/Pva8EBZW/g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pVuLN-005l8D-UG; Sat, 25 Feb 2023 13:12:06 +0000 Received: from mail-wm1-x332.google.com ([2a00:1450:4864:20::332]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pVuLK-005l7K-A1 for linux-arm-kernel@lists.infradead.org; Sat, 25 Feb 2023 13:12:03 +0000 Received: by mail-wm1-x332.google.com with SMTP id c18so1486098wmr.3 for ; Sat, 25 Feb 2023 05:12:00 -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:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=venjkIokm8GSX2ge2Rc27dt76cxYVR85slS/SbYCDaI=; b=KfUc2TMjMgU8j1j5SmUZ57UkfL5HxpCSKgAhZP4qQizXeVmtzxOfOOVXIQqIFzVCov W1t32Qi2f2NnVvw3/KA9aGL4FFk3c+lqbm9pu4B/pkzM0fT1WndSEmFTyIgDzWyCcamB P7Cg6CnwRv2c7yzhNoFO9W8LCjaa0WJ8qvABY4/5J2kcsnkyQhOnnzHBAWQIyfRI8eOY z1izimCojPZ1dlYwiIHO78xzP+lishGZ0telNVWnRI7ViLb1MVdb0JgihnpGYtwAbl1F xLAocLciAwklAg8tXJxbCuN81IQHpukbq9IkHQ7LxEUhcHnGqnDz3WGKx4uQ5JbnDahQ dXTQ== 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:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=venjkIokm8GSX2ge2Rc27dt76cxYVR85slS/SbYCDaI=; b=kUgQSkRrcXFHZ/CZLHWDXGi0JeeMJkpxo7s7m9RLwMjSviUp/JmYIhsMQplA03FXaN yK5ajwGORn6Ge6tQukLCDnih9kbh2QR4SE+CmXSxbzvbP9a769L9l7u1Pog8QpuVqnuB KBb3pMRcfalovw8KSH2lAdUQATIME4M8pMPFEif3cGli5sJCNtdd+O1dylu0ZCE5RPuJ XC2OpV3gKEMuDVJe5/RXkOzTXqo7NkHwb53d6Ky/JEOJETExFzT6BD9kh6Io5t3TBVnJ KH8fI/Ukt+TUj6t4tV6cbKrxVHJPYSR4rCV9BxqTonnstFPXvI/iCAktcbbP1VrNDyyC uEqg== X-Gm-Message-State: AO0yUKUYDpZu4onjgheLCzZIrh6mon5CSzR9sFpzv0/eyuitrbPECcTP d+YhlWlkWJCgN6JYwAsdEKYUtSpU9sfc0cFC X-Google-Smtp-Source: AK7set8O2VSqgwAnq/imhIlGDJngF7y0agxJuG7tVFHHKetGgD5yTpJ/duKxSgrL/CZ9LsS2rTAzRA== X-Received: by 2002:a05:600c:1656:b0:3dc:46f6:e607 with SMTP id o22-20020a05600c165600b003dc46f6e607mr13468231wmn.3.1677330718912; Sat, 25 Feb 2023 05:11:58 -0800 (PST) Received: from [192.168.1.20] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id v7-20020a05600c470700b003eb3933ef10sm823506wmo.46.2023.02.25.05.11.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 25 Feb 2023 05:11:58 -0800 (PST) Message-ID: <23f7e0d9-32e5-654d-9b4d-84c91f833b2f@linaro.org> Date: Sat, 25 Feb 2023 14:11:55 +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 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> <9a25020c-de26-5c1d-f7ff-c2dbb38d3872@linaro.org> <473e0ac5-f12a-c66f-6696-8b7fe6e540f0@gmail.com> Content-Language: en-US From: Krzysztof Kozlowski In-Reply-To: <473e0ac5-f12a-c66f-6696-8b7fe6e540f0@gmail.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230225_051202_401357_EA8F2C53 X-CRM114-Status: GOOD ( 17.19 ) 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 25/02/2023 13:48, INAGAKI Hiroshi wrote: > Hi Krzysztof, > > thank you for the response. > > On 2023/02/24 21:53, Krzysztof Kozlowski wrote: >> 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/ > > Oh, got it. So marvell/armada-38x.yaml needs to be created from > armada-38x.txt like armada-37xx.yaml. I don't understand why we need three or more files... all or almost all platforms are having them in one file. So just merge them to one. > > Questions: > > - who should be assigned to "maintainers:" in new yaml? Maintainer of platform. > - should the old text file be deleted when new yaml is created? If you convert, then yes, but we did not talk about conversion but at least starting documenting the new ones. Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel