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 X-Spam-Level: X-Spam-Status: No, score=-7.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E6971C433E3 for ; Fri, 21 Aug 2020 06:32:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C4FB120732 for ; Fri, 21 Aug 2020 06:32:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1597991550; bh=415OZuU8vzA50+rnOVabsjrgwD2vNtA0NKm0cqriH7Q=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=U7p0me/mdbSGoUg/fouMsi2NiC+83BwDWPRTIKAGvv2VwssJ5Zd5I8VUvdCC8ocOa tDHT6l+/Im8c1bPDHh+WA4pFNlFP/1CscMw8/pGB65ZLyXOcGsS3jXySqbFsFRr7uz 7YLtkHhDl9SB1g36QECKfXd5QlEvfSRY/03PBQrc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727797AbgHUGca (ORCPT ); Fri, 21 Aug 2020 02:32:30 -0400 Received: from mail.kernel.org ([198.145.29.99]:42410 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725992AbgHUGc2 (ORCPT ); Fri, 21 Aug 2020 02:32:28 -0400 Received: from mail-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 57E19207DA; Fri, 21 Aug 2020 06:32:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1597991547; bh=415OZuU8vzA50+rnOVabsjrgwD2vNtA0NKm0cqriH7Q=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=DuUO7+ImHFtJQvWsmC/X9O7YR+C/54F+4qsahrFrMc6qY/L3qvv2O1nhHQnqCTvWp DBKfRpVW93mQ3Qc3YiU/OCrB9bhR34qnq4FvcaCHsVHaEl5d0oPK+3ll8CQ62mqJZy yWtpPLov+lbV3CgFmJr8wKJ3bba0yhiF7uDvT81s= Received: by mail-ej1-f51.google.com with SMTP id u21so360590ejz.0; Thu, 20 Aug 2020 23:32:27 -0700 (PDT) X-Gm-Message-State: AOAM531TL/cVnX3hDJHLEGfB3INtcPVrztq/0Ig/oN/E8kwzP+LJMxlI Bg695nUsnJKOSA0/kMNKbaC0uUR+pUYUba0ZoDk= X-Google-Smtp-Source: ABdhPJzmNhcgBP4BHaa4+ob9gDnpioFjxsyx1iS1AVeOQjeO7mUt56aSdcZBGdYVXX8gX6athEENQYiVtJNm5lspNOA= X-Received: by 2002:a17:906:4ec3:: with SMTP id i3mr1400283ejv.215.1597991545947; Thu, 20 Aug 2020 23:32:25 -0700 (PDT) MIME-Version: 1.0 References: <20200708153420.29484-1-lukasz.luba@arm.com> <20200708153420.29484-3-lukasz.luba@arm.com> <20200817155021.GC15887@kozik-lap> <2099aea9-5a63-6e5b-d7f9-4e6476584461@arm.com> In-Reply-To: From: Krzysztof Kozlowski Date: Fri, 21 Aug 2020 08:32:14 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 2/2] ARM: dts: exynos: Remove interrupts from DMC controller in Exynos5422 To: Lukasz Luba Cc: "linux-kernel@vger.kernel.org" , linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "linux-samsung-soc@vger.kernel.org" , willy.mh.wolff.ml@gmail.com, k.konieczny@samsung.com, Chanwoo Choi , =?UTF-8?B?QmFydMWCb21pZWogxbtvxYJuaWVya2lld2ljeg==?= , chanwoo@kernel.org, myungjoo.ham@samsung.com, kyungmin.park@samsung.com, s.nawrocki@samsung.com, kgene@kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 21 Aug 2020 at 08:31, Krzysztof Kozlowski wrote: > > On Mon, 17 Aug 2020 at 19:17, Lukasz Luba wrote: > > > > Hi Krzysztof, > > > > On 8/17/20 4:50 PM, Krzysztof Kozlowski wrote: > > > On Wed, Jul 08, 2020 at 04:34:20PM +0100, Lukasz Luba wrote: > > >> The interrupts in Dynamic Memory Controller in Exynos5422 and Odroid > > >> XU3-family boards are no longer needed. They have been used in order > > >> to workaround some issues in scheduled work in devfreq. Now when the > > >> devfreq framework design is improved, remove the interrupt driven > > >> approach and rely on devfreq monitoring mechanism with fixed intervals. > > >> > > >> Reported-by: Willy Wolff > > >> Signed-off-by: Lukasz Luba > > >> --- > > >> arch/arm/boot/dts/exynos5420.dtsi | 3 --- > > >> 1 file changed, 3 deletions(-) > > > > > > I think the dependencies were merged so this can be safely applied > > > without bisectability problems? > > > > I have created v2 of that fix and it got merged > > via Chanwoo's tree, the commit 4fc9a0470d2dc37028 > > https://lkml.org/lkml/2020/7/10/1048 > > > > That commit switched the driver default mode from 'irq driven' to > > new devfreq monitoring mechanism. Furthermore, when the driver is > > built as a module, you can try to use the 'irq mode', but for this > > you would need the DT IRQs description (this $subject tries to remove). > > > > I would like to keep this IRQ mode for experimentation, as I > > described in answers to Bartek's questions: > > https://lkml.org/lkml/2020/7/14/315 > > > > Unfortunately, I am quite busy and won't make any progress before the > > LPC. > > None of these were the actual answer to my question, unless by "v2 of > that fix and it got merged" means the dependencies? > > I'll drop it from the queue. Please resend if it is valid. Agh, not drop, I mean postpone for the next cycle (this is v5.11). Best regards, Krzysztof