[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8f886e3d-e2ee-cbf8-a676-28ebed4977aa@gmail.com>
Date: Fri, 18 Sep 2020 18:53:35 +0200
From: Christian Lamparter <chunkeey@...il.com>
To: Ansuel Smith <ansuelsmth@...il.com>,
Kalle Valo <kvalo@...eaurora.org>
Cc: devicetree@...r.kernel.org, netdev@...r.kernel.org,
linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
ath10k@...ts.infradead.org,
"David S. Miller" <davem@...emloft.net>,
Rob Herring <robh+dt@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
linux-mtd@...ts.infradead.org,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [PATCH 2/2] dt: bindings: ath10k: Document qcom,
ath10k-pre-calibration-data-mtd
On 2020-09-18 18:29, Ansuel Smith wrote:
> Document use of qcom,ath10k-pre-calibration-data-mtd bindings used to
> define from where the driver will load the pre-cal data in the defined
> mtd partition.
>
> Signed-off-by: Ansuel Smith <ansuelsmth@...il.com>
Q: Doesn't mtd now come with nvmem support from the get go? So
the MAC-Addresses and pre-caldata could be specified as a
nvmem-node in the devicetree? I remember seeing that this was
worked on or was this mtd->nvmem dropped?
Cheers,
Christian
Powered by blists - more mailing lists