[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87tw63i2s7.fsf@kamboji.qca.qualcomm.com>
Date: Wed, 5 Apr 2017 10:09:44 +0000
From: Kalle Valo <kvalo@....qualcomm.com>
To: Alban <albeu@...e.fr>
CC: ath9k-devel <ath9k-devel@....qualcomm.com>,
John Crispin <john@...ozen.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/7] Documentation: dt: net: Update the ath9k binding for
SoC devices
Alban <albeu@...e.fr> writes:
> The current binding only cover PCI devices so extend it for SoC devices.
>
> Most SoC platforms use an MTD partition for the calibration data
> instead of an EEPROM. The qca,no-eeprom property was added to allow
> loading the EEPROM content using firmware loading. This new binding
> replace this hack with NVMEM cells, so we also mark the qca,no-eeprom
> property as deprecated in case anyone ever used it.
A patchset like this should definitely have a cover letter and explain
the backround and reasoning for this patchset. Currently I'm just
guessing.
> Signed-off-by: Alban <albeu@...e.fr>
Please use your full name both in From and S-o-b lines.
--
Kalle Valo
Powered by blists - more mailing lists