All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Gao <jun.gao@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	Wolfram Sang <wsa@the-dreams.de>,
	robh@kernel.org, srv_heupstream@mediatek.com,
	devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	yingjoe.chen@mediatek.com
Subject: Re: [RESEND PATCH v3 1/2] dt-bindings: i2c: Add Mediatek MT2701 i2c binding
Date: Tue, 23 May 2017 11:34:01 +0800	[thread overview]
Message-ID: <1495510441.930.7.camel@mhfsdcap03> (raw)
In-Reply-To: <4111ffc2-0a25-0811-fbd3-401649431315@gmail.com>

On Wed, 2017-05-10 at 12:35 +0200, Matthias Brugger wrote:
> 
> On 28/03/17 21:22, Wolfram Sang wrote:
> > On Tue, Mar 28, 2017 at 05:50:12PM +0800, Jun Gao wrote:
> >> On Wed, 2017-03-22 at 10:05 +0100, Wolfram Sang wrote:
> >>> On Thu, Mar 09, 2017 at 11:13:04AM +0800, Jun Gao wrote:
> >>>> From: Jun Gao <jun.gao@mediatek.com>
> >>>>
> >>>> Add MT2701 i2c binding to i2c-mt6577.txt and there is no need to
> >>>> modify i2c driver.
> >>>>
> >>>> Signed-off-by: Jun Gao <jun.gao@mediatek.com>
> >>>
> >>> There is still the issue which Matthias Brugger pointed out on January,
> >>> 24th: you need to describe the fallback compatibles.
> >>>
> >>
> >> IMHO the value under compatible are just inputs which can be accepted.
> >> It's little strange to add fallback information in binding. Some other
> >> bindings do not describe so detailedly.
> >> Is it OK to make binding as minimum standard?
> >> If we describe it very detailedly, we will have to modify binding if
> >> there are some changes for mt2701.
> > 
> > My reading of the below is that I could simply use "mediatek,mt2701-i2c"
> > as compatible and things will work. But it won't, we don't have that in
> > the driver IIRC. So, we need a fallback for that to work.
> > 
> >> Rob, could you give some suggestions?  Thanks!
> > 
> > Would be welcome, yes. I lost track what the preferred solution is.
> > 
> 
> We will need to define the fallback binding for each SoC.
> As example take the rockchip mmc:
> http://elixir.free-electrons.com/linux/latest/source/Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt
> 
> Regards,
> Matthias
> 

Hi Rob,

There is no such requirement for other components.
Could you give us some suggestions? 
Thanks!


> >>
> >>>> ---
> >>>>   .../devicetree/bindings/i2c/i2c-mt6577.txt         |   11 ++++++-----
> >>>>   1 file changed, 6 insertions(+), 5 deletions(-)
> >>>>
> >>>> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> >>>> index 0ce6fa3..27dbbf9 100644
> >>>> --- a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> >>>> +++ b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> >>>> @@ -4,11 +4,12 @@ The Mediatek's I2C controller is used to interface with I2C devices.
> >>>>   
> >>>>   Required properties:
> >>>>     - compatible: value should be either of the following.
> >>>> -      (a) "mediatek,mt6577-i2c", for i2c compatible with mt6577 i2c.
> >>>> -      (b) "mediatek,mt6589-i2c", for i2c compatible with mt6589 i2c.
> >>>> -      (c) "mediatek,mt8127-i2c", for i2c compatible with mt8127 i2c.
> >>>> -      (d) "mediatek,mt8135-i2c", for i2c compatible with mt8135 i2c.
> >>>> -      (e) "mediatek,mt8173-i2c", for i2c compatible with mt8173 i2c.
> >>>> +	"mediatek,mt2701-i2c"
> >>>> +	"mediatek,mt6577-i2c"
> >>>> +	"mediatek,mt6589-i2c"
> >>>> +	"mediatek,mt8127-i2c"
> >>>> +	"mediatek,mt8135-i2c"
> >>>> +	"mediatek,mt8173-i2c"
> >>>>     - reg: physical base address of the controller and dma base, length of memory
> >>>>       mapped region.
> >>>>     - interrupts: interrupt number to the cpu.
> >>>> -- 
> >>>> 1.7.9.5
> >>>>
> >>
> >>

WARNING: multiple messages have this Message-ID (diff)
From: jun.gao@mediatek.com (Jun Gao)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v3 1/2] dt-bindings: i2c: Add Mediatek MT2701 i2c binding
Date: Tue, 23 May 2017 11:34:01 +0800	[thread overview]
Message-ID: <1495510441.930.7.camel@mhfsdcap03> (raw)
In-Reply-To: <4111ffc2-0a25-0811-fbd3-401649431315@gmail.com>

On Wed, 2017-05-10 at 12:35 +0200, Matthias Brugger wrote:
> 
> On 28/03/17 21:22, Wolfram Sang wrote:
> > On Tue, Mar 28, 2017 at 05:50:12PM +0800, Jun Gao wrote:
> >> On Wed, 2017-03-22 at 10:05 +0100, Wolfram Sang wrote:
> >>> On Thu, Mar 09, 2017 at 11:13:04AM +0800, Jun Gao wrote:
> >>>> From: Jun Gao <jun.gao@mediatek.com>
> >>>>
> >>>> Add MT2701 i2c binding to i2c-mt6577.txt and there is no need to
> >>>> modify i2c driver.
> >>>>
> >>>> Signed-off-by: Jun Gao <jun.gao@mediatek.com>
> >>>
> >>> There is still the issue which Matthias Brugger pointed out on January,
> >>> 24th: you need to describe the fallback compatibles.
> >>>
> >>
> >> IMHO the value under compatible are just inputs which can be accepted.
> >> It's little strange to add fallback information in binding. Some other
> >> bindings do not describe so detailedly.
> >> Is it OK to make binding as minimum standard?
> >> If we describe it very detailedly, we will have to modify binding if
> >> there are some changes for mt2701.
> > 
> > My reading of the below is that I could simply use "mediatek,mt2701-i2c"
> > as compatible and things will work. But it won't, we don't have that in
> > the driver IIRC. So, we need a fallback for that to work.
> > 
> >> Rob, could you give some suggestions?  Thanks!
> > 
> > Would be welcome, yes. I lost track what the preferred solution is.
> > 
> 
> We will need to define the fallback binding for each SoC.
> As example take the rockchip mmc:
> http://elixir.free-electrons.com/linux/latest/source/Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt
> 
> Regards,
> Matthias
> 

Hi Rob,

There is no such requirement for other components.
Could you give us some suggestions? 
Thanks!


> >>
> >>>> ---
> >>>>   .../devicetree/bindings/i2c/i2c-mt6577.txt         |   11 ++++++-----
> >>>>   1 file changed, 6 insertions(+), 5 deletions(-)
> >>>>
> >>>> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> >>>> index 0ce6fa3..27dbbf9 100644
> >>>> --- a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> >>>> +++ b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> >>>> @@ -4,11 +4,12 @@ The Mediatek's I2C controller is used to interface with I2C devices.
> >>>>   
> >>>>   Required properties:
> >>>>     - compatible: value should be either of the following.
> >>>> -      (a) "mediatek,mt6577-i2c", for i2c compatible with mt6577 i2c.
> >>>> -      (b) "mediatek,mt6589-i2c", for i2c compatible with mt6589 i2c.
> >>>> -      (c) "mediatek,mt8127-i2c", for i2c compatible with mt8127 i2c.
> >>>> -      (d) "mediatek,mt8135-i2c", for i2c compatible with mt8135 i2c.
> >>>> -      (e) "mediatek,mt8173-i2c", for i2c compatible with mt8173 i2c.
> >>>> +	"mediatek,mt2701-i2c"
> >>>> +	"mediatek,mt6577-i2c"
> >>>> +	"mediatek,mt6589-i2c"
> >>>> +	"mediatek,mt8127-i2c"
> >>>> +	"mediatek,mt8135-i2c"
> >>>> +	"mediatek,mt8173-i2c"
> >>>>     - reg: physical base address of the controller and dma base, length of memory
> >>>>       mapped region.
> >>>>     - interrupts: interrupt number to the cpu.
> >>>> -- 
> >>>> 1.7.9.5
> >>>>
> >>
> >>

WARNING: multiple messages have this Message-ID (diff)
From: Jun Gao <jun.gao@mediatek.com>
To: <robh@kernel.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	Wolfram Sang <wsa@the-dreams.de>, <robh@kernel.org>,
	<srv_heupstream@mediatek.com>, <devicetree@vger.kernel.org>,
	<linux-i2c@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>, <yingjoe.chen@mediatek.com>
Subject: Re: [RESEND PATCH v3 1/2] dt-bindings: i2c: Add Mediatek MT2701 i2c binding
Date: Tue, 23 May 2017 11:34:01 +0800	[thread overview]
Message-ID: <1495510441.930.7.camel@mhfsdcap03> (raw)
In-Reply-To: <4111ffc2-0a25-0811-fbd3-401649431315@gmail.com>

On Wed, 2017-05-10 at 12:35 +0200, Matthias Brugger wrote:
> 
> On 28/03/17 21:22, Wolfram Sang wrote:
> > On Tue, Mar 28, 2017 at 05:50:12PM +0800, Jun Gao wrote:
> >> On Wed, 2017-03-22 at 10:05 +0100, Wolfram Sang wrote:
> >>> On Thu, Mar 09, 2017 at 11:13:04AM +0800, Jun Gao wrote:
> >>>> From: Jun Gao <jun.gao@mediatek.com>
> >>>>
> >>>> Add MT2701 i2c binding to i2c-mt6577.txt and there is no need to
> >>>> modify i2c driver.
> >>>>
> >>>> Signed-off-by: Jun Gao <jun.gao@mediatek.com>
> >>>
> >>> There is still the issue which Matthias Brugger pointed out on January,
> >>> 24th: you need to describe the fallback compatibles.
> >>>
> >>
> >> IMHO the value under compatible are just inputs which can be accepted.
> >> It's little strange to add fallback information in binding. Some other
> >> bindings do not describe so detailedly.
> >> Is it OK to make binding as minimum standard?
> >> If we describe it very detailedly, we will have to modify binding if
> >> there are some changes for mt2701.
> > 
> > My reading of the below is that I could simply use "mediatek,mt2701-i2c"
> > as compatible and things will work. But it won't, we don't have that in
> > the driver IIRC. So, we need a fallback for that to work.
> > 
> >> Rob, could you give some suggestions?  Thanks!
> > 
> > Would be welcome, yes. I lost track what the preferred solution is.
> > 
> 
> We will need to define the fallback binding for each SoC.
> As example take the rockchip mmc:
> http://elixir.free-electrons.com/linux/latest/source/Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt
> 
> Regards,
> Matthias
> 

Hi Rob,

There is no such requirement for other components.
Could you give us some suggestions? 
Thanks!


> >>
> >>>> ---
> >>>>   .../devicetree/bindings/i2c/i2c-mt6577.txt         |   11 ++++++-----
> >>>>   1 file changed, 6 insertions(+), 5 deletions(-)
> >>>>
> >>>> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> >>>> index 0ce6fa3..27dbbf9 100644
> >>>> --- a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> >>>> +++ b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> >>>> @@ -4,11 +4,12 @@ The Mediatek's I2C controller is used to interface with I2C devices.
> >>>>   
> >>>>   Required properties:
> >>>>     - compatible: value should be either of the following.
> >>>> -      (a) "mediatek,mt6577-i2c", for i2c compatible with mt6577 i2c.
> >>>> -      (b) "mediatek,mt6589-i2c", for i2c compatible with mt6589 i2c.
> >>>> -      (c) "mediatek,mt8127-i2c", for i2c compatible with mt8127 i2c.
> >>>> -      (d) "mediatek,mt8135-i2c", for i2c compatible with mt8135 i2c.
> >>>> -      (e) "mediatek,mt8173-i2c", for i2c compatible with mt8173 i2c.
> >>>> +	"mediatek,mt2701-i2c"
> >>>> +	"mediatek,mt6577-i2c"
> >>>> +	"mediatek,mt6589-i2c"
> >>>> +	"mediatek,mt8127-i2c"
> >>>> +	"mediatek,mt8135-i2c"
> >>>> +	"mediatek,mt8173-i2c"
> >>>>     - reg: physical base address of the controller and dma base, length of memory
> >>>>       mapped region.
> >>>>     - interrupts: interrupt number to the cpu.
> >>>> -- 
> >>>> 1.7.9.5
> >>>>
> >>
> >>

  reply	other threads:[~2017-05-23  3:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09  3:13 [RESEND PATCH v3 0/2] Add i2c dt-binding and device node for Mediatek MT2701 Soc Jun Gao
2017-03-09  3:13 ` Jun Gao
2017-03-09  3:13 ` Jun Gao
     [not found] ` <1489029185-21447-1-git-send-email-jun.gao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-03-09  3:13   ` [RESEND PATCH v3 1/2] dt-bindings: i2c: Add Mediatek MT2701 i2c binding Jun Gao
2017-03-09  3:13     ` Jun Gao
2017-03-09  3:13     ` Jun Gao
2017-03-15 20:26     ` Rob Herring
2017-03-15 20:26       ` Rob Herring
2017-03-22  9:05     ` Wolfram Sang
2017-03-22  9:05       ` Wolfram Sang
2017-03-22  9:05       ` Wolfram Sang
2017-03-28  9:50       ` Jun Gao
2017-03-28  9:50         ` Jun Gao
2017-03-28  9:50         ` Jun Gao
2017-03-28 19:22         ` Wolfram Sang
2017-03-28 19:22           ` Wolfram Sang
2017-03-28 19:22           ` Wolfram Sang
2017-05-10 10:35           ` Matthias Brugger
2017-05-10 10:35             ` Matthias Brugger
2017-05-10 10:35             ` Matthias Brugger
2017-05-23  3:34             ` Jun Gao [this message]
2017-05-23  3:34               ` Jun Gao
2017-05-23  3:34               ` Jun Gao
2017-05-23  6:31               ` Matthias Brugger
2017-05-23  6:31                 ` Matthias Brugger
2017-03-09  3:13 ` [RESEND PATCH v3 2/2] arm: dts: Add Mediatek MT2701 i2c device node Jun Gao
2017-03-09  3:13   ` Jun Gao
2017-03-09  3:13   ` Jun Gao

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=1495510441.930.7.camel@mhfsdcap03 \
    --to=jun.gao@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@kernel.org \
    --cc=srv_heupstream@mediatek.com \
    --cc=wsa@the-dreams.de \
    --cc=yingjoe.chen@mediatek.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.