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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED 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 03D8EC433E6 for ; Wed, 2 Sep 2020 08:52:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D30172078B for ; Wed, 2 Sep 2020 08:52:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="b7kETiou" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726567AbgIBIwv (ORCPT ); Wed, 2 Sep 2020 04:52:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45352 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726426AbgIBIwr (ORCPT ); Wed, 2 Sep 2020 04:52:47 -0400 Received: from mail-pl1-x644.google.com (mail-pl1-x644.google.com [IPv6:2607:f8b0:4864:20::644]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 58610C061244; Wed, 2 Sep 2020 01:52:47 -0700 (PDT) Received: by mail-pl1-x644.google.com with SMTP id bh1so1967066plb.12; Wed, 02 Sep 2020 01:52:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t5kK6Wa2EiA8NHptvj4DdfbhcaDVH2VnHPRJxPmhabs=; b=b7kETiouwJ153YPVInR5Q1rNs+RB/u2YtTWsd7rePfstwn6Z3cExVJ1qeUKG7nlogE UI8I7EMN/Z0rM14ZieXpbkXzSQMvfbvuEm+1nRuRNn+3zVPdTNY1ebSu88A8Ha7bTZpt s5Lzfzl5T7tF5+JFEdS7WRosBSF+UHLvnHlxJrGp9u9CwS++61yXo8/pEm3Qd6HAsVMC 6mVMzgOsLPJzdF1l8ylFRrtD2oJVelOj1sng0Ze9o84M3mBCpk7g0XMas4p4pG2pVpYZ 1rX3kQoYBjF2UpeJDboewgnG8c8kMQbyweS1VVdCosXFDHoCBhYzKg85hlFAPlybrM+r G+sQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t5kK6Wa2EiA8NHptvj4DdfbhcaDVH2VnHPRJxPmhabs=; b=QsbhbxiTwRaEMDoI7i9E0dZ3Sdg7a2tTV6kWTk3mPlKK5ao+j324QV0LLlg0Zw2QnR YvYin10vc9tiop05YKSGgcQZMM37+wPhUmqpwOfalH2hus0Ga1xnRNiRz7uq5+jOBSXb w80OebjaCxOaStZlMVpUzUg/vBKS3JH3lpsI3VlnfwtQQylOozRKrYcZV4lHdyYks6Q+ s/rDkpeFpc2Nsk+zX5aUq2k3vRQ99z+oMjmgguMtmn8PQ+jEjUXeGS1S8QRuKpcOgG0B JnXy+7ugsd3WLY3epmhmgP13TM0jzTv82AKj8Glzy8c5Zld0DGq42NsQrHzWJyDVyOui sktw== X-Gm-Message-State: AOAM533EMmVjH0IoiKhYTVRWoUtw5B8o6zQtnTm1i5ySgRm4ijuKuCfA br1GAhjJ5nBnYgOgzKJQryMhk2GgGahFeA2mlpc= X-Google-Smtp-Source: ABdhPJxkPxK6trSlnvLhkEo/gpXsPaxPq+zOvuJ5Z0Z1qNTtmQ2HGXwCVkoUiBr1B8I5XxZq0RiYUf7gF9GyRgUB48o= X-Received: by 2002:a17:90a:2c06:: with SMTP id m6mr1407120pjd.129.1599036766868; Wed, 02 Sep 2020 01:52:46 -0700 (PDT) MIME-Version: 1.0 References: <20200824054347.3805-1-william.sung@advantech.com.tw> In-Reply-To: From: Andy Shevchenko Date: Wed, 2 Sep 2020 11:52:29 +0300 Message-ID: Subject: Re: [PATCH] iio: dac: ad5593r: Dynamically set AD5593R channel modes To: "Hennerich, Michael" Cc: AceLan Kao , "Ardelean, Alexandru" , William Sung , Lars-Peter Clausen , Jonathan Cameron , Hartmut Knaack , Peter Meerwald-Stadler , linux-iio , Linux Kernel Mailing List , Campion Kang Content-Type: text/plain; charset="UTF-8" Sender: linux-iio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org On Wed, Sep 2, 2020 at 11:09 AM Hennerich, Michael wrote: > > From: Andy Shevchenko > > Sent: Montag, 31. August 2020 14:46 > > On Mon, Aug 31, 2020 at 2:28 PM AceLan Kao > > wrote: ... > > P.S. Jonathan, it seems this driver has artificial ACPI HID. We probably have to > > remove it. However, ADS is indeed reserved for Analog Devices in PNP registry. > > Can we have AD's official answer on this? > > Cc'ing additional AD people. > > Agreed, this ID was chosen under the PNP ID Vendor Space for Analog Devices Inc. > Days back, I did a quick kernel grep, and there are many drivers which use the 3-letter > PNP ID as acpi_device_id. So, I thought this being not an issue. No, no, the use of PNP ID is not an issue. The point is if the ID is artificial or official. > I'm against removing it since I know people shipping this in their ACPI tables already. I see. Can we consider this email as the official answer from AD that this ID is being allocated for this certain component? > Regarding ACPI DSD customization, one way to do this is to move this into the BIOS. > This way the particular piece of HW can be customized rather than manage HW > connections in software. Assuming the confirmation on the above, indeed, one may use ACPI HID with DSD properties in the firmware. Main purpose of PRP0001 is the *development* stage of the product at which a vendor should take care about allocation of proper ACPI IDs for the components in use. Yes, I know that this is not always feasible b/c some HW component vendors don't care about ACPI at all. -- With Best Regards, Andy Shevchenko