All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Felipe Balbi <felipe.balbi@linux.intel.com>,
	Amelie Delaunay <amelie.delaunay@st.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	John Youn <johnyoun@synopsys.com>
Cc: <linux-usb@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: Re: [PATCHv2 0/7] Add support for USB OTG on STM32F7
Date: Wed, 11 Oct 2017 16:38:08 +0200	[thread overview]
Message-ID: <3c36db6d-75fd-1be6-e946-b75a04e3760e@st.com> (raw)
In-Reply-To: <87sheplsrm.fsf@linux.intel.com>



On 10/11/2017 03:26 PM, Felipe Balbi wrote:
> 
> Hi,
> 
> Alexandre Torgue <alexandre.torgue@st.com> writes:
>> Hi
>>
>> On 10/11/2017 01:50 PM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Alexandre Torgue <alexandre.torgue@st.com> writes:
>>>> Hi Felip
>>>>
>>>> On 10/11/2017 12:04 PM, Felipe Balbi wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Amelie Delaunay <amelie.delaunay@st.com> writes:
>>>>>> The STM32F7 MCU family embeds two DWC2 USB OTG cores. One core is USB
>>>>>> OTG FS and the other is USB OTG HS. The USB FS core only works with its
>>>>>> internal phy whilst the USB HS core can work in HS with external ULPI phy
>>>>>> or in FS/LS with the on-chip FS phy.
>>>>>>
>>>>>> Amelie Delaunay (7):
>>>>>>      dt-bindings: usb: Document the STM32F7 DWC2 USB OTG HS core binding
>>>>>>      usb: dwc2: add support for STM32F7 USB OTG HS
>>>>>>      ARM: dts: stm32: Add USB HS support for STM32F746 MCU
>>>>>
>>>>> I have applied these three patches. Should I take the rest? They seems
>>>>> like they could go upstream through the ARM maintainers.
>>>>>
>>>>
>>>> I will take other DT patches in my PR.
>>>>
>>>> Concerning "ARM: dts: stm32: Add USB HS support for STM32F746 MCU" patch
>>>> I prefer also to take it. This patch adds some pinctrl groups but stm32
>>>> pinctrl bindings will change in my next PR (we will use a macro to
>>>> define pins instead of using defined values). So if you push the DT
>>>> patch through your pull request there will be a merge issue.
>>>> It is possible that I take also this one ?
>>>
>>> In that case, it's best if you take them all :-) Here's my Ack:
>>>
>>> Acked-by: Felipe Balbi <felipe.balbi@linux.intel.com>
>>>
>>> I'll drop them from my tree now
>>
>> Ok perfect, I will take DT patches (3 to 7) and I let you take patch 1&2
>> in your tree.
> 
> Well, I have dropped them from my tree. Please two 1-7 through yours.

Hum, ok for this patchset but IMO it is better (next time) that you take 
driver pacthes in your tree and I take only DT patches in mine.
No ?

Regards
Alex

> 

WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Felipe Balbi <felipe.balbi@linux.intel.com>,
	Amelie Delaunay <amelie.delaunay@st.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	John Youn <johnyoun@synopsys.com>
Cc: devicetree@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: Re: [PATCHv2 0/7] Add support for USB OTG on STM32F7
Date: Wed, 11 Oct 2017 16:38:08 +0200	[thread overview]
Message-ID: <3c36db6d-75fd-1be6-e946-b75a04e3760e@st.com> (raw)
In-Reply-To: <87sheplsrm.fsf@linux.intel.com>



On 10/11/2017 03:26 PM, Felipe Balbi wrote:
> 
> Hi,
> 
> Alexandre Torgue <alexandre.torgue@st.com> writes:
>> Hi
>>
>> On 10/11/2017 01:50 PM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Alexandre Torgue <alexandre.torgue@st.com> writes:
>>>> Hi Felip
>>>>
>>>> On 10/11/2017 12:04 PM, Felipe Balbi wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Amelie Delaunay <amelie.delaunay@st.com> writes:
>>>>>> The STM32F7 MCU family embeds two DWC2 USB OTG cores. One core is USB
>>>>>> OTG FS and the other is USB OTG HS. The USB FS core only works with its
>>>>>> internal phy whilst the USB HS core can work in HS with external ULPI phy
>>>>>> or in FS/LS with the on-chip FS phy.
>>>>>>
>>>>>> Amelie Delaunay (7):
>>>>>>      dt-bindings: usb: Document the STM32F7 DWC2 USB OTG HS core binding
>>>>>>      usb: dwc2: add support for STM32F7 USB OTG HS
>>>>>>      ARM: dts: stm32: Add USB HS support for STM32F746 MCU
>>>>>
>>>>> I have applied these three patches. Should I take the rest? They seems
>>>>> like they could go upstream through the ARM maintainers.
>>>>>
>>>>
>>>> I will take other DT patches in my PR.
>>>>
>>>> Concerning "ARM: dts: stm32: Add USB HS support for STM32F746 MCU" patch
>>>> I prefer also to take it. This patch adds some pinctrl groups but stm32
>>>> pinctrl bindings will change in my next PR (we will use a macro to
>>>> define pins instead of using defined values). So if you push the DT
>>>> patch through your pull request there will be a merge issue.
>>>> It is possible that I take also this one ?
>>>
>>> In that case, it's best if you take them all :-) Here's my Ack:
>>>
>>> Acked-by: Felipe Balbi <felipe.balbi@linux.intel.com>
>>>
>>> I'll drop them from my tree now
>>
>> Ok perfect, I will take DT patches (3 to 7) and I let you take patch 1&2
>> in your tree.
> 
> Well, I have dropped them from my tree. Please two 1-7 through yours.

Hum, ok for this patchset but IMO it is better (next time) that you take 
driver pacthes in your tree and I take only DT patches in mine.
No ?

Regards
Alex

> 

WARNING: multiple messages have this Message-ID (diff)
From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/7] Add support for USB OTG on STM32F7
Date: Wed, 11 Oct 2017 16:38:08 +0200	[thread overview]
Message-ID: <3c36db6d-75fd-1be6-e946-b75a04e3760e@st.com> (raw)
In-Reply-To: <87sheplsrm.fsf@linux.intel.com>



On 10/11/2017 03:26 PM, Felipe Balbi wrote:
> 
> Hi,
> 
> Alexandre Torgue <alexandre.torgue@st.com> writes:
>> Hi
>>
>> On 10/11/2017 01:50 PM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Alexandre Torgue <alexandre.torgue@st.com> writes:
>>>> Hi Felip
>>>>
>>>> On 10/11/2017 12:04 PM, Felipe Balbi wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Amelie Delaunay <amelie.delaunay@st.com> writes:
>>>>>> The STM32F7 MCU family embeds two DWC2 USB OTG cores. One core is USB
>>>>>> OTG FS and the other is USB OTG HS. The USB FS core only works with its
>>>>>> internal phy whilst the USB HS core can work in HS with external ULPI phy
>>>>>> or in FS/LS with the on-chip FS phy.
>>>>>>
>>>>>> Amelie Delaunay (7):
>>>>>>      dt-bindings: usb: Document the STM32F7 DWC2 USB OTG HS core binding
>>>>>>      usb: dwc2: add support for STM32F7 USB OTG HS
>>>>>>      ARM: dts: stm32: Add USB HS support for STM32F746 MCU
>>>>>
>>>>> I have applied these three patches. Should I take the rest? They seems
>>>>> like they could go upstream through the ARM maintainers.
>>>>>
>>>>
>>>> I will take other DT patches in my PR.
>>>>
>>>> Concerning "ARM: dts: stm32: Add USB HS support for STM32F746 MCU" patch
>>>> I prefer also to take it. This patch adds some pinctrl groups but stm32
>>>> pinctrl bindings will change in my next PR (we will use a macro to
>>>> define pins instead of using defined values). So if you push the DT
>>>> patch through your pull request there will be a merge issue.
>>>> It is possible that I take also this one ?
>>>
>>> In that case, it's best if you take them all :-) Here's my Ack:
>>>
>>> Acked-by: Felipe Balbi <felipe.balbi@linux.intel.com>
>>>
>>> I'll drop them from my tree now
>>
>> Ok perfect, I will take DT patches (3 to 7) and I let you take patch 1&2
>> in your tree.
> 
> Well, I have dropped them from my tree. Please two 1-7 through yours.

Hum, ok for this patchset but IMO it is better (next time) that you take 
driver pacthes in your tree and I take only DT patches in mine.
No ?

Regards
Alex

> 

  reply	other threads:[~2017-10-11 14:38 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 14:20 [PATCHv2 0/7] Add support for USB OTG on STM32F7 Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 1/7] dt-bindings: usb: Document the STM32F7 DWC2 USB OTG HS core binding Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-09-01 15:35   ` Rob Herring
2017-09-01 15:35     ` Rob Herring
2017-09-01 15:35     ` Rob Herring
2017-08-28 14:20 ` [PATCHv2 2/7] usb: dwc2: add support for STM32F7 USB OTG HS Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-09-29 14:20   ` Amelie DELAUNAY
2017-09-29 14:20     ` Amelie DELAUNAY
2017-09-29 14:20     ` Amelie DELAUNAY
2017-09-30 17:16     ` John Youn
2017-09-30 17:16       ` John Youn
2017-09-30 17:16       ` John Youn
2017-08-28 14:20 ` [PATCHv2 3/7] ARM: dts: stm32: Add USB HS support for STM32F746 MCU Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 4/7] ARM: dts: stm32: Enable USB HS on stm32746g-eval Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 5/7] ARM: dts: stm32: Enable USB HS on stm32f746-disco Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 6/7] ARM: dts: stm32: Add USB FS support for STM32F746 MCU Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 7/7] ARM: dts: stm32: Enable USB FS on stm32f746-disco Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-08-28 14:20   ` Amelie Delaunay
2017-10-11 10:04 ` [PATCHv2 0/7] Add support for USB OTG on STM32F7 Felipe Balbi
2017-10-11 10:04   ` Felipe Balbi
2017-10-11 10:04   ` Felipe Balbi
2017-10-11 11:36   ` Alexandre Torgue
2017-10-11 11:36     ` Alexandre Torgue
2017-10-11 11:36     ` Alexandre Torgue
2017-10-11 11:50     ` Felipe Balbi
2017-10-11 11:50       ` Felipe Balbi
2017-10-11 11:50       ` Felipe Balbi
2017-10-11 12:05       ` Alexandre Torgue
2017-10-11 12:05         ` Alexandre Torgue
2017-10-11 12:05         ` Alexandre Torgue
2017-10-11 13:26         ` Felipe Balbi
2017-10-11 13:26           ` Felipe Balbi
2017-10-11 13:26           ` Felipe Balbi
2017-10-11 14:38           ` Alexandre Torgue [this message]
2017-10-11 14:38             ` Alexandre Torgue
2017-10-11 14:38             ` Alexandre Torgue
2017-10-12  8:32             ` Amelie DELAUNAY
2017-10-12  8:32               ` Amelie DELAUNAY
2017-10-12  8:32               ` Amelie DELAUNAY
2017-10-12  8:43               ` Felipe Balbi
2017-10-12  8:43                 ` Felipe Balbi
2017-10-12  8:43                 ` Felipe Balbi
2017-10-12 11:46                 ` Alexandre Torgue
2017-10-12 11:46                   ` Alexandre Torgue
2017-10-12 11:46                   ` Alexandre Torgue
2017-10-12 11:51                   ` Felipe Balbi
2017-10-12 11:51                     ` Felipe Balbi
2017-10-12 11:51                     ` Felipe Balbi
2017-10-12 11:53                     ` Felipe Balbi
2017-10-12 11:53                       ` Felipe Balbi
2017-10-12 11:53                       ` Felipe Balbi
2017-10-12 12:01                       ` Alexandre Torgue
2017-10-12 12:01                         ` Alexandre Torgue
2017-10-12 12:01                         ` Alexandre Torgue
2017-10-16 16:16 ` Alexandre Torgue
2017-10-16 16:16   ` Alexandre Torgue
2017-10-16 16:16   ` Alexandre Torgue

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=3c36db6d-75fd-1be6-e946-b75a04e3760e@st.com \
    --to=alexandre.torgue@st.com \
    --cc=amelie.delaunay@st.com \
    --cc=benjamin.gaignard@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=felipe.balbi@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johnyoun@synopsys.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mcoquelin.stm32@gmail.com \
    --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 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.