Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp8202292ybi; Tue, 23 Jul 2019 04:36:29 -0700 (PDT) X-Google-Smtp-Source: APXvYqy/6o6MtOKLs8vumJRGSwcMODu+Kzks8HiDUkieoPBJjCHCyF9AGuD5jVagSkflW0qBD8gO X-Received: by 2002:a65:6850:: with SMTP id q16mr39331515pgt.423.1563881789737; Tue, 23 Jul 2019 04:36:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563881789; cv=none; d=google.com; s=arc-20160816; b=PY3qgqGfBgwNyQqbPDvIPGfgFUH7uDmpWMbHyI/0LbzwKjsL/RI1sr5wZ9ZSPD5yIo oAccdb1+ZXnfkhhjxD9bioXyi0lF+VUXvyKFhHYnrFIAhjanKZvfN4r7gEiXPa9LxUoQ HaR7pirzZQGXDZet1G/tSDUx7x42IU/+8/rQ9Ac2EtFixFpXHt/XVIWzsJzeYwi6VRtr 0ilbzJpMn1B9WFxxXS54tvGVAQFazPuh2m4MF4LiRkHIiGkrWF4xMKota5Mh2K6i6WtH Kh6pvHJdC2jTLBco5OjlSxYpWB5LKZM0atMXeB4Yd4Mg4cnZym+JYwD3DD4fDnkkn4pp UJxA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=c+fYefKdegWfzNVcvBNCZFAqK5d+WzXI5vtjxfFF6J8=; b=BMQwuHDUILUsgkJqtyEpa1N1VJ3gUTtbKHuzwStqor0aS0rXKWLy05MVYtBuQORf5w z5Q5Ey4J+73LTvDMEoIY+ZKilsqzdT8GnXq/JripvKW+zYSzzp2QO3HHylsABNITDbJc 9zjTzA2g7CM3U7fmCQ1l5ifNmMompEdrkCgfeddoqZW2jjjNDRtPwNe+tK3CMWlfX5jC zjFsqZW0jmZhFPThylJMIV1Bhq/AR/zBBzQSce66UMpL6kF0WjboH3Td0Djdzkh1UoHS 9edQE/ngea893T8Upsq0MFYyeE9h4DbRmnICwk6dKI1iXQup676iebUkil7p8iXHxOBC rayQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=zRFzuYvW; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id k198si11781805pga.313.2019.07.23.04.36.12; Tue, 23 Jul 2019 04:36:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=zRFzuYvW; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1729534AbfGWCEy (ORCPT + 99 others); Mon, 22 Jul 2019 22:04:54 -0400 Received: from mail-pl1-f194.google.com ([209.85.214.194]:45095 "EHLO mail-pl1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726284AbfGWCEy (ORCPT ); Mon, 22 Jul 2019 22:04:54 -0400 Received: by mail-pl1-f194.google.com with SMTP id y8so19942116plr.12 for ; Mon, 22 Jul 2019 19:04:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=c+fYefKdegWfzNVcvBNCZFAqK5d+WzXI5vtjxfFF6J8=; b=zRFzuYvWEWhGryAT6Q8/QwGY+31z0WJLeKBR9uQowX7cZbFobNq11qUpTg8+BZ9xdX geyyg7Y+iGQzwrwj3w8cE1UZojdY1o3jWGaU9cpggpJHJO1wmLY1aPQwKWhPKX7GxOIm /NvsPv7aR2tvFuB2l39aNzgFqRfkVWHNr/zBjK6BcrfdIBv5z6Ljx1/ZPwVyrbRfH+fn WC0xIll82mi599BW7YbJ6tFjpvgPx0Lgi5B03JE0YEPlBUchR3PWyTjQSVOMMOY5KJ2F be5nLPczyeJJU4UOXcnq4KKqAfKifvC4IYRjLWX3B2c/N80/HngqF6zuF/cKP6wBQfJd yM2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=c+fYefKdegWfzNVcvBNCZFAqK5d+WzXI5vtjxfFF6J8=; b=gfi4zmwWquIKKMkJ0CabcuS3XJ9ATIl0RgkvG/XjiyFvYVodag18eDRrcFtmDl973/ mnOvMGYeCQIKQaGRa7ZVjdLfN/VcxEhFeQ2biRa01onXYLuU4/IaSBifyDlyt6By2isD 2yT1f4DrlSoWdgpUVgi38VCo2UOZ5uK41nPAXr8iuiY0iSbxoFs/a70fu6RZ4sT2m8e/ SjIKxMjJvZVdwE9ydszUhIqtnE9oItbS1Jl0MffA6KtuJDgtBg9rlxVCYxTQ85hez+Ir j+rm1/sBIzJI9hVZHtA2gUYzJYLqZuJoehZOf2YlviZjZPQ1jtwLS47AZ2006g1hzEEQ W5Bw== X-Gm-Message-State: APjAAAVbvTGunjuNe7O53Ua5rPtUFYOu8by9HlmE/PHPwYUUGpNxMGpw 6/QCgxlFQ32vFz9OJPWTZzcC0w== X-Received: by 2002:a17:902:4623:: with SMTP id o32mr76901784pld.112.1563847493573; Mon, 22 Jul 2019 19:04:53 -0700 (PDT) Received: from localhost ([122.172.28.117]) by smtp.gmail.com with ESMTPSA id z63sm6349546pfb.98.2019.07.22.19.04.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jul 2019 19:04:52 -0700 (PDT) Date: Tue, 23 Jul 2019 07:34:50 +0530 From: Viresh Kumar To: Sylwester Nawrocki Cc: krzk@kernel.org, robh+dt@kernel.org, vireshk@kernel.org, devicetree@vger.kernel.org, kgene@kernel.org, pankaj.dubey@samsung.com, linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, b.zolnierkie@samsung.com, m.szyprowski@samsung.com Subject: Re: [PATCH v2 0/9] Exynos Adaptive Supply Voltage support Message-ID: <20190723020450.z2pqwetkn2tfhacq@vireshk-i7> References: <20190718143044.25066-1-s.nawrocki@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190718143044.25066-1-s.nawrocki@samsung.com> User-Agent: NeoMutt/20180716-391-311a52 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 18-07-19, 16:30, Sylwester Nawrocki wrote: > This is second iteration of patch series adding ASV (Adaptive Supply > Voltage) support for Exynos SoCs. The first one can be found at: > https://lore.kernel.org/lkml/20190404171735.12815-1-s.nawrocki@samsung.com > > The main changes comparing to the first (RFC) version are: > - moving ASV data tables from DT to the driver, > - converting the chipid and the ASV drivers to use regmap, > - converting the ASV driver to proper platform driver. > > I tried the opp-supported-hw bitmask approach as in the Qualcomm CPUFreq > DT bindings but it resulted in too many OPPs and DT nodes, around 200 > per CPU cluster. So the ASV OPP tables are now in the ASV driver, as in > downstream kernels. Hmm. Can you explain why do you have so many OPPs? How many frequencies do you actually support per cluster and what all varies per frequency based on hw ? How many hw version do u have ? I am asking as the OPP core can be improved to support your case if possible. But I need to understand the problem first. -- viresh