devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Guochun Mao <guochun.mao@mediatek.com>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Cyrille Pitchen <cyrille.pitchen@atmel.com>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Richard Weinberger <richard@nod.at>,
	Russell King <linux@armlinux.org.uk>,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	linux-mtd@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	David Woodhouse <dwmw2@infradead.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: mtd: add new compatible strings for mtk nor controller
Date: Thu, 3 Aug 2017 12:09:44 +0200	[thread overview]
Message-ID: <0796f86e-044b-5891-e56e-c96242611608@gmail.com> (raw)
In-Reply-To: <1501726602.4381.23.camel@mhfsdcap03>



On 08/03/2017 04:16 AM, Guochun Mao wrote:
> Hi Cyrille,
> 
> On Wed, 2017-08-02 at 17:31 +0200, Cyrille Pitchen wrote:
>> Hi Guochun,
>>
>> Le 02/08/2017 à 10:36, Boris Brezillon a écrit :
>>> Hi Matthias,
>>>
>>> On Tue, 1 Aug 2017 14:33:22 +0200
>>> Matthias Brugger <matthias.bgg@gmail.com> wrote:
>>>
>>>> On 07/25/2017 04:10 AM, Guochun Mao wrote:
>>>>> Add "mediatek,mt2712-nor" and "mediatek,mt7622-nor"
>>>>> for nor flash node's compatible strings.
>>>>>
>>>>> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
>>>>> Signed-off-by: Guochun Mao <guochun.mao@mediatek.com>
>>>>> ---
>>>>>    .../devicetree/bindings/mtd/mtk-quadspi.txt        |    2 ++
>>>>>    1 file changed, 2 insertions(+)
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt b/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt
>>>>> index 5ded66a..9845ff4 100644
>>>>> --- a/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt
>>>>> +++ b/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt
>>>>> @@ -3,6 +3,8 @@
>>>>>    Required properties:
>>>>>    - compatible: 	  The possible values are:
>>>>>    		  "mediatek,mt2701-nor"
>>>>> +		  "mediatek,mt2712-nor"
>>>>> +		  "mediatek,mt7622-nor"
>>>>>    		  "mediatek,mt7623-nor"
>>>>>    		  "mediatek,mt8173-nor"
>>>>>    		  For mt8173, compatible should be "mediatek,mt8173-nor".
>>>>>
>>
>> There should be another patch to update the mtk_nor_of_ids[] array in
>> the mtk-quadspi.c driver, shouldn't it?
>>
>> Currently, I only see the "mediatek,mt8173-nor" compatible string at the
>> driver side. The driver and its documentation should be aligned and both
>> patches should be applied at the same time.
> 
>> Best regards,
>>
>> Cyrille
> 
> 
>  From my designer's info, these IPs' nor controller could use same
> driver, and I had verified it. I think there's no need to update
> mtk_nor_of_ids[], unless we find difference between these IPs(exactly
> compared with mt8173).
> How do you think?
>


Right, mt8173-nor is the fallback binding which will be used by the driver. As 
the documentation states, the compatible string should be something like:
"mediatek,mt7622-nor", "mediatek,mt8173-nor"

So the mt7622-nor binding is not matched in the driver, as the driver is the 
same on all SoCs. Nonetheless if we realize in the future that mt7622 IP has 
some special feature/bug, we can use the binding to implement that in the driver.

AFAIK this is the standard way for bindings. Cyrille, is this ok for you, or do 
want all bindings to be reflected in the driver even though they don't change 
any functionality?

Regards,
Matthias

> And, we will add dts patches for new SOCs, are these patches should
> applied with this documentation?
> 
> Best regards,
> Guochun
> 

  reply	other threads:[~2017-08-03 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25  2:10 [PATCH v4 1/1] add new compatible strings for mtk nor controller Guochun Mao
     [not found] ` <1500948617-19627-1-git-send-email-guochun.mao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-07-25  2:10   ` [PATCH] dt-bindings: mtd: " Guochun Mao
     [not found]     ` <1500948617-19627-2-git-send-email-guochun.mao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-08-01 12:33       ` Matthias Brugger
     [not found]         ` <03016ea3-51ad-0b2d-e824-0a20913bd7c1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-02  8:36           ` Boris Brezillon
2017-08-02 15:31             ` Cyrille Pitchen
     [not found]               ` <535cc2d5-7bc9-2cb7-42cf-9d7058e64226-yU5RGvR974pGWvitb5QawA@public.gmane.org>
2017-08-03  2:16                 ` Guochun Mao
2017-08-03 10:09                   ` Matthias Brugger [this message]
2017-08-03 17:47                   ` Rob Herring
2017-08-04  3:44                     ` Guochun Mao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0796f86e-044b-5891-e56e-c96242611608@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=cyrille.pitchen@atmel.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=guochun.mao@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=marek.vasut@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).