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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C0461C433F5 for ; Mon, 14 Feb 2022 13:51:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234124AbiBNNvY (ORCPT ); Mon, 14 Feb 2022 08:51:24 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:33140 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230424AbiBNNvX (ORCPT ); Mon, 14 Feb 2022 08:51:23 -0500 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B55FD49FB2; Mon, 14 Feb 2022 05:51:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1644846675; x=1676382675; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=hDs9gRO/GUR9OEq0XvETsLm6kPmyTsfZT1pnOepiDE8=; b=nM9Ssa+1N5wM6xfg+/iUUuPiQq5MNIzCUto2QMza4c3xs72eU88ms1cc LeoYkCWBCx99cGHSjWUWbU0/zgN4901SvsEqyfxP3VrE3hUTzSgn2nBTH MsG84nDHmT0Gz897mXduPtru5fbOoaUOpiFQIemcwkyxTHHU6/ptQw0th 4vl63jK0Xc540c/cxHEX+YKc+Ea0yteiCkY9fzQ/ClBW9QkIbWZEjZFNM WyddtGpo3CLv/Hy7gkSKq6mvqQXoIeUoMymcGk130W+EIxp5we4mL/dME H4b6dUVNToK8b4vF0fByV8hwiXJ0s7CL/hfhb4dBAH8pOk5heVVQfJfPg A==; X-IronPort-AV: E=McAfee;i="6200,9189,10257"; a="336517448" X-IronPort-AV: E=Sophos;i="5.88,368,1635231600"; d="scan'208";a="336517448" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Feb 2022 05:51:15 -0800 X-IronPort-AV: E=Sophos;i="5.88,368,1635231600"; d="scan'208";a="624228521" Received: from unknown (HELO smile.fi.intel.com) ([10.237.72.59]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Feb 2022 05:51:13 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nJbkA-004YZT-3u; Mon, 14 Feb 2022 15:50:18 +0200 Date: Mon, 14 Feb 2022 15:50:17 +0200 From: Andy Shevchenko To: Nuno =?iso-8859-1?Q?S=E1?= Cc: "Sa, Nuno" , "linux-iio@vger.kernel.org" , "devicetree@vger.kernel.org" , Rob Herring , Jonathan Cameron , Lars-Peter Clausen , "Hennerich, Michael" Subject: Re: [PATCH v3 1/3] iio: dac: add support for ltc2688 Message-ID: References: <20220121142501.151-1-nuno.sa@analog.com> <20220121142501.151-2-nuno.sa@analog.com> <0fc9da519df96aaeb3cdcd155fb8aabbdc17fbeb.camel@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0fc9da519df96aaeb3cdcd155fb8aabbdc17fbeb.camel@gmail.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Mon, Feb 14, 2022 at 02:23:01PM +0100, Nuno Sá wrote: > On Mon, 2022-02-07 at 21:19 +0100, Nuno Sá wrote: > I would definetly like to have some settlement on the above (before > sending a v4). It kind of was discussed a bit already in [1] where I > felt we had to live with OF for this driver (that is why I kept OF in > v3. With the above, I cannot > really see how we can have device API with also including OF... If I > missing something please let me know :) Sorry for the delay, answered to your previous message. > [1]: https://lore.kernel.org/all/CAHp75VczFs8QpsY7tuB-h4X=H54nyjABA4qDSmpQ+FRYAHZdrA@mail.gmail.com/ -- With Best Regards, Andy Shevchenko