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 73101C433EF for ; Thu, 5 May 2022 12:05:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237149AbiEEMJL (ORCPT ); Thu, 5 May 2022 08:09:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45622 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232917AbiEEMJI (ORCPT ); Thu, 5 May 2022 08:09:08 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6F84E13CF7; Thu, 5 May 2022 05:05:28 -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 2DD64B82B79; Thu, 5 May 2022 12:05:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D5618C385A8; Thu, 5 May 2022 12:05:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1651752326; bh=YOSvkdiD9YeJgj4aRLVreDoeI4SdaGNCAtWBB3qrsZo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=MC2c9NhE+Pp2MlVr3eXkpI9xcJh1KF7xIr04oUTt6jPiN4MhfDWrvX4CmOp/8DIkx 6lLS9h6njGu+8KOSenAdgP5CoTDXKWtmfFqjh4LLgii3NS7DVLesGnm9Gs7r9ymxic g0DNA2Dz3sfBQAJ7NYg0FcGyPHC54ylRSMHbAtZo8btjuEaXYeSXqK6KkY/t8J6ZbT WPc4AabJ9vePARuVBWs1TjOjVg1JPToqG8IyIEdHtf8h0UHcYYTtljfxsDoZqmFH6M hNBQRcMltqpyX/xHW8zQKpLnymUyV8sXagxEvYa8dlASeDdK2OsxqiHFp6goiTffCW iNDW434jhq2zw== Date: Thu, 5 May 2022 13:05:19 +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, MyungJoo Ham , Chanwoo Choi 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="7moZXgHmwiy4vUEp" Content-Disposition: inline In-Reply-To: X-Cookie: Real programs don't eat cache. Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --7moZXgHmwiy4vUEp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, May 04, 2022 at 02:35:08PM -0700, Zev Weiss wrote: > On Wed, May 04, 2022 at 01:49:12PM PDT, Mark Brown wrote: > > For example if the output comes out on a socket then that socket should > > be described. > Okay -- in the case of an Open19 power shelf like the ahe-50dc, there are 50 > instances of this, 48 of which are in four ganged connectors each with 12 > pairs of pins, but two of which have their own dedicated little individual > sockets. The connectors are physically different, but they're all identical > as far as software is concerned, so I'm not clear on why it would need to be > expressed in any DT properties or the like. Or did you just mean > explanatory free-form text in the description field? Explanatory description would be one example of something that should be described, yes - if there is control for switching the supplies on and off the user is going to need to be able to figure out which software control corresponds to which physical connection. Other devices may have more things that need autoamtion (eg, jack detection). > > 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. > Alright, so would you suggest creating something like > drivers/extcon/extcon-regulator-output.c, and just having its extcon > functionality be something of a stub for now? I'm not super familiar with extcon but that seems plausible. --7moZXgHmwiy4vUEp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmJzvX8ACgkQJNaLcl1U h9A8UAf/fie/0qtJtkcTIuxOavIxjrhnkZVoXgVXIZQkG30kKpFcFusvyLn7WqXr gpDsmSfB5Z2Eg2pd6Vqx58Gst7G7sDnZJt5O7PubZzenBQCMkyiWZiyqc5Rufp9F vtG6Zfsj1xhkkmZiXuuLuoDm+xLqFTuybFX0WiFCyis5gqvJdMnESUYcxrAhqafh YnxdpGueFPqxO/tT8kXNrt62bk5xZ1VpJDtesx1FvQ/tGj1I0alTPs30SRrNRNyc UkYI4t+wLyPh/NGIukqN+yzllWgjjHM7LCMnAM+VyM9vMtNunlRtx/M+T4E8K1b3 j4fLzaFv8XLddtp/924vcwv2ZG/nnw== =k/3z -----END PGP SIGNATURE----- --7moZXgHmwiy4vUEp--