Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2778777ybl; Mon, 20 Jan 2020 09:10:27 -0800 (PST) X-Google-Smtp-Source: APXvYqz0onEfxx/NDF++KLwfsAaWuOSawugNJypJvCU8bhMD51WYN2u9hZ8WBhj9iDdp2/Q3LzQO X-Received: by 2002:a9d:da2:: with SMTP id 31mr301502ots.319.1579540227618; Mon, 20 Jan 2020 09:10:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579540227; cv=none; d=google.com; s=arc-20160816; b=vdmSyvE3+8r68FJGFmx7ojo38ZpEugMs3g26lsn+oUdF8GbfFnq9aoyS3iOnKMeGK9 ZOASf8c9DGQsZ4QmBEiP+YQZmhKcinLLfhwYHRCoJpzVDzf4d2pfpx+CsETz8+ZC853y 5zNyPSPd8CiFV7nmp7VWpw786kqz8ZYNW2sWp5+1NsUJ/BzK8g+flk+KPQGMKA9NfpCa 4IVONqm+OrKh/1O1/vSk0MuOsOIaw0gemDvuV95JLn5PCwl/fg47KI33CSW1TT28LGUg b1j+lQtU6prKkyk/itkWFHxrF7rM2+oSHCwYab6lyQdkFtG4H1S8ZyiOwLfZAH4w13yu AeKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=qtpq7Ni1zovk0mzgogyywBbU/2XmkPRvIj+EhvsDfUE=; b=OZWcFcB9WXrOEAQR8NRbhsx/Ne9pV8t5Bxv41cahjlAz2CRpRVcq4QqIoVEtzskpOX Do5auGm46SzeWpgbbIPdAHI7cjuSOHMJmYyDnGJQ3cxuy/jIP9ZTF7Xp0+XlIGi9URFq Znpn03amBSCZiYb8xgPq4tLqSSmS3JuAOiY+PpsQfHUSoPynE0sZ+KDir0czggGy7FxI dyUt9LJj1mRfglINFf/U0aZ3OaSjTjb6RMC3AyL++eLbIqSk8uyTKIbeXWU4YDEiQzCf EJLQ//nMY9FhOgTg7MrHmTGfegQ/oLpx5M2LAScNfftTAWiF/s7ctCc6B4mMfUVwEPbE goEA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v6si20575549ota.19.2020.01.20.09.10.15; Mon, 20 Jan 2020 09:10:27 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729259AbgATRJN (ORCPT + 99 others); Mon, 20 Jan 2020 12:09:13 -0500 Received: from foss.arm.com ([217.140.110.172]:34844 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726642AbgATRJN (ORCPT ); Mon, 20 Jan 2020 12:09:13 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 78A5531B; Mon, 20 Jan 2020 09:09:12 -0800 (PST) Received: from [10.1.194.52] (e112269-lin.cambridge.arm.com [10.1.194.52]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 3FCC83F68E; Mon, 20 Jan 2020 09:09:10 -0800 (PST) Subject: Re: [PATCH v3 4/7] drm/panfrost: Add support for multiple regulators To: Mark Brown Cc: Mark Rutland , devicetree@vger.kernel.org, Nicolas Boichat , Tomeu Vizoso , David Airlie , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Liam Girdwood , Rob Herring , linux-mediatek@lists.infradead.org, Alyssa Rosenzweig , hsinyi@chromium.org, Matthias Brugger , linux-arm-kernel@lists.infradead.org References: <20200114071602.47627-1-drinkcat@chromium.org> <20200114071602.47627-5-drinkcat@chromium.org> <7e82cac2-efbf-806b-8c2e-04dbd0482b50@arm.com> <20200120170343.GE6852@sirena.org.uk> From: Steven Price Message-ID: Date: Mon, 20 Jan 2020 17:09:08 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 In-Reply-To: <20200120170343.GE6852@sirena.org.uk> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/01/2020 17:03, Mark Brown wrote: > On Mon, Jan 20, 2020 at 02:43:10PM +0000, Steven Price wrote: > >> From discussions offline, I think I've come round to the view that >> having a "soft PDC" in device tree isn't the right solution. Device tree >> should be describing the hardware and that isn't actually a hardware >> component. > > You can use an implementation like that separately to it being in the > device tree, it is perfectly possible to instantiate devices that have > no representation at all in device tree based on other things that are > there like board or SoC information, or as subdevices of things that are > there. Yes - and I may yet implement a "soft PDC" device if this turns out to be more than a 'quirk' for a very small number of device. But like you say - it doesn't need to be (and shouldn't be) in the actual device tree. For now though I think the code Nicolas has written works well enough and it's only really worth 'fixing' if we end up with too many 'quirky' devices. Steve