linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] updates to soc/fsl drivers for v4.14
Date: Mon, 23 Oct 2017 09:11:16 +0800	[thread overview]
Message-ID: <20171023011115.GF8700@dragon> (raw)
In-Reply-To: <AM4PR0401MB1699CA477F157A2C7618492D8F430@AM4PR0401MB1699.eurprd04.prod.outlook.com>

Hi Leo,

On Fri, Oct 20, 2017 at 10:04:07PM +0000, Leo Li wrote:
> > - We should come to an agreement on how we do these in the future.
> >   Usually I expect any Freescale/NXP/ARM changes to come through the
> >   i.MX maintainers (Shawn and Sascha), not directly from other developers.
> >   There is usually some degree of coordination required between the
> >   SoC drivers and the DT files and platform code, so it's really best to
> >   have someone be aware of all the components, and I prefer to have
> >   a smaller number of people sending me pull requests. If you already
> >   talked to Shawn about it and he prefers you to send the pull request
> >   to us directly, that's fine too, but please at least keep him on Cc.
> 
> I would like to share some more background information on this.  The microcontroller business(produces i.mx product line) and the networking business(produces qoriq product line) are completely two different business units within Freescale/NXP.  There are separate hardware design teams and software development teams due to the different targeting markets.  The hardware design are almost completely different.  Historically, the microcontroller product line focused on m68k and armv7 architectures while the networking product line focused on PowerPC architecture and recently moved to ARMv8 architecture.  There are surely some IP sharing but only on basic peripheral devices such as i2c, usb and etc.   But due to the different targeting markets most of the peripheral devices are very different.  For example this DPAA framework, network interfaces and a lot of other accelerators will never be used in the i.mx products.  On the core architecture side we are working on SBSA compliance hardware and SBBA compliance software with UEFI and ACPI in the picture, which would be a overkill for microcontrollers.    In my opinion, the differences between i.MX and QorIQ products could be even bigger than the difference between QorIQ products and some server focused ARMv8 SoCs from other vendors.  The synergy for combining these two will be very limited.
> 

I'm fine with you send drivers/soc/fsl changes to Arnd directly, since
we already have separate folders (drivers/soc/imx vs. drivers/soc/fsl)
for i.MX and QorIQ.  But as Arnd suggested, please keep me on copy, so
that I can be aware of the changes which might be somehow related to
arch/arm64/boot/dts/freescale/ changes that I'm currently taking care
of.  Thanks.

Shawn

  reply	other threads:[~2017-10-23  1:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 19:37 [GIT PULL] updates to soc/fsl drivers for v4.14 Li Yang
2017-10-03  9:55 ` Madalin-cristian Bucur
2017-10-03 16:38   ` Leo Li
2017-10-20 21:01 ` Arnd Bergmann
2017-10-20 22:04   ` Leo Li
2017-10-23  1:11     ` Shawn Guo [this message]
2017-10-23 16:26       ` Leo Li
2017-10-27  7:47       ` Arnd Bergmann
2017-10-27 17:33         ` Leo Li
2017-10-30  9:15           ` Arnd Bergmann

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=20171023011115.GF8700@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).