From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kalle Valo Subject: Re: [PATCH 1/7] Documentation: dt: net: Update the ath9k binding for SoC devices Date: Wed, 5 Apr 2017 10:09:44 +0000 Message-ID: <87tw63i2s7.fsf@kamboji.qca.qualcomm.com> References: <1489439116-4233-1-git-send-email-albeu@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1489439116-4233-1-git-send-email-albeu@free.fr> (Alban's message of "Mon, 13 Mar 2017 22:05:09 +0100") Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Alban Cc: ath9k-devel , John Crispin , Rob Herring , Mark Rutland , "linux-wireless@vger.kernel.org" , "netdev@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" List-Id: devicetree@vger.kernel.org Alban 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 Please use your full name both in From and S-o-b lines. --=20 Kalle Valo=