From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Fainelli Subject: Re: [PATCH v5] mmc: OCTEON: Add host driver for OCTEON MMC controller Date: Wed, 10 Feb 2016 18:55:55 -0800 Message-ID: <56BBF83B.8020908@gmail.com> References: <1455125775-7245-1-git-send-email-matt.redfearn@imgtec.com> <56BB7B2F.60307@caviumnetworks.com> <20160210234907.GC1640@darkstar.musicnaut.iki.fi> <56BBD6AD.2090902@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <56BBD6AD.2090902@caviumnetworks.com> Sender: linux-kernel-owner@vger.kernel.org To: David Daney , Aaro Koskinen Cc: Matt Redfearn , linux-mmc@vger.kernel.org, david.daney@cavium.com, ulf.hansson@linaro.org, linux-mips@linux-mips.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Zubair.Kakakhel@imgtec.com, Aleksey Makarov , Chandrakala Chavva , Aleksey Makarov , Leonid Rosenboim , Peter Swain , Aaron Williams List-Id: linux-mmc@vger.kernel.org Le 10/02/2016 16:32, David Daney a =C3=A9crit : > On 02/10/2016 03:49 PM, Aaro Koskinen wrote: >> Hi, >> >> On Wed, Feb 10, 2016 at 10:02:23AM -0800, David Daney wrote: >>> On 02/10/2016 09:36 AM, Matt Redfearn wrote: >>>> + pr_warn(FW_WARN "%s: Legacy property '%s'. Please remove\= n", >>>> + node->full_name, legacy_name); >>> >>> I don't like this warning message. >>> >>> The vast majority of people that see it will not be able to change = their >>> firmware. So it will be forever cluttering up their boot logs. >> >> Until they switch to use APPENDED_DTB. :-) >> >=20 > I am philosophically opposed to making the DTB an internal kernel > implementation detail. >=20 > For OCTEON boards, it is an ABI between the boot firmware and the > kernel, and is impractical to change. >=20 > One could argue that many years ago, when the decision was made (by m= e), > that we should have opted to carry in the kernel source code tree the > DTS files for all OCTEON boards ever made, but we did not do that. D= ue > to the non-reversibility of time, the decision is hard to reverse. >=20 > In the case of this MMC driver, the only real difference is that two > properties have legacy names that later had differing "official" name= s. > The overhead of carrying the legacy bindings is very low. Since there is an existing FDT patching infrastructure in arch/mips/cavium-octeon/ would not that be a place where you could put an adaptation layer between your legacy firmware properties and the upstream binding? --=20 =46lorian