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=-1.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,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 E4F5DC74A30 for ; Wed, 10 Jul 2019 17:01:22 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id BAA1A21019 for ; Wed, 10 Jul 2019 17:01:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="M4/BAqLQ"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="U//DVdj8" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BAA1A21019 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=mUtC0qciyPFqGyTdadjqihj9RNzDyjAO0GZhgEJtfb0=; b=M4/BAqLQyKz3PF +2wJBLxXsHbgUu6mfJ2Zis2eNCVWBh4HlXivu2VqeZrnVLkcDIPpzgdP/4K0dP6IwA++bVKih12Id Km5flLQ9L+ULx8yp6HrpweFFZ68xTJ5lSjYv1SE4Eu4Z60Y3au9KhKTAA4E/EJIHJQf+hE+TYP3Hu RYfV8/6y9SpQzTJgkIE+1aT5I7ueEcLw8cD1K9kGrCjk4zZkhs6ATI/Q80sQ2nmXu/p7eYI1tkreU kOLp8V08jWPTUL3vx6bxMj8AFvwDu8JTVizaWNJjCKKv9z8SjRj4+/M5AaPGJ5h+vNcaK/O7M3MrN +te0FjI4HYACZ8zigLNg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hlFy2-0004Wm-Lq; Wed, 10 Jul 2019 17:01:18 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hlFy0-0004WK-7N for linux-arm-kernel@lists.infradead.org; Wed, 10 Jul 2019 17:01:17 +0000 Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) (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 3C50621537 for ; Wed, 10 Jul 2019 17:01:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562778075; bh=TxbpTbFTB6tcLStSvP+aZxI9Q0R2lb9U8jlmNMNQU/k=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=U//DVdj8YeqqMqoEDtUVuLtXzsBFDbK43r7r+8WEjfC1VRimpCIv2wgciP4TBN/1i J5jJLff9enx6GJSi0qmcn2fHltBH8KhSQR0qMHQ+By8LbYiJ+S6vw1yXceuxXgquR4 s/H+wScP71uIDBVJapDktsBgEARQrR4kG7GwHgdk= Received: by mail-lf1-f42.google.com with SMTP id v85so2100439lfa.6 for ; Wed, 10 Jul 2019 10:01:15 -0700 (PDT) X-Gm-Message-State: APjAAAWKCBSZ1+OeOJ54nq/Q+r4tLdsMiMZKiMhnNQUcGBG8tTrHSyeG 2GO9f7Qr52DSCnaJ4IY2gRbytgBaSqqDb4t3OIA= X-Google-Smtp-Source: APXvYqxUw6gRJ6UeOU32AlyJP63sp59JGRy6Bmn26fDc8R5P8j2rXUGuDLf2Ue/ajr7oZwhSM/V1T6YgEMGuHxdFzX0= X-Received: by 2002:ac2:4d1c:: with SMTP id r28mr14953327lfi.159.1562778073455; Wed, 10 Jul 2019 10:01:13 -0700 (PDT) MIME-Version: 1.0 References: <20190708141140.24379-1-k.konieczny@partner.samsung.com> <91f65527-3440-90fd-4096-5824fba1df78@partner.samsung.com> <631ffd68-7aab-2483-8799-2019bf3bb444@partner.samsung.com> In-Reply-To: <631ffd68-7aab-2483-8799-2019bf3bb444@partner.samsung.com> From: Krzysztof Kozlowski Date: Wed, 10 Jul 2019 19:01:02 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 0/3] add coupled regulators for Exynos5422/5800 To: Kamil Konieczny X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190710_100116_299465_E2D58CA9 X-CRM114-Status: GOOD ( 22.57 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , Nishanth Menon , "linux-samsung-soc@vger.kernel.org" , linux-arm-kernel@lists.infradead.org, Bartlomiej Zolnierkiewicz , Stephen Boyd , Viresh Kumar , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , Chanwoo Choi , Kyungmin Park , Kukjin Kim , MyungJoo Ham , devicetree@vger.kernel.org, Marek Szyprowski Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, 10 Jul 2019 at 15:51, Kamil Konieczny wrote: > > On 10.07.2019 12:14, Krzysztof Kozlowski wrote: > > On Wed, 10 Jul 2019 at 12:03, Kamil Konieczny > > wrote: > >> > >> On 10.07.2019 11:00, Krzysztof Kozlowski wrote: > >>> On Mon, 8 Jul 2019 at 16:12, wrote: > >>>> > >>>> From: Kamil Konieczny > >>>> > >>>> Hi, > >>>> > >>>> The main purpose of this patch series is to add coupled regulators for > >>>> Exynos5422/5800 to keep constrain on voltage difference between vdd_arm > >>>> and vdd_int to be at most 300mV. In exynos-bus instead of using > >>>> regulator_set_voltage_tol() with default voltage tolerance it should be > >>>> used regulator_set_voltage_triplet() with volatege range, and this is > >>>> already present in opp/core.c code, so it can be reused. While at this, > >>>> move setting regulators into opp/core. > >>>> > >>>> This patchset was tested on Odroid XU3. > >>>> > >>>> The last patch depends on two previous. > >>> > >>> So you break the ABI... I assume that patchset maintains > >>> bisectability. However there is no explanation why ABI break is needed > >>> so this does not look good... > >> > >> Patchset is bisectable, first one is simple and do not depends on others, > >> second depends on first, last depends on first and second. > >> > >> What do you mean by breaking ABI ? > > > > I mean, that Linux kernel stops working with existing DTBs... or am I > > mistaken and there is no problem? Maybe I confused the order... > > It is not ABI break, it should work with existing DTBs Ah, thanks. My misunderstanding then. Looks good. Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel