From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751210AbdAQDhX (ORCPT ); Mon, 16 Jan 2017 22:37:23 -0500 Received: from mail.free-electrons.com ([62.4.15.54]:39502 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751104AbdAQDhT (ORCPT ); Mon, 16 Jan 2017 22:37:19 -0500 Date: Tue, 17 Jan 2017 14:36:50 +1100 From: Thomas Petazzoni To: Boris Brezillon Cc: Marek Vasut , Rob Herring , Mark Rutland , devicetree@vger.kernel.org, Guochun Mao , Richard Weinberger , Russell King , linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, Matthias Brugger , linux-mediatek@lists.infradead.org, Cyrille Pitchen , Brian Norris , David Woodhouse , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v1 2/2] arm: dts: mt2701: add nor flash node Message-ID: <20170117143650.5db87148@free-electrons.com> In-Reply-To: <20170116094032.6f471f11@bbrezillon> References: <1484291609-20195-1-git-send-email-guochun.mao@mediatek.com> <1484291609-20195-3-git-send-email-guochun.mao@mediatek.com> <20170113151747.6bc85245@bbrezillon> <20170113172825.75d545a3@bbrezillon> <86c997be-f500-eaa1-3ba5-d21cff6223b7@gmail.com> <20170113175628.1793f433@bbrezillon> <0fafcd8d-cf99-de6b-728f-5e3637810b68@gmail.com> <20170114092958.022f2fc8@bbrezillon> <20170116094032.6f471f11@bbrezillon> Organization: Free Electrons X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, (Side note: you guys should learn about stripping irrelevant parts of an e-mail when replying!) On Mon, 16 Jan 2017 09:40:32 +0100, Boris Brezillon wrote: > > Well this is OK I guess, but then you can also use "mediatek,mt8173-nor" > > as the oldest supported compatible and be done with it, no ? It looks a > > bit crappy though, I admit that ... > > Let's stop bikeshedding and wait for DT maintainers feedback > before taking a decision ;-). > > Rob, Mark, any opinion? I agree that a clarification would be good. There are really two options: 1. Have two compatible strings in the DT, the one that matches the exact SoC where the IP is found (first compatible string) and the one that matches some other SoC where the same IP is found (second compatible string). Originally, Linux only supports the second compatible string in its device driver, but if it happens that a difference is found between two IPs that we thought were the same, we can add support for the first compatible string in the driver, with a slightly different behavior. 2. Have a single compatible string in the DT, matching the exact SoC where the IP is found. This involves adding immediately this compatible string in the corresponding driver. I've not really been able to figure out which of the two options is the most future-proof/appropriate. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com