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=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 A713FC54FCF for ; Sun, 22 Mar 2020 16:01:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7447E2072E for ; Sun, 22 Mar 2020 16:01:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=startmail.com header.i=@startmail.com header.b="U6XcNeoS" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725997AbgCVQBZ (ORCPT ); Sun, 22 Mar 2020 12:01:25 -0400 Received: from mx-out2.startmail.com ([145.131.90.155]:57586 "EHLO mx-out2.startmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725881AbgCVQBZ (ORCPT ); Sun, 22 Mar 2020 12:01:25 -0400 Date: Sun, 22 Mar 2020 18:06:04 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=startmail.com; s=2017-11; t=1584892883; bh=tw0ThCWI6Kf/ThW1nb3APK71N9og+oAkYn4EacBWeMY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=U6XcNeoSW3y31P1NSwUv664upochH/VhOGSeIZvsaGD/43e5v285IK1r0wstqbLWM GNFGh5XA0EQLDNRBvy0JVJc4y2koeCCYKOkQDPJJ/SqO/0euqpQHETeIwwMm9YovX3 u0IGDw7Ea2nWOtvnwhMg28YMnaqKirLIn1M8aHsBtWHeXkGvNV4TfiKuMwlZ6cAlej lW+2DVzCwqyvIBMj9Nrbdo/8TQSx+pIWmkcjb8+UFic7ybqLDJb7qAjoOt+D6vtRMD OsaTx3qfRRZj7Tuwf45P7MnaupD2PjQXvdXnQnhXXPsUHaooV1RRe0ntzDQSGLTNTb Wb9FS/eVlIz5g== From: Alexandru Lazar To: Jonathan Cameron Cc: "Ardelean, Alexandru" , "robh+dt@kernel.org" , "mark.rutland@arm.com" , "devicetree@vger.kernel.org" , "knaack.h@gmx.de" , "linux-iio@vger.kernel.org" , "pmeerw@pmeerw.net" , "lars@metafoo.de" Subject: Re: [PATCH v4 1/2] dt-bindings: iio: adc: Add MAX1241 device tree bindings in documentation Message-ID: <20200322160604.GA222611@leena.republic> References: <20200320150114.9297-1-alazar@startmail.com> <20200320150114.9297-2-alazar@startmail.com> <20200321173412.52548ef1@archlinux> <20200321193541.GA16892@leena.republic> <1e51c4079222858410e9fe94c9d7f21d99abfe15.camel@analog.com> <20200322095317.GA3099@leena.republic> <20200322152735.36cb3493@archlinux> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200322152735.36cb3493@archlinux> Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org > You'd be surprised how often this gets added to drivers precisely because > people will put it on a controllable supply. It may well not have it's own > supply but it may share one with a bunch of other external chips and > all of them need to use the regulator framework controls to make sure it's > only disabled when they are all suspended etc. I figured it might be something like this :-). I've added the vdd-supply binding in v5. If this isn't something that can be easily handled in the core, do you think we can document it somewhere as a convention/common idiom? (Assuming it's not already documented, of course). It seems like it's something that all IIO devices would need. I can do the writing part. Thanks, Alex