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 1FDB3C433FE for ; Mon, 7 Nov 2022 10:38:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229979AbiKGKix (ORCPT ); Mon, 7 Nov 2022 05:38:53 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47120 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231421AbiKGKiv (ORCPT ); Mon, 7 Nov 2022 05:38:51 -0500 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E9A77F59; Mon, 7 Nov 2022 02:38:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1667817530; x=1699353530; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=D68k+70AbtJNumRWp6LgrGl/TGfcgO3I3DFP2CNfipI=; b=BDVm/e0yIHVH5VOnTealylWAAKkQrJAQbB/jq/y0ocd55jaOBtVjq+wM +xeFxej4G2RIeYuq1q9WPc85LYvodjjfVBBSOekut7Dx6XsX1PfK+Jr0G G43n5g4G6bPxi55lrMveogc088hvyGtYL0AnHA6pX2xRLG3Rm4SXqS9em DHWk8ubtsVrRJJu5FXn4btpT7LzDYCUt7pHph6Ro3esd0HleO8f7RAmND 09gjVa0NODN2HX/ybwIOEQa1JjL4u3TJSt49eLY+TMQT2Cg6Gz/y2uCu6 vKWawDMgaRt22FDikLyWCtRrBwwdjXuiru1bjtgCv8UAsDpzlsFIC0wrO w==; X-IronPort-AV: E=McAfee;i="6500,9779,10523"; a="309090680" X-IronPort-AV: E=Sophos;i="5.96,143,1665471600"; d="scan'208";a="309090680" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Nov 2022 02:38:50 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10523"; a="704824002" X-IronPort-AV: E=Sophos;i="5.96,143,1665471600"; d="scan'208";a="704824002" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga004.fm.intel.com with ESMTP; 07 Nov 2022 02:38:49 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1orzWh-008ax9-3A; Mon, 07 Nov 2022 12:38:47 +0200 Date: Mon, 7 Nov 2022 12:38:47 +0200 From: Andy Shevchenko To: William Breathitt Gray Cc: linus.walleij@linaro.org, brgl@bgdev.pl, linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] gpio: 104-dio-48e: Migrate to regmap API Message-ID: References: <523cfe2bfbf804e64e8c9f6ed38339e850e6d9d9.1667472555.git.william.gray@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <523cfe2bfbf804e64e8c9f6ed38339e850e6d9d9.1667472555.git.william.gray@linaro.org> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Thu, Nov 03, 2022 at 07:20:47AM -0400, William Breathitt Gray wrote: > The regmap API supports IO port accessors so we can take advantage of > regmap abstractions rather than handling access to the device registers > directly in the driver. I'm wondering if gpio-regmap can be used for these... -- With Best Regards, Andy Shevchenko