R: [PATCH 2/2] dt: bindings: ath10k: Document qcom, ath10k-pre-calibration-data-mtd
Date: Fri Sep 18 2020 - 14:09:04 EST
> -----Messaggio originale-----
> Da: Christian Lamparter <chunkeey@xxxxxxxxx>
> Inviato: venerdì 18 settembre 2020 18:54
> A: Ansuel Smith <ansuelsmth@xxxxxxxxx>; Kalle Valo
> Cc: devicetree@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; linux-
> wireless@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
> ath10k@xxxxxxxxxxxxxxxxxxx; David S. Miller <davem@xxxxxxxxxxxxx>; Rob
> Herring <robh+dt@xxxxxxxxxx>; Jakub Kicinski <kuba@xxxxxxxxxx>; linux-
> mtd@xxxxxxxxxxxxxxxxxxx; Srinivas Kandagatla
> <srinivas.kandagatla@xxxxxxxxxx>; Bartosz Golaszewski
> Oggetto: Re: [PATCH 2/2] dt: bindings: ath10k: Document qcom, ath10k-
> 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@xxxxxxxxx>
> 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?
Can you give me some example where this is used? I can't find any reference.