Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp1520702pxb; Sun, 11 Apr 2021 23:10:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzCNMZ8Zie7CieVLiakbJpIi0twhlCEyT1G31Ndp2twajt4XIV0lbmDRSibM6YcF1c02NMu X-Received: by 2002:aa7:d445:: with SMTP id q5mr28528239edr.318.1618207839133; Sun, 11 Apr 2021 23:10:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618207839; cv=none; d=google.com; s=arc-20160816; b=wcx9Lcrez5LfvGiEQno4F09aSlZo/xH8ucySPzFy8g2A/vktKQvUIiOr/H9e+0IHj3 cF9Eej+PDpPYm5PxM1Q8UbxBWqwXLktaGbg3Wyddc9f97O3iDJQz67Iv1EMESYKhmA5G YpLYmh46rqjUdLIbLodFTK61mgvGwxoFGjovNmxRI2R1uQ98cFQfjcR2tOsWEzwhl/6q YW+8FJ0Wcp90bemuE4LSqDlCG8xMYHNq79IuSTUoAOJZkmASLZwIYU4KTmXiGMnOaopd /kjM3I4XafrZWQnl5MMdz074jteqrUjiLZq2KmgEmbL4Lf5veWtgtEXH5QIpth5wauwG mtVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=X9RoBg67BHVjKCImXrORY9bFHDFbk9sL1L46WpmLp7Y=; b=kYqZ/jGQGNrNllZCrqlyUt22Qx+QvqhbDTtTGa90+HvoTH/nvyP1djy9Y4QZscvin0 UyQiAkrOMPzn4ETtpCMIImYUgOYl+UABtHQPkJO4zKqDfCO3pE4vYqFUV5WtRW3ZD4QL PGOmK8lM/BXckUH5dUUngsHQB7IkESF/zvtrFzApRE5QcSRdh7zwsaVOBY0IJv0miJrl awmWRJiUf+us6cUaPUEgoBIhvWTk+l8FgwmuHaHuD9NSTOa05gNAy4YxpNsV7RaFTXnd wnQtV59uQ23TU9wbyB3AG0T0mIOgczInfDLxaoGK26LOqrrl7SBHvruzpks2e0YD2OZD Y+Uw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hw7si3724136ejc.417.2021.04.11.23.10.16; Sun, 11 Apr 2021 23:10:39 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230368AbhDLGHN (ORCPT + 99 others); Mon, 12 Apr 2021 02:07:13 -0400 Received: from router.aksignal.cz ([62.44.4.214]:59200 "EHLO router.aksignal.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229448AbhDLGHN (ORCPT ); Mon, 12 Apr 2021 02:07:13 -0400 Received: from localhost (localhost [127.0.0.1]) by router.aksignal.cz (Postfix) with ESMTP id A8FA04307A; Mon, 12 Apr 2021 08:06:53 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at router.aksignal.cz Received: from router.aksignal.cz ([127.0.0.1]) by localhost (router.aksignal.cz [127.0.0.1]) (amavisd-new, port 10026) with LMTP id Y9rT_o_lsjxK; Mon, 12 Apr 2021 08:06:53 +0200 (CEST) Received: from [172.25.161.36] (unknown [83.240.30.185]) (Authenticated sender: jiri.prchal@aksignal.cz) by router.aksignal.cz (Postfix) with ESMTPSA id 01FE843079; Mon, 12 Apr 2021 08:06:52 +0200 (CEST) Subject: Re: [PATCH 0/3] nvmem: eeprom: add support for FRAM To: Christian Eggers , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Rob Herring References: <20210409154720.130902-1-jiri.prchal@aksignal.cz> <4311739.LvFx2qVVIh@n95hx1g2> From: =?UTF-8?B?SmnFmcOtIFByY2hhbA==?= Message-ID: <5624cedb-e9e2-d1c3-2fb3-b03f7fe51a99@aksignal.cz> Date: Mon, 12 Apr 2021 08:06:52 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <4311739.LvFx2qVVIh@n95hx1g2> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09. 04. 21 19:21, Christian Eggers wrote: > Hi Jiri, > > I have two Fujitsu different FRAMs running with the stock at25 driver. I set > the page size equal to the device size (as FRAMs have no pages). > > Are you able to run your FRAM with the unmodified driver? > > I assume that getting the device geometry from the chip is vendor specific (in > contrast to flash devices which have standard commands for this). I suppose > that there is no much value getting vendor specific information from a chip. If > the drivers knows the vendor, it should also know the chip (e.g. from the dt). Hi Christian, main purpose of this patch is to get serial number from this chip. I don't have it done yet, in older kernels I expose it as separate file in sysfs, but in this kernel no luck. So a post first things while I'm working on sernum exposing. Does your chip has serial number? Can you read it? Any help welcomed. Thanks Jiri PS: If standard EEPROMs has some commands to get size etc., why it's not used? I guess that size is increased as time goes while board is still the same, so isn't it annoying changing dt every new lot with bigger eeproms.