All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Biju Das <biju.das@bp.renesas.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Simon Horman <horms@verge.net.au>,
	Chris Paterson <chris.paterson2@renesas.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND] phy: rcar-gen2: Add r8a7743/5 support
Date: Wed, 25 Oct 2017 16:00:10 +0530	[thread overview]
Message-ID: <87211738-8d65-32c0-fb6b-dc2cd395016a@ti.com> (raw)
In-Reply-To: <bcfa1e90-c497-ee29-687d-9f9a04ce2d4b@ti.com>



On Wednesday 18 October 2017 05:10 PM, Kishon Vijay Abraham I wrote:
> 
> 
> On Monday 09 October 2017 03:52 PM, Biju Das wrote:
>> Add USB PHY support for r8a7743/5 SoC. Renesas RZ/G1[ME] (R8A7743/5)
>> USB PHY is identical to the R-Car Gen2 family.
>>
>> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
>> Acked-by: Simon Horman <horms+renesas@verge.net.au>
>> Acked-by: Rob Herring <robh@kernel.org>
>> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> 
> merged, thanks!

just realized $subject is misleading since this is only dt-binding patch. Do
you plan to send the driver patch too?

Thanks
Kishon
> 
> -Kishon
>> ---
>> This patch is tested against Linux next tag next-20170929.
>>
>>  Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt | 7 +++++--
>>  1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt b/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
>> index 91da947..eeb9e18 100644
>> --- a/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
>> +++ b/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
>> @@ -4,10 +4,13 @@ This file provides information on what the device node for the R-Car generation
>>  2 USB PHY contains.
>>  
>>  Required properties:
>> -- compatible: "renesas,usb-phy-r8a7790" if the device is a part of R8A7790 SoC.
>> +- compatible: "renesas,usb-phy-r8a7743" if the device is a part of R8A7743 SoC.
>> +	      "renesas,usb-phy-r8a7745" if the device is a part of R8A7745 SoC.
>> +	      "renesas,usb-phy-r8a7790" if the device is a part of R8A7790 SoC.
>>  	      "renesas,usb-phy-r8a7791" if the device is a part of R8A7791 SoC.
>>  	      "renesas,usb-phy-r8a7794" if the device is a part of R8A7794 SoC.
>> -	      "renesas,rcar-gen2-usb-phy" for a generic R-Car Gen2 compatible device.
>> +	      "renesas,rcar-gen2-usb-phy" for a generic R-Car Gen2 or
>> +					  RZ/G1 compatible device.
>>  
>>  	      When compatible with the generic version, nodes must list the
>>  	      SoC-specific version corresponding to the platform first
>>

WARNING: multiple messages have this Message-ID (diff)
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Biju Das <biju.das@bp.renesas.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Simon Horman <horms@verge.net.au>,
	Chris Paterson <chris.paterson2@renesas.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
	<devicetree@vger.kernel.org>, <linux-renesas-soc@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH RESEND] phy: rcar-gen2: Add r8a7743/5 support
Date: Wed, 25 Oct 2017 16:00:10 +0530	[thread overview]
Message-ID: <87211738-8d65-32c0-fb6b-dc2cd395016a@ti.com> (raw)
In-Reply-To: <bcfa1e90-c497-ee29-687d-9f9a04ce2d4b@ti.com>



On Wednesday 18 October 2017 05:10 PM, Kishon Vijay Abraham I wrote:
> 
> 
> On Monday 09 October 2017 03:52 PM, Biju Das wrote:
>> Add USB PHY support for r8a7743/5 SoC. Renesas RZ/G1[ME] (R8A7743/5)
>> USB PHY is identical to the R-Car Gen2 family.
>>
>> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
>> Acked-by: Simon Horman <horms+renesas@verge.net.au>
>> Acked-by: Rob Herring <robh@kernel.org>
>> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> 
> merged, thanks!

just realized $subject is misleading since this is only dt-binding patch. Do
you plan to send the driver patch too?

Thanks
Kishon
> 
> -Kishon
>> ---
>> This patch is tested against Linux next tag next-20170929.
>>
>>  Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt | 7 +++++--
>>  1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt b/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
>> index 91da947..eeb9e18 100644
>> --- a/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
>> +++ b/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
>> @@ -4,10 +4,13 @@ This file provides information on what the device node for the R-Car generation
>>  2 USB PHY contains.
>>  
>>  Required properties:
>> -- compatible: "renesas,usb-phy-r8a7790" if the device is a part of R8A7790 SoC.
>> +- compatible: "renesas,usb-phy-r8a7743" if the device is a part of R8A7743 SoC.
>> +	      "renesas,usb-phy-r8a7745" if the device is a part of R8A7745 SoC.
>> +	      "renesas,usb-phy-r8a7790" if the device is a part of R8A7790 SoC.
>>  	      "renesas,usb-phy-r8a7791" if the device is a part of R8A7791 SoC.
>>  	      "renesas,usb-phy-r8a7794" if the device is a part of R8A7794 SoC.
>> -	      "renesas,rcar-gen2-usb-phy" for a generic R-Car Gen2 compatible device.
>> +	      "renesas,rcar-gen2-usb-phy" for a generic R-Car Gen2 or
>> +					  RZ/G1 compatible device.
>>  
>>  	      When compatible with the generic version, nodes must list the
>>  	      SoC-specific version corresponding to the platform first
>>

WARNING: multiple messages have this Message-ID (diff)
From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] phy: rcar-gen2: Add r8a7743/5 support
Date: Wed, 25 Oct 2017 16:00:10 +0530	[thread overview]
Message-ID: <87211738-8d65-32c0-fb6b-dc2cd395016a@ti.com> (raw)
In-Reply-To: <bcfa1e90-c497-ee29-687d-9f9a04ce2d4b@ti.com>



On Wednesday 18 October 2017 05:10 PM, Kishon Vijay Abraham I wrote:
> 
> 
> On Monday 09 October 2017 03:52 PM, Biju Das wrote:
>> Add USB PHY support for r8a7743/5 SoC. Renesas RZ/G1[ME] (R8A7743/5)
>> USB PHY is identical to the R-Car Gen2 family.
>>
>> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
>> Acked-by: Simon Horman <horms+renesas@verge.net.au>
>> Acked-by: Rob Herring <robh@kernel.org>
>> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> 
> merged, thanks!

just realized $subject is misleading since this is only dt-binding patch. Do
you plan to send the driver patch too?

Thanks
Kishon
> 
> -Kishon
>> ---
>> This patch is tested against Linux next tag next-20170929.
>>
>>  Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt | 7 +++++--
>>  1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt b/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
>> index 91da947..eeb9e18 100644
>> --- a/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
>> +++ b/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
>> @@ -4,10 +4,13 @@ This file provides information on what the device node for the R-Car generation
>>  2 USB PHY contains.
>>  
>>  Required properties:
>> -- compatible: "renesas,usb-phy-r8a7790" if the device is a part of R8A7790 SoC.
>> +- compatible: "renesas,usb-phy-r8a7743" if the device is a part of R8A7743 SoC.
>> +	      "renesas,usb-phy-r8a7745" if the device is a part of R8A7745 SoC.
>> +	      "renesas,usb-phy-r8a7790" if the device is a part of R8A7790 SoC.
>>  	      "renesas,usb-phy-r8a7791" if the device is a part of R8A7791 SoC.
>>  	      "renesas,usb-phy-r8a7794" if the device is a part of R8A7794 SoC.
>> -	      "renesas,rcar-gen2-usb-phy" for a generic R-Car Gen2 compatible device.
>> +	      "renesas,rcar-gen2-usb-phy" for a generic R-Car Gen2 or
>> +					  RZ/G1 compatible device.
>>  
>>  	      When compatible with the generic version, nodes must list the
>>  	      SoC-specific version corresponding to the platform first
>>

  reply	other threads:[~2017-10-25 10:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 10:22 [PATCH RESEND] phy: rcar-gen2: Add r8a7743/5 support Biju Das
2017-10-09 10:22 ` Biju Das
     [not found] ` <1507544543-28654-1-git-send-email-biju.das-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-10-16 10:52   ` Chris Paterson
2017-10-16 10:52     ` Chris Paterson
2017-10-16 10:52     ` Chris Paterson
2017-10-18 11:40   ` Kishon Vijay Abraham I
2017-10-18 11:40     ` Kishon Vijay Abraham I
2017-10-18 11:40     ` Kishon Vijay Abraham I
2017-10-25 10:30     ` Kishon Vijay Abraham I [this message]
2017-10-25 10:30       ` Kishon Vijay Abraham I
2017-10-25 10:30       ` Kishon Vijay Abraham I
     [not found]       ` <87211738-8d65-32c0-fb6b-dc2cd395016a-l0cyMroinI0@public.gmane.org>
2017-10-25 10:32         ` Geert Uytterhoeven
2017-10-25 10:32           ` Geert Uytterhoeven
2017-10-25 10:32           ` Geert Uytterhoeven

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=87211738-8d65-32c0-fb6b-dc2cd395016a@ti.com \
    --to=kishon@ti.com \
    --cc=biju.das@bp.renesas.com \
    --cc=chris.paterson2@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=yoshihiro.shimoda.uh@renesas.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.