Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1378609 > unrolled thread

Re: [PATCH v5 00/10] Support for Cortex-M Prototyping System

Started byVladimir Murzin <vladimir.murzin@arm.com>
First post2016-04-14 10:50 +0200
Last post2016-04-15 18:30 +0200
Articles 6 — 4 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v5 00/10] Support for Cortex-M Prototyping System Vladimir Murzin <vladimir.murzin@arm.com> - 2016-04-14 10:50 +0200
    Re: [PATCH v5 00/10] Support for Cortex-M Prototyping System Daniel Lezcano <daniel.lezcano@linaro.org> - 2016-04-14 11:50 +0200
    Re: [PATCH v5 00/10] Support for Cortex-M Prototyping System Greg KH <gregkh@linuxfoundation.org> - 2016-04-14 21:30 +0200
      Re: [PATCH v5 00/10] Support for Cortex-M Prototyping System Sudeep Holla <sudeep.holla@arm.com> - 2016-04-15 11:00 +0200
        Re: [PATCH v5 00/10] Support for Cortex-M Prototyping System Vladimir Murzin <vladimir.murzin@arm.com> - 2016-04-15 11:40 +0200
        Re: [PATCH v5 00/10] Support for Cortex-M Prototyping System Greg KH <gregkh@linuxfoundation.org> - 2016-04-15 18:30 +0200

#1378609 — Re: [PATCH v5 00/10] Support for Cortex-M Prototyping System

FromVladimir Murzin <vladimir.murzin@arm.com>
Date2016-04-14 10:50 +0200
SubjectRe: [PATCH v5 00/10] Support for Cortex-M Prototyping System
Message-ID<rnL8n-7nM-23@gated-at.bofh.it>
Hi,

On 01/04/16 15:02, Vladimir Murzin wrote:
> Hi,
> 
> This patch series provides the basic support for running ucLinux on V2M-MPS2
> platform.
> 
> With these patches applied ucLinux can be run on both HW and FVP models
> with Cortex-M3/M4/M7 configurations.

Any objection to get it merged?

Sudeep Holla noticed that there is merge conflict against linux-next
with PIC32 uart (Makefile and serial_core.h), so should I provide
conflict resolution or do rebase on someone's branch?

Anyway, I'd be glad to know how it should be processed further?

Thanks
Vladimir

> 
> Board description:
> 
> http://infocenter.arm.com/help/topic/com.arm.doc.100112_0100_03_en/arm_versatile_express_cortex_m_prototyping_system_(v2m_mps2)_technical_reference_manual_100112_0100_03_en.pdf
> 
> Application notes (cover Cortex-M3/M4/M7):
> 
> http://infocenter.arm.com/help/topic/com.arm.doc.dai0385a/DAI0385A_cortex_m3_on_v2m_mps2.pdf
> http://infocenter.arm.com/help/topic/com.arm.doc.dai0386a/DAI0386A_cortex_m4_on_v2m_mps2.pdf
> http://infocenter.arm.com/help/topic/com.arm.doc.dai0399a/DAI0399A_cortex_m7_on_v2m_mps2.pdf
> http://infocenter.arm.com/help/topic/com.arm.doc.dai0400a/DAI0400A_cortex_m7_on_v2m_mps2.pdf
> 
> Cortex-M System Design Kit (referenced as CMDK from documents above):
> 
> http://infocenter.arm.com/help/topic/com.arm.doc.ddi0479c/DDI0479C_cortex_m_system_design_kit_r1p0_trm.pdf
> 
> I'd be happy to hear any feedback/comments on this series!
> 
> Changelog:
> 
>   v4  -> v5:
>       - rebased on 4.6-rc1
>       - updated mps2-uart per Peter
>       - s/COFIG_ARCH_MPS2/CONFIG_ARCH_MPS under arm/mach-vexpress
> 
>   v3  -> v4:
>       - rebased on 4.5-rc5
>       - updated mps2-uart per Andy, Alan and Peter
>       - dropped "zombie" EMBEDDED from defconfg per Arnd
>       - moved mps2 under vexpress umbrella per Arnd
>       - updated device-tree sources per Arnd
>       - dropped low-level debug support, seems earlycon works well for that
> 
>   v2  -> v3:
>       - rebased on 4.5-rc4
>       - fixes for mps2-timer per Thomas
>       - swicthed back to ttyMPS naming per Greg
> 
>   v1  -> v2:
>       - rebased on 4.5-rc2
>       - fixes for mps2-timer per Daniel and Rob (added Ack from Daniel)
>       - fixes for mps2-uart per Greg and Andy
> 
>   RFC -> v1:
>       - dropped RFC tag
>       - rebased on 4.4-rc3
>       - added Acks from Rob
>       - updated mps2-timer per Daniel
>       - fixed build failures reported by 0-DAY kernel test infrastructure
> 
> Thanks!
> 
> Vladimir Murzin (10):
>   dt-bindings: document the MPS2 timer bindings
>   clockevents/drivers: add MPS2 Timer driver
>   dt-bindings: document the MPS2 UART bindings
>   serial: mps2-uart: add MPS2 UART driver
>   serial: mps2-uart: add support for early console
>   ARM: vexpress/mps2: introduce MPS2 platform
>   ARM: configs: add MPS2 defconfig
>   ARM: dts: introduce MPS2 AN385/AN386
>   ARM: dts: introduce MPS2 AN399/AN400
>   MAINTAINERS: Update ARM Versatile Express platform entry
> 
>  .../devicetree/bindings/serial/arm,mps2-uart.txt   |   19 +
>  .../devicetree/bindings/timer/arm,mps2-timer.txt   |   28 +
>  MAINTAINERS                                        |    1 +
>  arch/arm/Kconfig                                   |    8 +
>  arch/arm/Makefile                                  |    1 +
>  arch/arm/boot/dts/Makefile                         |    3 +
>  arch/arm/boot/dts/mps2-an385.dts                   |   92 +++
>  arch/arm/boot/dts/mps2-an399.dts                   |   92 +++
>  arch/arm/boot/dts/mps2.dtsi                        |  242 ++++++++
>  arch/arm/configs/mps2_defconfig                    |  109 ++++
>  arch/arm/mach-vexpress/Makefile                    |    4 +-
>  arch/arm/mach-vexpress/Makefile.boot               |    3 +
>  arch/arm/mach-vexpress/v2m-mps2.c                  |   21 +
>  drivers/clocksource/Kconfig                        |    6 +
>  drivers/clocksource/Makefile                       |    1 +
>  drivers/clocksource/mps2-timer.c                   |  275 +++++++++
>  drivers/tty/serial/Kconfig                         |   13 +
>  drivers/tty/serial/Makefile                        |    1 +
>  drivers/tty/serial/mps2-uart.c                     |  626 ++++++++++++++++++++
>  include/uapi/linux/serial_core.h                   |    3 +
>  20 files changed, 1547 insertions(+), 1 deletion(-)
>  create mode 100644 Documentation/devicetree/bindings/serial/arm,mps2-uart.txt
>  create mode 100644 Documentation/devicetree/bindings/timer/arm,mps2-timer.txt
>  create mode 100644 arch/arm/boot/dts/mps2-an385.dts
>  create mode 100644 arch/arm/boot/dts/mps2-an399.dts
>  create mode 100644 arch/arm/boot/dts/mps2.dtsi
>  create mode 100644 arch/arm/configs/mps2_defconfig
>  create mode 100644 arch/arm/mach-vexpress/Makefile.boot
>  create mode 100644 arch/arm/mach-vexpress/v2m-mps2.c
>  create mode 100644 drivers/clocksource/mps2-timer.c
>  create mode 100644 drivers/tty/serial/mps2-uart.c
> 

[toc] | [next] | [standalone]


#1378660

FromDaniel Lezcano <daniel.lezcano@linaro.org>
Date2016-04-14 11:50 +0200
Message-ID<rnM4q-88a-19@gated-at.bofh.it>
In reply to#1378609
On Thu, Apr 14, 2016 at 09:47:57AM +0100, Vladimir Murzin wrote:
> Hi,
> 
> On 01/04/16 15:02, Vladimir Murzin wrote:
> > Hi,
> > 
> > This patch series provides the basic support for running ucLinux on V2M-MPS2
> > platform.
> > 
> > With these patches applied ucLinux can be run on both HW and FVP models
> > with Cortex-M3/M4/M7 configurations.
> 
> Any objection to get it merged?
> 
> Sudeep Holla noticed that there is merge conflict against linux-next
> with PIC32 uart (Makefile and serial_core.h), so should I provide
> conflict resolution or do rebase on someone's branch?
> 
> Anyway, I'd be glad to know how it should be processed further?

This patchset should go through the arm-soc tree. Any conflicts resulting
from a merge *after* your patchset is in the arm-soc tree is no longer your
problem.

So IOW, if your patchset applies to arm-soc and Arnd is ok to pick it, then
everything is fine.

  -- Daniel

[toc] | [prev] | [next] | [standalone]


#1379239

FromGreg KH <gregkh@linuxfoundation.org>
Date2016-04-14 21:30 +0200
Message-ID<rnV7H-77H-13@gated-at.bofh.it>
In reply to#1378609
On Thu, Apr 14, 2016 at 09:47:57AM +0100, Vladimir Murzin wrote:
> Hi,
> 
> On 01/04/16 15:02, Vladimir Murzin wrote:
> > Hi,
> > 
> > This patch series provides the basic support for running ucLinux on V2M-MPS2
> > platform.
> > 
> > With these patches applied ucLinux can be run on both HW and FVP models
> > with Cortex-M3/M4/M7 configurations.
> 
> Any objection to get it merged?
> 
> Sudeep Holla noticed that there is merge conflict against linux-next
> with PIC32 uart (Makefile and serial_core.h), so should I provide
> conflict resolution or do rebase on someone's branch?
> 
> Anyway, I'd be glad to know how it should be processed further?

I have no objection to the tty/serial changes, so if this all goes
through the arm-soc tree, that's fine with me.

thanks,

greg k-h

[toc] | [prev] | [next] | [standalone]


#1379563

FromSudeep Holla <sudeep.holla@arm.com>
Date2016-04-15 11:00 +0200
Message-ID<ro7LB-hc-27@gated-at.bofh.it>
In reply to#1379239

On 14/04/16 20:25, Greg KH wrote:
> On Thu, Apr 14, 2016 at 09:47:57AM +0100, Vladimir Murzin wrote:
>> Hi,
>>
>> On 01/04/16 15:02, Vladimir Murzin wrote:
>>> Hi,
>>>
>>> This patch series provides the basic support for running ucLinux on V2M-MPS2
>>> platform.
>>>
>>> With these patches applied ucLinux can be run on both HW and FVP models
>>> with Cortex-M3/M4/M7 configurations.
>>
>> Any objection to get it merged?
>>
>> Sudeep Holla noticed that there is merge conflict against linux-next
>> with PIC32 uart (Makefile and serial_core.h), so should I provide
>> conflict resolution or do rebase on someone's branch?
>>
>> Anyway, I'd be glad to know how it should be processed further?
>
> I have no objection to the tty/serial changes, so if this all goes
> through the arm-soc tree, that's fine with me.
>

Thanks Greg, can I take this as Ack ? arm-soc guys might expect to see
that tag :)

Hi Vladimir,

I have pulled this series into
git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git 
for-next/armv7-vexpress-updates

I will stick Greg's tag when it comes.

-- 
Regards,
Sudeep

[toc] | [prev] | [next] | [standalone]


#1379646

FromVladimir Murzin <vladimir.murzin@arm.com>
Date2016-04-15 11:40 +0200
Message-ID<ro8oi-S5-17@gated-at.bofh.it>
In reply to#1379563
On 15/04/16 09:52, Sudeep Holla wrote:
> 
> 
> On 14/04/16 20:25, Greg KH wrote:
>> On Thu, Apr 14, 2016 at 09:47:57AM +0100, Vladimir Murzin wrote:
>>> Hi,
>>>
>>> On 01/04/16 15:02, Vladimir Murzin wrote:
>>>> Hi,
>>>>
>>>> This patch series provides the basic support for running ucLinux on
>>>> V2M-MPS2
>>>> platform.
>>>>
>>>> With these patches applied ucLinux can be run on both HW and FVP models
>>>> with Cortex-M3/M4/M7 configurations.
>>>
>>> Any objection to get it merged?
>>>
>>> Sudeep Holla noticed that there is merge conflict against linux-next
>>> with PIC32 uart (Makefile and serial_core.h), so should I provide
>>> conflict resolution or do rebase on someone's branch?
>>>
>>> Anyway, I'd be glad to know how it should be processed further?
>>
>> I have no objection to the tty/serial changes, so if this all goes
>> through the arm-soc tree, that's fine with me.
>>
> 
> Thanks Greg, can I take this as Ack ? arm-soc guys might expect to see
> that tag :)
> 
> Hi Vladimir,
> 
> I have pulled this series into
> git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git
> for-next/armv7-vexpress-updates
> 
> I will stick Greg's tag when it comes.
> 

Everything looks fine! Thanks everyone for making it happen!

Cheers
Vladimir

[toc] | [prev] | [next] | [standalone]


#1379984

FromGreg KH <gregkh@linuxfoundation.org>
Date2016-04-15 18:30 +0200
Message-ID<roeN4-5WB-25@gated-at.bofh.it>
In reply to#1379563
On Fri, Apr 15, 2016 at 09:52:20AM +0100, Sudeep Holla wrote:
> 
> 
> On 14/04/16 20:25, Greg KH wrote:
> > On Thu, Apr 14, 2016 at 09:47:57AM +0100, Vladimir Murzin wrote:
> > > Hi,
> > > 
> > > On 01/04/16 15:02, Vladimir Murzin wrote:
> > > > Hi,
> > > > 
> > > > This patch series provides the basic support for running ucLinux on V2M-MPS2
> > > > platform.
> > > > 
> > > > With these patches applied ucLinux can be run on both HW and FVP models
> > > > with Cortex-M3/M4/M7 configurations.
> > > 
> > > Any objection to get it merged?
> > > 
> > > Sudeep Holla noticed that there is merge conflict against linux-next
> > > with PIC32 uart (Makefile and serial_core.h), so should I provide
> > > conflict resolution or do rebase on someone's branch?
> > > 
> > > Anyway, I'd be glad to know how it should be processed further?
> > 
> > I have no objection to the tty/serial changes, so if this all goes
> > through the arm-soc tree, that's fine with me.
> > 
> 
> Thanks Greg, can I take this as Ack ? arm-soc guys might expect to see
> that tag :)

Sorry, yes:

	Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web