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 A30E2C433EF for ; Fri, 17 Dec 2021 09:00:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233966AbhLQJAN (ORCPT ); Fri, 17 Dec 2021 04:00:13 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50584 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233949AbhLQJAM (ORCPT ); Fri, 17 Dec 2021 04:00:12 -0500 Received: from mail-ua1-x92b.google.com (mail-ua1-x92b.google.com [IPv6:2607:f8b0:4864:20::92b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 663E3C06173E for ; Fri, 17 Dec 2021 01:00:12 -0800 (PST) Received: by mail-ua1-x92b.google.com with SMTP id w23so3082089uao.5 for ; Fri, 17 Dec 2021 01:00:12 -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=1IH63Q90oG2/sG9LVJYEHCd1u9C2HmHeMsRBX0qtkUo=; b=qIE8qNdqXPTUkGC9i0YDDZP2+Z4Mb1MUWzSefMskqX5QKqkuhfmvD+G2br+RJjGAkb pwQV/bFp+oXMsVJz7aJ2VZZKZc56eqRznRccK/sPEaCf3N7vtXruXVAfTjRM9T6KS93f ArrgpUzKYZNiH+O8EQTXEsW6LyZUpPZXPsZCA= 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=1IH63Q90oG2/sG9LVJYEHCd1u9C2HmHeMsRBX0qtkUo=; b=B2lvhQoDRfIC4UKuWLVs5DPgebCFwfgCHfGYY8CSfdJOmqTbRUL4kul86RVJ9aNE3n amUTlOZtj/bTb1uGhGN9K4TQ2U6h5eN5VIPHNo5bZTmXgT0wwIdOdnuXOAcfrdY1/A9Y 923QzinKM7kIR/zBdqwaeIIYj4BPiXThwx6grr1mG39/QCFRaSjZUAlY2uB7hRYJaD7g kpagqejvzxlCc5tiTD4DgdBUzOFzTyP8Lxkq06qqcOCn+1fcIhCXbgOzLl4t1sHZXkAt 3lWV8D7W7WjocWXS0odOuBA1DVavR1D/pUXzyvpDM/lPx2B1hSqhDKA8qCDOBd5T7PmJ BB9w== X-Gm-Message-State: AOAM531QQVbUMzzWAEliY+P/ZqaL/WFpapG63mDFBr9vJ7k6RTz/ZDxt HWhTU2z9SK5qauHyMFLY9wUD3ADJj+PMG76YMDivjg== X-Google-Smtp-Source: ABdhPJzBtMbh27J6qJpt+5sIKjlVPbdSyfevk8+JF4+f8w0xH2iu5rDghZD+yfHmIAyZww+PpPzT4a+7O3u35rmyL2U= X-Received: by 2002:a67:17c6:: with SMTP id 189mr629048vsx.71.1639731611453; Fri, 17 Dec 2021 01:00:11 -0800 (PST) MIME-Version: 1.0 References: <20211212181906.94062-1-romain.perier@gmail.com> <20211212181906.94062-3-romain.perier@gmail.com> In-Reply-To: From: Daniel Palmer Date: Fri, 17 Dec 2021 18:00:00 +0900 Message-ID: Subject: Re: [PATCH v2 2/6] clocksource: msc313e: Add support for ssd20xd-based platforms To: Romain Perier Cc: Daniel Lezcano , Thomas Gleixner , Rob Herring , Russell King , 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 Fri, 17 Dec 2021 at 03:18, Romain Perier wrote: > > Hi Daniel, > > What do you think about the following description ? : " > clocksource: msc313e: Add support for ssd20xd-based platforms > > > Signed-off-by: Romain Perier I looked at the disassembly of the bootrom again and it doesn't look like it's set there. I think it's the hardware default for the register. I'm thinking something like this: On SSD20X family SoCs the timers are connected to a 432MHz clock instead of 12MHz that all the previous chips used. There is no way to reduce or divide these clocks in the clktree yet as we don't know exactly where the 432MHz clock comes from but it's enabled at boot. The SSD20X timers have an input clock divider within the timer itself to configure the frequency. timer0 is preconfigured at power up to run at 12MHz so it is backwards compatible and doesn't need special handling right now. timer1 and timer2 run at 432Mhz at power up so are not backward compatible. This commit adds support for the input clock divider register and sets timer1 and timer2 to run at 48Mhz for clockevents. Cheers, Daniel