Messages in this thread | | | From | <> | Subject | R: [PATCH 2/2] dt: bindings: ath10k: Document qcom, ath10k-pre-calibration-data-mtd | Date | Fri, 18 Sep 2020 20:08:55 +0200 |
| |
> -----Messaggio originale----- > Da: Christian Lamparter <chunkeey@gmail.com> > Inviato: venerdì 18 settembre 2020 18:54 > A: Ansuel Smith <ansuelsmth@gmail.com>; Kalle Valo > <kvalo@codeaurora.org> > Cc: devicetree@vger.kernel.org; netdev@vger.kernel.org; linux- > wireless@vger.kernel.org; linux-kernel@vger.kernel.org; > ath10k@lists.infradead.org; David S. Miller <davem@davemloft.net>; Rob > Herring <robh+dt@kernel.org>; Jakub Kicinski <kuba@kernel.org>; linux- > mtd@lists.infradead.org; Srinivas Kandagatla > <srinivas.kandagatla@linaro.org>; Bartosz Golaszewski > <bgolaszewski@baylibre.com> > Oggetto: 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@gmail.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
Can you give me some example where this is used? I can't find any reference.
| |