Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2101016yba; Mon, 15 Apr 2019 05:05:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqwjJGypMruow0k/52z1WW+kv0pg7MSYE4XMcl4zd1VZINedgl6gTKJkXEtbHuiFFWzsLkJ1 X-Received: by 2002:a63:1d45:: with SMTP id d5mr48112847pgm.184.1555329945969; Mon, 15 Apr 2019 05:05:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555329945; cv=none; d=google.com; s=arc-20160816; b=dBRohkc49UzgJhIooLDXK/2bt/v01oWgjByvSL/SGjCriRTnp5VQvq7hDTCTChjJoc SxzMR0gmsF5AJrddsmw9cyZ35hTrHMkz2VZ2OZ7HnN33ledYEdMoFIKmVFGHkbXJGZUB TqUJDQs3lVXMTmR6Gp/yaA3DsoYEPTyF1YvDeEglsKuWc2u58pcT80R4g3+b7v1WXNi9 5cEM66oDhyyUCYLDvmrQ4QNoeM/FTW66x/TF8e6n9xURxYmJv31w25T2KebsHohNcFQA 6JZtUROOAxN2NLPnNRW9QiN1h6XoNJNItXqdqHpcaUDldJdapGs6y+mFNUGWLQALgALv 4uRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=3xLoLmscGfkNKEZ7aTcUOT2ZJYYQ/RJc7tCQzYBljrM=; b=jmGFddf4qJ0RvjeqFx53CBWhVqH4QKNnpvjoSxcdxVApP6Ke3z9DRQG0U85F41CFXT cCQ0B6k80KOiTNski+wusgDtfLSbFfcZvm33SWL6bk00gOq/F6JZ74h01OEceV2gy3jD x3U3gDD3iHMn0f5VAIcbhmJOWOaNEnmK3Dc3CKSD8khvgL0dfU1E3KuydsuQ3kh/76yq yMRDrZLAx05FX1cjEeMcYuqm6dkDrh6QDzGxxjS4GZnlXaGV8xQn6s8QsblDJW6eGwBB PydCgr4REZXdmU42B2N3/B7xARzBt3q0rRRlHqSHf+ijLVD5wJg8Q+86iaLdYXhwPBQJ wg9g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j133si45199567pgc.543.2019.04.15.05.05.29; Mon, 15 Apr 2019 05:05:45 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727337AbfDOMEo (ORCPT + 99 others); Mon, 15 Apr 2019 08:04:44 -0400 Received: from sauhun.de ([88.99.104.3]:41120 "EHLO pokefinder.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725994AbfDOMEo (ORCPT ); Mon, 15 Apr 2019 08:04:44 -0400 Received: from localhost (p54B331F8.dip0.t-ipconnect.de [84.179.49.248]) by pokefinder.org (Postfix) with ESMTPSA id 9A7942C0114; Mon, 15 Apr 2019 14:04:41 +0200 (CEST) Date: Mon, 15 Apr 2019 14:04:41 +0200 From: Wolfram Sang To: Peter Rosin Cc: Wolfram Sang , "linux-i2c@vger.kernel.org" , "linux-renesas-soc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Stefan Lengfeld , "linux-omap@vger.kernel.org" , "linux-tegra@vger.kernel.org" , Linus Walleij , Andy Shevchenko Subject: Re: [PATCH 04/12] i2c: mux: populate the new *_atomic callbacks Message-ID: <20190415120441.ka65mytvxsuzul4v@ninjato> References: <20190403124019.8947-1-wsa+renesas@sang-engineering.com> <20190403124019.8947-5-wsa+renesas@sang-engineering.com> <59d32414-3859-d614-dc41-cc0a1bc63301@axentia.se> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lhxkp6eumrz5hzmr" Content-Disposition: inline In-Reply-To: <59d32414-3859-d614-dc41-cc0a1bc63301@axentia.se> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --lhxkp6eumrz5hzmr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > I guess the question is if it is allowed to have .master_xfer_atomic > but not .master_xfer (and similarly for .smbus_xfer{,_atomic})? Maybe > that decision should be made explicit? And perhaps enforced? xfer_atomic callbacks are optional. One xfer callback is mandatory. I did a check for falling back to master_xfer_atomic if there is no suitable smbus_xfer_atomic. I will think about the vice-versa case you mentioned. Yet, this is indeed a super corner case, so I prefer to fix this incrementally. > I don't care deeply about the above though, so feel free to do > something about it, or >=20 > Reviewed-by: Peter Rosin Thanks for the review! --lhxkp6eumrz5hzmr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAly0c1kACgkQFA3kzBSg KbY5og//XeihKLEc7DDv97Bd8+50Rbfgz2b1tUDb5iCLL0Ttpw1Kx/NFjesHZN2I saEndxnDFct6Pb9ygV/yYRkKckqIUXzG5DMp/bDhUw+aFeSwSn6nPhSSSU1hsXG3 yHhSJhKPb3oFr+hQhdZ8dz9skH6NhdZggxQ1pFcCeTOvZ9DcJllm3dxLqZWnGNxk +F1lyDyJBHyUWa2OzuMi908/nTR5DWPIy3rTUKYAq2teWyHMok3KR8v8FW8EsqTa AffUcR1KV9JgVVAm79S1J1H+3IOLtt6Arh9GXvwkgiiJqvXtiygTQbA6rgTPYi9K ZHKh3fv+T6wtOfSAPXSWacGz8k8NJoTsT64ge+IDNIV769/H7W6GgVGa8ScjEWYh zPjEV/P8lkfI8HQ1mbcFZebFLIhdg6ki1z4TVq4HADwbgoT3uZdYwzhgnlAO7uGm iWe9+rLUm1YXl9k5pOLpZYHkhvy2d/Rsm0WOMuQLXTDXP8yjMD+tWJcHKPy0rqDG LV1Eqo18K+FXwBYu4hFKhblVMOtkFeDI7rk90e+BDOiN6FMOqGNoo8PslcT1T9Qe Lv+ZJo3bjhHgJiZJsCtzZJD/JsopOptF7zEK7zh4j8TSgyWD1BPBgg80IRdwVKnF QKUYvkby2DOPx8dFWrfLxzC5EHsWtPaHq2NibN5HlMcBRB4WYlk= =lPUY -----END PGP SIGNATURE----- --lhxkp6eumrz5hzmr--