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=-7.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 29673C433ED for ; Tue, 20 Apr 2021 16:13:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DD9A7613C9 for ; Tue, 20 Apr 2021 16:13:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233065AbhDTQOS (ORCPT ); Tue, 20 Apr 2021 12:14:18 -0400 Received: from mail.kernel.org ([198.145.29.99]:55714 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232901AbhDTQOQ (ORCPT ); Tue, 20 Apr 2021 12:14:16 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 02DE6613C4; Tue, 20 Apr 2021 16:13:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1618935224; bh=cD3y7b3kSrwWftJRkxx0RYSxy1zhp+eP+mHHMyD5znU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=p72y/+C8zRB7jibKzZbKoTo/4uyciL4SpZsoR7nj2YJec0zW/MCB5DPdwwosi/2pM U2GgmVaYXdVJoucJvIUgePup+nRr8NSaVmI4VG6xl3Hi4GEcaKuKdbnb/3MlwGhZRn 6YRNqNYBKbW7XhTMAz++sKLDXKnCXn8YuoifOVUJodf2hEm0ZXACnhRjPBvARLkmBo UVPlbEHHUb1bmAGvpqkfXtNmmKTnilvKc4djCmzP/gPch3f5XUHXy11DVceQhGqCh3 0UxfV6M9+HBiNWxwXcVLwhdOhPltUygJRaw7SKNahQArEKMYUWMPhhqZL/BuI7+OI+ xDN6Rzd+SqB7g== Date: Tue, 20 Apr 2021 17:13:18 +0100 From: Mark Brown To: Zev Weiss Cc: Guenter Roeck , Jean Delvare , linux-hwmon@vger.kernel.org, Andrew Jeffery , Liam Girdwood , linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org Subject: Re: Enabling pmbus power control Message-ID: <20210420161317.GE6073@sirena.org.uk> References: <20210330180200.GK4976@sirena.org.uk> <20210330193810.GA235990@roeck-us.net> <20210420033648.GA227111@roeck-us.net> <9639fa33-01ca-9802-e745-5e3edb81e305@roeck-us.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="KlAEzMkarCnErv5Q" Content-Disposition: inline In-Reply-To: X-Cookie: Falling rock. User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --KlAEzMkarCnErv5Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 20, 2021 at 10:19:04AM -0500, Zev Weiss wrote: > Mark, do you have any further input on what a viable approach might look > like? I already suggested writing a driver or drivers that represent the hardware you have, that advice remains. It's hard to follow what you were trying to say with your long mail earlier today but it seems like you basically don't want to use any abstraction or framework, but that's not really suitable for upstream integration - other hardware that looks similar to the end user should look similar in the kernel too. --KlAEzMkarCnErv5Q Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmB+/Z0ACgkQJNaLcl1U h9A2Hwf/SWR76PMEbzeYJSpzqHxdwIVdQoQPT//JnsDvGXFKZpXK29a+gvAY9EW2 vR/O/no5OLWRaQ6DRjrNbg4y3kcNsGSIMBrl1g0+jO+Iznes8ZRqBkFYcsh2uHnA b6ZHnLqIhfIoSxC2WfYKo1ZlHoJzZJwgD9tTIs0B6/jWJ0VmtWH1Vfkg7Efcwfq7 YQv84OLLrLaXPBCrF9U2Gekw+Ju9JHnH8fPIlyeHQHN1JW4M/nOYc7ri5R/islne SLA9DkV7l/cr6YUDU6eKCB8F5I2XEpJOOLgGcnMYo0rpTZoypOUygw6ZxEXk34qy 2AmIyG9TTs70sV/hLjrJEXBh+PNynA== =T6vq -----END PGP SIGNATURE----- --KlAEzMkarCnErv5Q--