Received: by 2002:a25:2c96:0:0:0:0:0 with SMTP id s144csp137679ybs; Tue, 26 May 2020 05:42:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxhkutXb5oWHHXGUKb3jSwU9G9SJdgdo+PW3Lq0jjLpHcABeUlSdc0jRoPEXa5LTBSmOuGA X-Received: by 2002:a17:906:6891:: with SMTP id n17mr927641ejr.338.1590496922297; Tue, 26 May 2020 05:42:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590496922; cv=none; d=google.com; s=arc-20160816; b=szewfxlhLhFm1jQOrpXn/afwHNQat51SAdHFI7WgbAg6IIeHFOKz/74e5yVoBTMOQM 6gTVC1NMEfp1//RUptqWCNe3SM+njd/1D1PG1gth67YrsFix2lUwxWanTRurc8OOgAPN FSObdBANg2CNLF35Kn1qP71+R2ydps1Eo3d9DM1vzyaXhdNFfuQiLJSdsGIvPZB7ML4u uofgluoVzKS44EY8AHmmZg10Za5wvGn0yIN4yIgr6okidzEDXtWcB8tZk1GAocQ9kanv gMfhSNhCEhWaBXV2KzWPDWSr2LlZQ56NiuqAJ4ZCDOuDF9lwm3RMSBbLCyPobqAGx8Uc jGgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:mail-followup-to:message-id:subject:cc:to :from:date:dkim-signature; bh=C8k53DjjYyfSex56lDdOYubcmmBBqtjkh1SjIKFK07M=; b=FczARJErc7Lp1fZvsULc0eMsqDoKjyCSRwvjI+TXNnYZf1wuV27nsccIMwFPqJnRMZ PigAwZ0Bc8izANktXMxt7Q6B0m8tSSLhYfPusmF2DMenHAbnl6pevws2XeO9KFx2yPIB DHkxbeeVAgHyGhxANsphNBMMmWIEpfkjsM266CryoIOuP+elHDgsfGt3MT0fI38gYSHx h1sEK2rXgckdUrU5Hl5yTx3GDVoISueV/EqOo43b1hJZPdosbMgKJQRe0ZvVZXQmjmdC 8d/wKNNXXj0RXBKAIdoawIDKX/LUMXKW7npIXknm4hUR4Ybaln+vw+zMI1LYO8CgfG1Y ddog== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@st.com header.s=STMicroelectronics header.b=TJa7J+KA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=st.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v28si808545edd.233.2020.05.26.05.41.38; Tue, 26 May 2020 05:42:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@st.com header.s=STMicroelectronics header.b=TJa7J+KA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=st.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731920AbgEZKj4 (ORCPT + 99 others); Tue, 26 May 2020 06:39:56 -0400 Received: from mx07-00178001.pphosted.com ([62.209.51.94]:58439 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731907AbgEZKjx (ORCPT ); Tue, 26 May 2020 06:39:53 -0400 Received: from pps.filterd (m0046037.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 04QAc29I022072; Tue, 26 May 2020 12:39:40 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=st.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=STMicroelectronics; bh=C8k53DjjYyfSex56lDdOYubcmmBBqtjkh1SjIKFK07M=; b=TJa7J+KAtCbOnxiZK8u+N6QqtUgLtfQvtNkevPschMh1XJjFhH8jP552iBQXXguttwQh z3w80ac8qN4sp+TpakM9FxdyUhhRplARc6bqFemUdyeet+YozLGN+j6fLWSjU1zjLybG TI+GIi4nfOW98MmUuiLAwIZI9dwUTAQf5fRzNfMhqezE6D9U5tpJjdihzwQ8HkA3+e5y dqmtRyZKYc2eJ+7ehnq1PVI/44JJhoaIt4Iuqd5HSrWOISTNrDI5bAtEzrDpXAD+eyps FX3ZiJqBU16syzJTWse7QPXLIZGe/UDh6Xgq6GGy5SqQ802IJN07pc5bhY0nhR/lop5O Kw== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com with ESMTP id 316skw75hc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 26 May 2020 12:39:40 +0200 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 4FD7710002A; Tue, 26 May 2020 12:39:40 +0200 (CEST) Received: from Webmail-eu.st.com (sfhdag3node2.st.com [10.75.127.8]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 399452A705A; Tue, 26 May 2020 12:39:40 +0200 (CEST) Received: from gnbcxd0016.gnb.st.com (10.75.127.46) by SFHDAG3NODE2.st.com (10.75.127.8) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 26 May 2020 12:39:39 +0200 Date: Tue, 26 May 2020 12:39:38 +0200 From: Alain Volmat To: Wolfram Sang CC: Benjamin Tissoires , , , , , , , , , , , Subject: Re: [PATCH 4/4] i2c: stm32f7: Add SMBus-specific protocols support Message-ID: <20200526103938.GC14423@gnbcxd0016.gnb.st.com> Mail-Followup-To: Wolfram Sang , Benjamin Tissoires , robh+dt@kernel.org, mark.rutland@arm.com, pierre-yves.mordret@st.com, mcoquelin.stm32@gmail.com, alexandre.torgue@st.com, linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, fabrice.gasnier@st.com References: <1588657871-14747-1-git-send-email-alain.volmat@st.com> <1588657871-14747-5-git-send-email-alain.volmat@st.com> <20200523110140.GD3459@ninjato> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20200523110140.GD3459@ninjato> X-Disclaimer: ce message est personnel / this message is private X-Originating-IP: [10.75.127.46] X-ClientProxiedBy: SFHDAG7NODE3.st.com (10.75.127.21) To SFHDAG3NODE2.st.com (10.75.127.8) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216,18.0.687 definitions=2020-05-26_01:2020-05-26,2020-05-26 signatures=0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, May 23, 2020 at 01:01:40PM +0200, Wolfram Sang wrote: > > > +static int stm32f7_i2c_reg_client(struct i2c_client *client) > > +{ > > + struct stm32f7_i2c_dev *i2c_dev = i2c_get_adapdata(client->adapter); > > + int ret; > > + > > + if (client->flags & I2C_CLIENT_HOST_NOTIFY) { > > + /* Only enable on the first device registration */ > > + if (atomic_inc_return(&i2c_dev->host_notify_cnt) == 1) { > > + ret = stm32f7_i2c_enable_smbus_host(i2c_dev); > > + if (ret) { > > + dev_err(i2c_dev->dev, > > + "failed to enable SMBus host notify (%d)\n", > > + ret); > > + return ret; > > + } > > + } > > + } > > + > > + return 0; > > +} > > So, as mentioned in the other review, I'd like to evaluate other > possibilities for the above: > > - One option is to enable it globally in probe(). Then you lose the > possibility to have a device at address 0x08. I'd prefer avoid this solution to not lose the address 0x08. > - Enable it in probe() only if there is a generic binding "host-notify". Do you mean having the adapter walk through childs node and see if at least one of them have the host-notify property ? This mean that such solution wouldn't work for device relying on platform data rather than DT nodes. > - Let the core scan for a device with HOST_NOTIFY when registering an > adapter and then call back into the driver somehow? You mean at adapter registration time only ? Not device probing time ? At probing time, we could have the core (i2c_device_probe) check for the flag HOST_NOTIFY and if setted call a dedicated host-notify reg callback ? > > Other ideas? >