Linux dev-4.19

Tomer Maimon tmaimon77 at
Wed Dec 12 23:05:25 AEDT 2018

Hi Joel,

First, I like to apologize that there is many patches of NPCM to add, so it
look quite messy...

After adding the below our customers could use (in most cases) OpenBMC
linux tree and not Nuvoton Linux tree.

We have the following patches to add:

·         Patches already have accepted.

·         Patches on upstream process.

·         PCI Mailbox patches - The PCI mail box will not upstream, because
it not build with the mailbox driver interface,

but still OpenBMC have an application to use the miscellaneous mailbox but
still OpenBMC have an application

to use the miscellaneous mailbox.

·         ETHERNET MAC CONTROLLER (EMC) patches – the patches is on final
stage of upstream work, but it is very important to us that the patches will

add now because costumer requests that are using the OpenBMC linux.

·         Device tree and defconfig patches – in our github it is a bunch
of patches, so I prefer to send you one patch to each topic.

I will start to send device tree update to Rob soon.

*Commit upstream to kernel 4.20*

*hwmon: (npcm-750-pwm-fan) Change initial pwm target to 255  *

*Commits will upstream to kernel 4.21*

*dt-binding: spi: add NPCM PSPI controller documentation  *

*spi: npcm: add NPCM PSPI controller driver  *

*spi: npcm: fix u32 csgpio being checked for less than zero  *

*spi: npcm: fix platform_no_drv_owner.cocci warnings  *

*spi: npcm: Fix an error code in the probe function  *

*spi: npcm: Fix uninitialized variable warning  *

*spi: npcm: Modify pspi send function  *

*spi: Update NPCM PSPI controller documentation  *

*pinctrl: nuvoton: modify NPCM7xx pin configuration function  *

*watchdog: npcm: Modify npcm watchdog kconfig arch parameter  *

*Commits on **upstream* *process*

*dt-binding: mtd: add NPCM FIU controller*


*mtd: spi-nor: add NPCM FIU controller driver*

*dt-bindings: i2c: npcm7xx: add binding for i2c controller*

*i2c: npcm: driver for Poleg i2c controller*

*dt-binding: bmc: Add NPCM7xx LPC BPC documentation*

*misc: npcm7xx-lpc-bpc: add NPCM7xx BIOS post code driver*

*misc: bpc: modify remove function in npcm7xx bpc driver*

*PCI mail box commits*

*dt-binding: bmc: add npcm7xx pci mailbox document*

*misc: mbox: add npcm7xx pci mailbox driver*

*EMC net commits*

*net: npcm: add NPCM7xx Ethernet MAC controller*

*dt-binding: net: document NPCM7xx EMC DT bindings*

Waiting to your approval, Thanks a lot.



On Tue, 4 Dec 2018 at 05:20, Joel Stanley <joel at> wrote:

> Hello Dave,
> On Tue, 4 Dec 2018 at 13:43, David Thompson <dthompson at>
> wrote:
> >
> > Since 4.19 kernel is deemed "longterm" with a projected EOL of Dec 2020,
> is the plan to keep OpenBMC on this kernel version for a while?
> I have no plans to stay on a given release once the next is out at
> this stage. My goal is to get all of the code upstream, so that I
> don't need to maintain any out of tree patches, and then system
> integrator can pick whichever kernel they want for their system.
> It would be straight forward to maintain a stable tree once the "dev"
> tree has moved on past 4.19. I have some ideas on how this could work
> if you are interested.
> > I've yet to upstream any of my changes, my bad, and as a
> > result I've gone through four kernel upgrades this year
> > {4.13, 4.17, 4.18, and now 4.19}.
> I encourage you to get your patches on the list! Do you have a run
> down of what you keep out of tree?
> Cheers,
> Joel
> > I'm curious about the OpenBMC kernel upgrade strategy,
> > esp. after 4.19.
> >
> > Regards,
> > - Dave
> >
> > -----Original Message-----
> > From: openbmc < at>
> On Behalf Of Joel Stanley
> > Sent: Monday, December 3, 2018 5:05 PM
> > To: Amithash Prasad <amithash at>
> > Cc: OpenBMC Maillist <openbmc at>; vijaykhemka at
> > Subject: Re: Linux dev-4.19
> >
> > On Tue, 4 Dec 2018 at 07:25, Amithash Prasad <amithash at> wrote:
> > >
> > > >> I have couple of NCSI patch which were up streamed last week in
> linux-next kernel. Will those be part of this 4.19 kernel in openbmc or
> what is procedure to pull those patches in openbmc build. As these are
> required for Meta-facebook build with networking working.
> > > Joel,
> > >
> > > Thanks for cherry-picking a few of the NCSI changes into dev-4.19!
> Along with these, can we get a couple more cherry-picked into dev-4.19?
> > >
> > > One patch from linux-next:
> > >
> > > mmit/net/ncsi?h=next-20181203&id=16e8c4ca21a238cdf0355475bf15bd72e92fe
> > > b8f
> > >
> > > One merged patch to bring in the Tiogapass device tree:
> > >
> > > t/arch/arm/boot/dts/aspeed-bmc-facebook-tiogapass.dts?id=3368e06e2a91a
> > > 65cff59e520acc51b9adf4900bf
> >
> > Nice work. This is a great way to request the patches get merged. I'm
> happy because they're already on their way upstream, and the URLs with SHAs
> make it easy for me to cherry pick.
> >
> > Merged!
> >
> > Cheers,
> >
> > Joel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-arm-npcm-add-configuration-for-EVB-based-NPCM7xx-BMC.patch
Type: application/octet-stream
Size: 3526 bytes
Desc: not available
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-dts-npcm7xx-Modify-NPCM7xx-device-tree.patch
Type: application/octet-stream
Size: 87682 bytes
Desc: not available
URL: <>

More information about the openbmc mailing list