All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stefan-Gabriel Mirea <stefan-gabriel.mirea@nxp.com>
Cc: corbet@lwn.net, robh+dt@kernel.org, mark.rutland@arm.com,
	catalin.marinas@arm.com, will@kernel.org, shawnguo@kernel.org,
	leoyang.li@nxp.com, jslaby@suse.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-serial@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 0/5] Add initial support for S32V234-EVB
Date: Wed, 16 Oct 2019 06:17:28 -0700	[thread overview]
Message-ID: <20191016131728.GA56859@kroah.com> (raw)
In-Reply-To: <1571230107-8493-1-git-send-email-stefan-gabriel.mirea@nxp.com>

On Wed, Oct 16, 2019 at 03:48:22PM +0300, Stefan-Gabriel Mirea wrote:
> Hello,
> 
> NXP's S32V234[1] ("Treerunner") vision microprocessors are targeted for
> high-performance, computationally intensive vision and sensor fusion
> applications that require automotive safety levels. They include leading
> edge Camera Vision modules like APEX-2, ISP and GPU. The S32V234-EVB and
> S32V234-SBC boards are available for customer evaluation.
> 
> The following patch series introduces minimal enablement support for the
> NXP S32V234-EVB2[2] board, which leverages most of the SoC capabilities.
> Up to v2, this series also included the fsl_linflexuart driver, which has
> been included in Linux 5.4-rc1[3].
> 
> In the future, we aim to submit multiple drivers upstream, which can be
> found in the kernel of our Auto Linux BSP[4] ("ALB"), starting with basic
> pinmuxing, clock and uSDHC drivers.
> 
> For validation, you can use the U-Boot bootloader in the ALB[5], which we
> build and test with our patched version of the Linaro GCC 6.3.1 2017.05
> toolchain for ARM 64-bit, with sources available on [6].
> 
> Changes in v7:
> * Rebase the patch 'serial: fsl_linflexuart: Be consistent with the name'
>   on the tty-next branch in Greg's tty git tree.

I've taken patch 3 in my tty-next tree.  The others should probably go
through an arm-specific tree, right?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Stefan-Gabriel Mirea <stefan-gabriel.mirea@nxp.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, corbet@lwn.net,
	catalin.marinas@arm.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, leoyang.li@nxp.com,
	robh+dt@kernel.org, linux-serial@vger.kernel.org,
	jslaby@suse.com, shawnguo@kernel.org, will@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 0/5] Add initial support for S32V234-EVB
Date: Wed, 16 Oct 2019 06:17:28 -0700	[thread overview]
Message-ID: <20191016131728.GA56859@kroah.com> (raw)
In-Reply-To: <1571230107-8493-1-git-send-email-stefan-gabriel.mirea@nxp.com>

On Wed, Oct 16, 2019 at 03:48:22PM +0300, Stefan-Gabriel Mirea wrote:
> Hello,
> 
> NXP's S32V234[1] ("Treerunner") vision microprocessors are targeted for
> high-performance, computationally intensive vision and sensor fusion
> applications that require automotive safety levels. They include leading
> edge Camera Vision modules like APEX-2, ISP and GPU. The S32V234-EVB and
> S32V234-SBC boards are available for customer evaluation.
> 
> The following patch series introduces minimal enablement support for the
> NXP S32V234-EVB2[2] board, which leverages most of the SoC capabilities.
> Up to v2, this series also included the fsl_linflexuart driver, which has
> been included in Linux 5.4-rc1[3].
> 
> In the future, we aim to submit multiple drivers upstream, which can be
> found in the kernel of our Auto Linux BSP[4] ("ALB"), starting with basic
> pinmuxing, clock and uSDHC drivers.
> 
> For validation, you can use the U-Boot bootloader in the ALB[5], which we
> build and test with our patched version of the Linaro GCC 6.3.1 2017.05
> toolchain for ARM 64-bit, with sources available on [6].
> 
> Changes in v7:
> * Rebase the patch 'serial: fsl_linflexuart: Be consistent with the name'
>   on the tty-next branch in Greg's tty git tree.

I've taken patch 3 in my tty-next tree.  The others should probably go
through an arm-specific tree, right?

thanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-10-16 13:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 12:48 [PATCH v7 0/5] Add initial support for S32V234-EVB Stefan-Gabriel Mirea
2019-10-16 12:48 ` Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 1/5] dt-bindings: arm: fsl: Add the S32V234-EVB board Stefan-Gabriel Mirea
2019-10-16 12:48   ` Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 2/5] arm64: Introduce config for S32 Stefan-Gabriel Mirea
2019-10-16 12:48   ` Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 3/5] serial: fsl_linflexuart: Be consistent with the name Stefan-Gabriel Mirea
2019-10-16 12:48   ` Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 4/5] arm64: dts: fsl: Add device tree for S32V234-EVB Stefan-Gabriel Mirea
2019-10-16 12:48   ` Stefan-Gabriel Mirea
2019-10-26 13:42   ` Shawn Guo
2019-10-26 13:42     ` Shawn Guo
2019-10-16 12:48 ` [PATCH v7 5/5] arm64: defconfig: Enable configs for S32V234 Stefan-Gabriel Mirea
2019-10-16 12:48   ` Stefan-Gabriel Mirea
2019-10-16 13:17 ` Greg KH [this message]
2019-10-16 13:17   ` [PATCH v7 0/5] Add initial support for S32V234-EVB Greg KH
2019-10-16 16:54   ` Stefan-gabriel Mirea
2019-10-16 16:54     ` Stefan-gabriel Mirea
2019-10-26 13:26     ` Shawn Guo
2019-10-26 13:26       ` Shawn Guo
2019-10-26 15:12       ` Stefan-gabriel Mirea
2019-10-26 15:12         ` Stefan-gabriel Mirea
2019-10-26 13:44 ` Shawn Guo
2019-10-26 13:44   ` Shawn Guo

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=20191016131728.GA56859@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jslaby@suse.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=stefan-gabriel.mirea@nxp.com \
    --cc=will@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.