Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp87743pxb; Fri, 29 Oct 2021 06:18:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx4izp2ZSuOsrHabm72uK3Q/Kfw37wYHGG+xPh3zXo3Xhb1pBMN3IK9yljA1t8FObF/77E3 X-Received: by 2002:a50:d80d:: with SMTP id o13mr14810240edj.204.1635513499915; Fri, 29 Oct 2021 06:18:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635513499; cv=none; d=google.com; s=arc-20160816; b=ULgPet7HRgMlUz+meVizzpCpl9xlrZoY1VOkThCH5HlQGskBCuj2n8uCYRC5fCa8Px raq2zQOA0WlqpeicOWxhGRc0nHDpaYUGOSKL2ZM8VQhza9Y5WB59Cfqo+ihZsEJL23bu CRlOjKkflQOBzoGdG0fNMy/CY2zA0KiZxa6zfK/qfo/+/4v1laaJbeeN+kVHunkE1be5 SZ/P+ZB/2mkyFkFouzdynZwC9HeSkeOR6cXssIlX/o9FSuFvVBTn8eJXDiMyumxLFmsk aVh/DXZg7fZ1F5JPTpzCVrAJNLqc7Y+H14YsURInhtRsVZ7V3kTdWo1PelIOs19R5P3Z 009g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=g+Jn0Zb4XSWTtnsH7XrcWpFd+2PsMM1WYmSDBWFjSHk=; b=r1Ti3mUtuhTxsf6zYCGj4L8w2JbJrO2r3rgQIk61IGlVpQgZHWE0Al6qSJbiCPAXYM jibNEhRyIPnTMoEWkVzYFrUV7uO9fqoU/kyBduuQ1Ik3Djq5rISigvWeraPq7ysbJrJe SBvvm75EUkn0AwjwkseWUL5wdMfK0ooeripkex0h6gb3mqO9wvYFEEzkFMG94MNl2qqC favEqoh3qKuvVqXi5qBdQnEF3ZmqA4Z9vbo6uMiObHu33ysMGTaH4BsX1DNR5SyXjRKt xqzox1rS7RdFJqfB5ITfdeDI8VYqYaHbE0yIM/yHFZi5VOJfKJjgcZts23XjJM1C6QyP 0dAA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="b9E/lRCv"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 5si7842143eji.566.2021.10.29.06.17.30; Fri, 29 Oct 2021 06:18:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="b9E/lRCv"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231599AbhJ2NSG (ORCPT + 99 others); Fri, 29 Oct 2021 09:18:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56732 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230213AbhJ2NSF (ORCPT ); Fri, 29 Oct 2021 09:18:05 -0400 Received: from mail-ua1-x92e.google.com (mail-ua1-x92e.google.com [IPv6:2607:f8b0:4864:20::92e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E3A07C061714 for ; Fri, 29 Oct 2021 06:15:36 -0700 (PDT) Received: by mail-ua1-x92e.google.com with SMTP id x3so17972392uar.13 for ; Fri, 29 Oct 2021 06:15:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=g+Jn0Zb4XSWTtnsH7XrcWpFd+2PsMM1WYmSDBWFjSHk=; b=b9E/lRCvOBOQR1o3F7Fxr20iMUVtSJUqUxSOg6lRP3YmV//6oeIM13YCK+fke+bnix g/gii88LV1Ol2o5XiRcBIF1zdz7LNiNUU3EERvs0w4Fw75e8TzfH38xw3lE72l3P+OwA rh8RmIzbnE3CrIp8PKTRJ+pAfHgm6aMlFZwZ+EBoy4c877CzsdbrvddazYth9n8HKb4K 3lU5bFpLNwATuM534+CbMr5KoLDzQtq4rikxLyka3CLMScSCnkYR+xcl/2oCN55jH8Eo InKF8BKDFNs8H53aXzh5N7Kd7gHP5DDx7fv9lZ9a1SnvETzyYPbpzU3dboZYmSWxXA15 Ubnw== 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=g+Jn0Zb4XSWTtnsH7XrcWpFd+2PsMM1WYmSDBWFjSHk=; b=xT6gXn+wKqSjEL9yZW2ZMuLqJNNgy8OX3EireQc9/4cWWq2SdfKVdFcLyil5uix7qW jSPZSlgs3DXO2cpTciYfb09JzqHHPE8mPggYaBVoH5TMmFAKtckkS8cZwFIGn8bp57io qLOOJggBVZjs9zS5ZF5+pTryAGQ9qd6+30sYyYfvKK7rHuJ2QX2Ik6zrZVrFcJ8imr9o lKUvRIM28kPwwn3G/Kak0kznBkE277wAtUovokFiGHL7UGkLydryjiPVXpMMmciNDfPH gJeTwijjiQqWrGwfMuorvgSYpnnS6Tyt0eIuTYELG/cQ92VyD72+ndj0uWEw5azvsMHA Kd7w== X-Gm-Message-State: AOAM531uswxpDXtXJiTm3PkjNcj+1pDYHGbM1LchRFDQgU98t38Tzz/t ysTfIrD6KvkwLXo1JXdOmP+4ZavjNhBS4bKUrVteQQ== X-Received: by 2002:a67:f1ca:: with SMTP id v10mr12138135vsm.55.1635513336043; Fri, 29 Oct 2021 06:15:36 -0700 (PDT) MIME-Version: 1.0 References: <20211026115916.31553-1-semen.protsenko@linaro.org> <8b3466f1-2b16-80ca-79c7-577860fc90aa@canonical.com> In-Reply-To: From: Sam Protsenko Date: Fri, 29 Oct 2021 16:15:24 +0300 Message-ID: Subject: Re: [PATCH] arm64: Kconfig: Enable MCT timer for ARCH_EXYNOS To: Marek Szyprowski Cc: Krzysztof Kozlowski , linux-arm Mailing List , Linux Kernel Mailing List , Linux Samsung SOC , Mark Rutland , Chanwoo Choi , Will Deacon , Marc Zyngier , Catalin Marinas Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 29 Oct 2021 at 14:38, Marek Szyprowski wrote: > > On 28.10.2021 16:35, Krzysztof Kozlowski wrote: > > On 28/10/2021 16:22, Sam Protsenko wrote: > >> On Tue, 26 Oct 2021 at 17:03, Krzysztof Kozlowski > >> wrote: > >>> On 26/10/2021 13:59, Sam Protsenko wrote: > >>>> Some ARM64 Exynos SoCs have MCT timer block, e.g. Exynos850 and > >>>> Exynos5433. CLKSRC_EXYNOS_MCT option is not visible unless COMPILE_TEST > >>>> is enabled. Select CLKSRC_EXYNOS_MCT option for ARM64 ARCH_EXYNOS like > >>>> it's done in arch/arm/mach-exynos/Kconfig, to enable MCT timer support > >>>> for ARM64 Exynos SoCs. > >>>> > >>>> Signed-off-by: Sam Protsenko > >>>> --- > >>>> arch/arm64/Kconfig.platforms | 1 + > >>>> 1 file changed, 1 insertion(+) > >>>> > >>> +CC Marek, Marc, Mark and Chanwoo, > >>> Looks like duplicated: > >>> https://lore.kernel.org/lkml/20181018095708.1527-7-m.szyprowski@samsung.com/ > >>> > >>> The topic stalled and I think this particular patch did not make sense > >>> on its own, without rest of changes from Marek. I am not sure, though... > >>> > >> Krzysztof, Marek, > >> > >> That series looks nice, I'm quite interested in that being applied. Do > >> you think I can do something to help with that (e.g. rebasing, > >> re-sending on behalf of Marek, testing on Exynos850, etc)? > > I think there were no objections against v4 of this patchset, but > > somehow it wasn't applied. > > > > Marek, > > Does it make sense to try respinning your v4? > > I think I've abandoned it, because I got a final NACK on the arch timer > change (support for 'not-fw-configured' timers). Without that the above > mentioned changes doesn't make much sense. > > I know that the Exynos5433 firmware breaks the defined protocol, but on > the other hand I can do nothing more than carrying internally those few > patches out of tree to keep it fully working with 'mainline'. > > I've observed the same problem with newer Exynos SoCs, but those so far > didn't get mainline support (yet), although there have been some > attempts from the community. > There is no such problem on Exynos850 SoC (which I'm trying to upstream right now), the architectured timer seems to be working fine there, as is. Or maybe everything is configured properly in bootloader, not sure. Also I managed to use MCT as a primary clocksource (for sched_clock, etc) by disabling arch timer in arch/arm64/kernel/time.c (just for the sake of test), and it works fine. So I still would like to have MCT enabled in kernel: this way we can at least test the driver, as the clocksource can be changed to MCT via sysfs (or by disabling arch timer in time.c). And for that we need to at least enable CLKSRC_EXYNOS_MCT in ARCH_EXYNOS. I guess all your patches (except one you mentioned) from that series should be fine to apply. Do you mind if I re-send your patch series (minus one patch) on your behalf? That would spare you some boring work, and at least minimize your local delta you're carrying. Thanks! > Best regards > > -- > Marek Szyprowski, PhD > Samsung R&D Institute Poland >