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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3ED4AC433EF for ; Wed, 4 May 2022 20:49:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1378362AbiEDUxA (ORCPT ); Wed, 4 May 2022 16:53:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39952 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235304AbiEDUw6 (ORCPT ); Wed, 4 May 2022 16:52:58 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 495904F9EE; Wed, 4 May 2022 13:49:21 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 4E02DB82984; Wed, 4 May 2022 20:49:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 229DEC385A5; Wed, 4 May 2022 20:49:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1651697357; bh=uAn1jx4nc/AyBKpUGArQO9zmKvmz3TirIiMxZEWuzcw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=azIP2rCeokqKbAzsWLeh/51f72I2r/dtxufFiQT1RPrFaPBYSqj/s5pkOUM5GmsQV nrQM+zGGqt4HRLNoTaaPKnVTVceTC+7XgOV4PkrmXeM4DkT9UaVUBlFHafejXpLhRY arLbbxLrx+rL0Q1WHeG2FHnKcBsN8OFkEgHRjhaqLNCyMeO2bybTg/lO8iUzwsjxfJ 2BfMNwBbm1EF1B6IXsbTgFNCyoq7p6yNtWJQYiAxKNgIyEFGPEKOCPNOW6n/v2uKmA YYChYKS8chwl6Dj0bV9jmrItxddT2tuFiF5Si96tvZF9eBBnePoKXHKqdq8tt+sJ53 D/FNXZ5sQxacA== Date: Wed, 4 May 2022 21:49:12 +0100 From: Mark Brown To: Zev Weiss Cc: Liam Girdwood , Rob Herring , Krzysztof Kozlowski , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Greg Kroah-Hartman , openbmc@lists.ozlabs.org Subject: Re: [PATCH 2/6] dt-bindings: regulator: Add reg-external-output binding Message-ID: References: <20220504065252.6955-1-zev@bewilderbeest.net> <20220504065252.6955-2-zev@bewilderbeest.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="66W6v/kA9l7TTEWD" Content-Disposition: inline In-Reply-To: X-Cookie: Mother is the invention of necessity. Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --66W6v/kA9l7TTEWD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, May 04, 2022 at 01:33:58PM -0700, Zev Weiss wrote: > On Wed, May 04, 2022 at 05:55:53AM PDT, Mark Brown wrote: > > I think at a minimum anything like this would need some sort of > > representation of how the output physically appears so that people can > > work out how outputs are mapped to the hardware they see. > I don't quite understand what you're describing here -- could you elaborate > on what you mean by "how the output physically appears", and what that might > look like in a DT binding? For example if the output comes out on a socket then that socket should be described. > > However we > > already have a subsystem for external connectors - extcon. Perhaps this > > should be a regulator client in the extcon API? It's common for > > connectors to include some sort of power provision so it seems like this > > would fit right in. > Interesting -- I wasn't previously aware of the extcon subsystem, thanks for > the pointer. However, after looking at it a bit, I'm not sure I see how > it'd be applicable here, since it looks like it's built to handle hardware > that's at least sophisticated enough for software to tell whether or not > something's plugged in, which isn't the case here. The connector is just a > ground pin and +12VDC pin, no presence-detection mechanism or anything else. > Outside of the regulator itself there's really no "device" there for > software to talk to or otherwise interact with at all. Sure, but there's no reason why it can't scale down to something simpler. It's easier to support something simpler than have to extend to support something more complicated. --66W6v/kA9l7TTEWD Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmJy5sgACgkQJNaLcl1U h9B35Af+PHHkp2wfo6G66nqsy/m9SQn1PAVUGFZ0DrivXUKk7YOodvsS0HglBDu2 gkBV/c4Kdp3RrS3MYpqsGRRCdkRMiEO98WLKhnIW7LVqs4fB+BMi6TbFUyJX4IVS S86d8/3j97F7mA/EzmITT3naxTPMnym23r2wDfL1BTf7MuQGwRbchmQfwxArsz4c Vh+CbfhYTk4b7X4sG8AddkqRvRG0yuHtokGbIqBFOiPZbgulVrqWPPKLYgIzqYKY LTo2IeGwL5pRTtzfqNDNfWsMfFo879rPIzeOCUvzraToQRABMPanKEyP/LYI7eWA c9LJQhPk8fhLuDunH6clBkWd1m1CBg== =lUz7 -----END PGP SIGNATURE----- --66W6v/kA9l7TTEWD--