Received: by 2002:a05:7412:251c:b0:e2:908c:2ebd with SMTP id w28csp1151463rda; Mon, 23 Oct 2023 04:26:23 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFLtr2spArNWcACLMA+lLPTr5id47mYAUvLRo1hRRvJ2/0Rb60VMD9qvgjlKSA80u1Xa2qa X-Received: by 2002:a05:6358:c115:b0:168:e4ca:8eb6 with SMTP id fh21-20020a056358c11500b00168e4ca8eb6mr1324020rwb.4.1698060383267; Mon, 23 Oct 2023 04:26:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1698060383; cv=none; d=google.com; s=arc-20160816; b=Q5HcxC7TNbyM8x4loyEh4UL/jPnIKlVAcVma7YMEki0FL8SGF+fibFgLOtfSJQP6fO dbISAjJx9F/faMFlCuekRbS4jC3c0Ms+Mp9fGBBF0cpw6lkdACVhFy6ocf3Svgg1Rn5B 0F7umXv8LPZ8n6IM1GUufLARWULqyxZkfuYrNVkg6UZ8S0kisALYohQfgsLOW6F1TND/ Wl8z862MylIXznIVCxfkMVyxO2llaGlNG1qYbtDhSKZfLZOMqZp8xx3iOqV0TQ+4yTlm 6exV/n+fnJD/b3OeJ/ChjzOgc+xHyvao7uyhoT2BbSKSKAd7uwDC1FsrGFAjSyam0rbI msKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:organization:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=zRprI43txG8tPxFBPb5MQzJyGE0GQHz4O15f1G29/CY=; fh=J9P/8HttTWePP4N98uSOalHTQDXeTdNtRCDrrqCELH4=; b=VqQ7M/6EaYLFql8jAOI4Q0JRiP1kAwC78E2Ou3IQJxMBkOcNCe5FUG9yT0wuTHeYe8 2d8rfWZqk330xKkobiq7kLodylBN9lQbtGhab7FlQsmEiWlj8gtBK5VRcrrAFv7ldtjV zpImR/sxW4BkUdWJwAGdKvzIDMD2M+1gtLxWeHdL/U67FvMQLFgScXnITh6wW1L3hVmA 2O0KE2wdlA60Vo5DDG01uLzaKwGpHbITJao00AZV+STYQfi1a1fuS5UTlp4w8UWK2Qqe viproifH555H4EMDV09CHc71wGKHZNp8oqB5mcIaLg32XVG37Gh+8y8eUXz0Vbml9+WS 6vaw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="mhnoRdN/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from groat.vger.email (groat.vger.email. [2620:137:e000::3:5]) by mx.google.com with ESMTPS id w191-20020a6382c8000000b0057ab7f46381si6209922pgd.76.2023.10.23.04.26.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 23 Oct 2023 04:26:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="mhnoRdN/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id 9F9C28098FF8; Mon, 23 Oct 2023 04:26:20 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233888AbjJWLZ4 (ORCPT + 99 others); Mon, 23 Oct 2023 07:25:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37366 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233912AbjJWLZw (ORCPT ); Mon, 23 Oct 2023 07:25:52 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8278FD6; Mon, 23 Oct 2023 04:25:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1698060349; x=1729596349; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=BT1f7Iex0XAyJsTj/kj5X5QAFWs1h789Jw5nBVP3ffU=; b=mhnoRdN/aBf8lctQRtVtg5wJUHUgsValcy16ZSipHFg+Ywsarij/NiPy XlqoVZ3OXR0i5PX5khBRwcEzYruL3f2oydNzh4BN3IeetEUWSfaB8WLk/ n3RcS8i7DmZWFXUpMw1c6LrtDaiT93DRw5UGjz7n861MnwgJVeBb+txyz 0v1jRyX4crbSElCTQIGmbXFFPKcbjCmTyLDpL2ki9Ardrb0AElOys794h DEnO32tn0QZLwcRe8PLA0G3HnFSaJLR368TE3MDnYSFCgGTbR1LybNewx /FCxR6MlUUzCeDIsTwu/rnfWRmuaiZ3z5Igxsm4sObNibavjbUS8DSJTz Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10871"; a="386633174" X-IronPort-AV: E=Sophos;i="6.03,244,1694761200"; d="scan'208";a="386633174" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Oct 2023 04:25:49 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10871"; a="761714038" X-IronPort-AV: E=Sophos;i="6.03,244,1694761200"; d="scan'208";a="761714038" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga007.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Oct 2023 04:25:46 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.97-RC2) (envelope-from ) id 1qut42-00000007v9d-3saM; Mon, 23 Oct 2023 14:25:42 +0300 Date: Mon, 23 Oct 2023 14:25:42 +0300 From: Andy Shevchenko To: Angel Iglesias Cc: linux-iio@vger.kernel.org, Biju Das , linux-kernel@vger.kernel.org, Jonathan Cameron , Lars-Peter Clausen , Phil Elwell , Linus Walleij , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Subject: Re: [PATCH v2 4/5] iio: pressure: bmp280: Allow multiple chips id per family of devices Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Mon, 23 Oct 2023 04:26:20 -0700 (PDT) On Sun, Oct 22, 2023 at 07:22:20PM +0200, Angel Iglesias wrote: > Improve device detection in certain chip families known to have various > chip ids. > When no known ids match, gives a warning but follows along what device > said on the firmware and tries to configure it. I would rephrase it a bit: "Improve device detection in certain chip families known to have various chip IDs. When no ID matches, give a warning but follow along what device said on the firmware side and try to configure it." ... > + for (i = 0; i < data->chip_info->num_chip_id; i++) { > + if (chip_id == data->chip_info->chip_id[i]) { > + dev_info(dev, "0x%x is a known chip id for %s\n", chip_id, name); > + break; > + } > + dev_warn(dev, "chip id 0x%x does not match known id 0x%x\n", > + chip_id, data->chip_info->chip_id[i]); If the matching ID is not the first one, user will have an unneeded warning here. > } -- With Best Regards, Andy Shevchenko