Message ID | 20230201064717.18410-1-zajec5@gmail.com (mailing list archive) |
---|---|
Headers | show
Return-Path: <linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org> X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BFAE6C05027 for <linux-arm-kernel@archiver.kernel.org>; Wed, 1 Feb 2023 06:53:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:Cc :To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=kFx85Yr74YgK60dxFax+MxnKtkJGrJ6aueFZ07mUbeA=; b=q4x+05XQuocpAp Ko5h1m1LHaC2ivQre3IA5LcmbiI+mB2fPH80r4C+/q9H9Fm6jWKgF8j9ol9zzFUUnuQWNn39Db8NN KTXKjIRb3pVy5Mek6i20Uzp1ebElznWcYEaYiG6Hl3Mw+5pVMZKgiu5Ga3qs07er6LtLSLkRd7bpI f/dD3pehZAbTFWz2YeRBFU4+Qt9j1q2lKRAXAhsDbD0ke7jCM3raGp684Oegv8axjU7Aca7trFT52 4SkSsWK3nKcd5JwB3kXj6UyKHXanDF2ZRmMwoSk8IbO8/MS6gHDU3TsqmO0pHfyr3Z1tBMde0arnz AQCr4sJjzT/WmIcm78qw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pN6yv-00AVil-CU; Wed, 01 Feb 2023 06:52:33 +0000 Received: from mail-ej1-x62f.google.com ([2a00:1450:4864:20::62f]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pN6yr-00AVhJ-Te; Wed, 01 Feb 2023 06:52:31 +0000 Received: by mail-ej1-x62f.google.com with SMTP id gr7so23857512ejb.5; Tue, 31 Jan 2023 22:52:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=IMU0WzlJkgoGbKPFmkcXrdPY8PaQeZ4fjfOamOl8qjc=; b=a2YsEAmx/kUClgAZDcv2fVH8oN+RKJimOLk1eglv7EyoSakA3WJQparUKoKi4OaZX7 Qv3YJaJdcnuYLCSEF/tc0tERnaxKQo4ywe8UDRX0okFJ42+PkmK3fQtrWNKGJLUb8WnX D/ZJ3wfngZm0jeJUDmquRxPvqTZPKeHlgp511CJS7TsZt9db8IqdfHFsVdqTSZZw+dJF Y8EeVS4PYV4F5rb4AFh7bS1l3lNOD2Rzmy54kZZX+MjArXb9qUW2tNcF7asKIKySQRgo yUJgHDpF6CQ9FeCNSUvbbcKlDdPcbmfa5t65k80DDefOSax5MSAC04zEuHfp5ttq9CmQ nt8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=IMU0WzlJkgoGbKPFmkcXrdPY8PaQeZ4fjfOamOl8qjc=; b=bdQil6SumO1ospwg1KqGzNAZuvYF3F9pPmHCE8bUUxYhyLH/fBSa6cDGPVKP1SxHMo MW2Jxojp2NWowf6PAlk7eB2w5NGZIra1V1f19h3Zqt+QoFj9IPy3gMr73elkVX6WK7Md CFYe7jBxqrRpZLuKKHRvbVW+HXfRP5ySFPeTzRKmo4/gQ9Uoa8NDMT3YTtIB0XAzNGg6 P7rRS80D/APRXABL5EbSnV54NQ+RsLKUd3QmUujWDyOyURTiwwEY8DvYoTryea3eAu+g Fbxc02zSSueTiV+bhF2p9s9a3/RL3+CEGew9EeHQlAkfxJ6inP7ZCQNT2LC6OIYOSUNr DsDw== X-Gm-Message-State: AO0yUKVtLij/3IMqHbLon8Nr4/7QU6R3FdWLI4tip+Aq6l6mZBeruTDx wdXLUmXCGgCkudGRiBerKuo= X-Google-Smtp-Source: AK7set8jh7awTsTD0Mny29s1rpwDIwGC9gf44rtfGI0Nkha6ybhzwArAt8Ck7RlIIEly0DB/mNRoSg== X-Received: by 2002:a17:907:6d15:b0:878:7cf2:3617 with SMTP id sa21-20020a1709076d1500b008787cf23617mr1683067ejc.3.1675234344639; Tue, 31 Jan 2023 22:52:24 -0800 (PST) Received: from localhost.lan (ip-194-187-74-233.konfederacka.maverick.com.pl. [194.187.74.233]) by smtp.gmail.com with ESMTPSA id 1-20020a170906218100b008720c458bd4sm9509608eju.3.2023.01.31.22.52.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 31 Jan 2023 22:52:24 -0800 (PST) From: =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= <zajec5@gmail.com> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: Matthias Brugger <matthias.bgg@gmail.com>, Kunihiko Hayashi <hayashi.kunihiko@socionext.com>, Masami Hiramatsu <mhiramat@kernel.org>, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= <rafal@milecki.pl> Subject: [PATCH 0/4] nvmem: add and use generic MMIO NVMEM Date: Wed, 1 Feb 2023 07:47:13 +0100 Message-Id: <20230201064717.18410-1-zajec5@gmail.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230131_225229_972051_AC05B522 X-CRM114-Status: GOOD ( 11.42 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: <linux-arm-kernel.lists.infradead.org> List-Unsubscribe: <http://lists.infradead.org/mailman/options/linux-arm-kernel>, <mailto:linux-arm-kernel-request@lists.infradead.org?subject=unsubscribe> List-Archive: <http://lists.infradead.org/pipermail/linux-arm-kernel/> List-Post: <mailto:linux-arm-kernel@lists.infradead.org> List-Help: <mailto:linux-arm-kernel-request@lists.infradead.org?subject=help> List-Subscribe: <http://lists.infradead.org/mailman/listinfo/linux-arm-kernel>, <mailto:linux-arm-kernel-request@lists.infradead.org?subject=subscribe> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: "linux-arm-kernel" <linux-arm-kernel-bounces@lists.infradead.org> Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org |
Series |
nvmem: add and use generic MMIO NVMEM
|
expand
|
On 1.02.2023 07:47, Rafał Miłecki wrote: > From: Rafał Miłecki <rafal@milecki.pl> > > MMIO accessible NVMEM devices should be simple enough to allow using a > single binding & driver for them. > > I already replaced two existing drivers. With NVMEM layouts introduced I > can also replace Broadcom's NVRAM driver but that work depends on my > pending U-Boot patchset (it provides required helpers). This was meant to be marked as V2. Changes: 1. Replaced io with mmio to be clear 2. Replaced 2 existing drivers with generic implementation
From: Rafał Miłecki <rafal@milecki.pl> MMIO accessible NVMEM devices should be simple enough to allow using a single binding & driver for them. I already replaced two existing drivers. With NVMEM layouts introduced I can also replace Broadcom's NVRAM driver but that work depends on my pending U-Boot patchset (it provides required helpers). Rafał Miłecki (4): dt-bindings: nvmem: mmio: new binding for MMIO accessible NVMEM devices nvmem: add generic driver for devices with MMIO access nvmem: mtk-efuse: replace driver with a generic MMIO one nvmem: uniphier-efuse: replace driver with a generic MMIO one .../devicetree/bindings/nvmem/mmio.yaml | 46 +++++++++ drivers/nvmem/Kconfig | 24 +++-- drivers/nvmem/Makefile | 6 +- drivers/nvmem/mmio.c | 84 ++++++++++++++++ drivers/nvmem/mtk-efuse.c | 97 ------------------- drivers/nvmem/uniphier-efuse.c | 78 --------------- 6 files changed, 148 insertions(+), 187 deletions(-) create mode 100644 Documentation/devicetree/bindings/nvmem/mmio.yaml create mode 100644 drivers/nvmem/mmio.c delete mode 100644 drivers/nvmem/mtk-efuse.c delete mode 100644 drivers/nvmem/uniphier-efuse.c