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 71697C433F5 for ; Sun, 12 Dec 2021 16:44:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231701AbhLLQoi (ORCPT ); Sun, 12 Dec 2021 11:44:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43102 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231694AbhLLQoh (ORCPT ); Sun, 12 Dec 2021 11:44:37 -0500 Received: from mail-vk1-xa35.google.com (mail-vk1-xa35.google.com [IPv6:2607:f8b0:4864:20::a35]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E8F3CC061751 for ; Sun, 12 Dec 2021 08:44:36 -0800 (PST) Received: by mail-vk1-xa35.google.com with SMTP id q21so9027328vkn.2 for ; Sun, 12 Dec 2021 08:44:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=0x0f.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4Iup0PuQre5u2Fob/RPt24yhd3mS85xJKv7O7p908ig=; b=F2V1Iuxnw9sXZfv56vR+qR+HCrc1/OxCJlGpzFbiru0wzuPfyfrIEIOon3bymnAoag j2F/IT3+KnzDb3lApTtZb3+torJDqkF1EP7sKKH0moLvV9PG2bvbOPQiOen+WYHHc+sU 3e+GhLSHRGzkOM3EHNPHCeJQyXP5sRmNmhKUE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4Iup0PuQre5u2Fob/RPt24yhd3mS85xJKv7O7p908ig=; b=OIXdfK9GCz91gHUexKGxcLq0vJPQ2RG0xWDS73GD01TyE0c0JSM4jT+LnLcFNSFxLw A4UYavgzcUjh+bZ0dyBouhT1IFZMzoq3oUHM4BTVQ1QLVMlKuhUsiIiA808oJbPZlk72 p3pHDBoRJ8lR18MoHMrQT/W3tZ6w5nH7MYxV9kZqy9Ngm8HY6mfU8blCrmulLSwjwibU 7E/3O76U02Gbd8/r+GPwxGJwMS0z4wuoZn2EGY1l6+r4scy8M7xhy4VdjJgnXYkGDy0d r2cWrKrf2575cvD8teFhiLOF6iSleX0EbaaqlxV3HW4cptbbRiihrOKqCfGsCmB2BYsR Ifgw== X-Gm-Message-State: AOAM531j0qCcqpCIYeP1HMVHh7BiNTJd2vojByoNZGB5cd4/3kbTnsYJ iP6EJpG3CkMC3xgokzpP3pjszOZxS33L9d3UiJx08Q== X-Google-Smtp-Source: ABdhPJwEJeOqr6oQvcFJg4KKaYC67h13cUgL588VnkbnkRUdVDD8DYVhG8iE/HgJufzkIQypRs6woELUDisWGMdurjo= X-Received: by 2002:a05:6122:1354:: with SMTP id f20mr28815931vkp.12.1639327475901; Sun, 12 Dec 2021 08:44:35 -0800 (PST) MIME-Version: 1.0 References: <20211126202144.72936-1-romain.perier@gmail.com> <20211126202144.72936-7-romain.perier@gmail.com> In-Reply-To: From: Daniel Palmer Date: Mon, 13 Dec 2021 01:44:25 +0900 Message-ID: Subject: Re: [PATCH 5/5] ARM: dts: mstar: Switch to compatible "mstar,ssd20xd-timer" on ssd20xd To: Romain Perier Cc: Daniel Lezcano , Thomas Gleixner , Rob Herring , DTML , linux-arm-kernel , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Romain, On Mon, 13 Dec 2021 at 01:10, Romain Perier wrote: >> I just noticed this during testing. I think we should put this in >> mstar-infinity2m.dts. All of the infinity2m chips use the same die >> from what I can tell so if the ssd201/ssd202d needs this then anything >> else that includes mstar-infinity2m.dtsi will too. > > > Mhhh, makes sense. > Do we keep the compatible "sstar,ssd20xd-timer" in this case ? > Because this is true for either the SSR621D or the SSD201 or the SSD202D, > so... what about "sstar,ssxd-timer", or something like this ? I think for anything infinity2m specific we use "sstar,ssd20xd-timer" as the SSD201 and SSD202D are the first chips we found this in. The SSR621D might get some specific compatibles for things that only it has broken out like the SATA. Cheers, Daniel