Open Source Summit Japan & Automotive Linux Summit 2017

LSTI Presence at Open Source Summit Japan & Autotive Linux Summit 2017

LTSI Session:
"Using Long Term Stabel Kernel for Automotive"
Speaker: Tsugikazu Shibata (NEC)
Event: Automotive Linux Summit
Date & Time: 2:50pm on June 2nd

You can see summary of the session here.

LTSI Workshop 
Date & Time: June 2nd, 2017 start from 4pm
Venue: Room2 on the 3rd Floor
We would like to take advantage of this opportunity to discuss about the future requirements to the Linux & LTSI kernel with the attendees.
Therefore, we would like to have a BoF style meeting to discuss on  the future demand/requirements for Linux Kernel from the industry.
The areas of new requirements can be vary, but we can foresee that there would be demands to include the features such as, container, virtualization, SIL, Real Time, IPv6 to the Kernel.

So we would like to welcome those who wish to share your thoughts (or hearing someone's thoughts) in the area mentioned above.
Of course, the recommended agenda is not limited to above! If you have ANY topics you wish to share and discuss with LTSI community, please come around!!

In the meantime, we will also be talking about the development schedule of the new release of LTSI Kernel. 




LTSI-3.14 Release Note

LTSI Kernel Maintainer Greg Kroah-Hartman on Jan. 9 released the latest version of the LTSI Kernel (3.14.28-LTSI).

The following are the changes that have been merged for each release.


  • ktap 0.4, a lightweight script-based dynamic tracing tool for Linux was back ported. Please visit  for more information.


  • Intel Low Power Sub-system (LPSS) PWM, found in Intel Baytrail & Braswell SoC. The PWM driver supports both PCI and ACPI enumeration. (The clock rate for PWM is set through driver data because the PWM does not have any clock dividers or gate for varying the clock). 
  • I2C/SMBus i801, added PCI Device ID for Intel Baytrail, Braswell & Intel Wildcat Point (PCH).
  • LPC ICH MFD has various features included in LTSI v3.14, listed below:

       + supports PCI enumeration for Intel Braswell SoC and Intel 9 Series PCH.

       + iTCO v3 support for Intel Avoton SoC.

       + GPIO support for Intel Avoton SoC, Panther Point PCH and NM10 chipset

  • Watchdog iTCO, the driver is now at v1.11 version which supports v3 silicon with slightly different iTCO functionality and register maps change. For details, please see "watchdog: iTCO_wdt: Add support for v3 silicon.”


Renesas R-CarH2 Lager Board and R-CarM2 Koelsch board are now supported.

    • Renesas R-Car M2/MH latest device support codes are added.
    • Expanded DTS (Device Tree Support).


If you wish to find more detailed information on the differences between 3.14-lts and 3.14-ltsi please download DIFF-STATS FILE that shows the exact difference between 3.14.28-lts and 3.14.28-ltsi.

With these releases, 900 upstream bug/security fixes have been applied. This should result in a reduction of in-house maintenance costs for the companies that use the LTSI Kernel.

Quick Guide to Get Ready for LTSI 3.10


Noriaki's picture
The 3.11 kernel release is on Sept. 2. So I think it is a good time to update the development schedule of LTSI 3.10 and provide a brief guideline to participate in the LTSI 3.10 development process.
Development Schedule:
LTSI 3.10 Merge Window Opens:
LTSI merge window should open on the date that the 3.12 MAINLINE KERNEL is RELEASED, WHICH IS THE DATE 3.10 WILL BECOME FORMALLY LTS.
Since the 3.11 mainline kernel was released on Sept. 2, and the new kernels come out roughly around every 2 months, we assume that we can open the merge window around early November.
The Merge Window should open for 60 days.
Testing Period:
After the 60-day merge period, we will take a 30-day testing period.
Based on the assumption that the merge period would start Nov. 1, the testing period will start Jan. 1 and end Jan. 30, 2014.
So we can assume that we can release LTSI 3.10 around the early to mid-February timeframe.
What to do to participate:
Here is the list of tips to participate in the LTSI 3.10 development process and take full advantage of LTSI project.
  1. Check what is in the 3.11 kernel to see if there are any new features, functions, device drivers etc that you would like to add on top of LTS-3.10.
  2. Keep your eyes on 3.12 kernel development to see if any new features, functions, device drivers etc, that you wish to add on top of LTS-3.10, are merging to the 3.12 mainline kernel.
  3. If we are lucky enough, we can also back port the patch from 3.13 kernel to this LTSI kernel development cycle.
  4. Throw your patch over to the mailing list (
  5. We basically back port only the patches that are previously accepted to the main line kernel. In the meantime if you have in-house patches that are NOT merged with the mainline kernel yet, please don't be discouraged, but send your patches anyway. We have LTSI Patchwork (, which is a collection of patches that are submitted to LTSI mailing list. From this patch work, you can cherry pick the patches you wish to add on to LTSI-3.10 on your own.
If you have any questions, please free free to contact the LTSI Project team: (

Let's Work Together for LTSI 3.10


Noriaki's picture

Greg Kroah-Hartman, the maintainer of LTS and LTSI, announced 2 weeks ago on his blog that the next LTS and LTSI version will be 3.10. It is now time for the industry to get ready for the LTSI 3.10 release.

For those of you who are not fully aware of the LTSI release process, I would like to take this opportunity to elaborate on what you need to do to prepare for the new LTSI release.

1) The 3.10-LTSI schedule is now under discussion among the LTSI project team. We should be able to announce the schedule around the early September time frame.

2) The LTSI merge window will be open for 60 days or so, and most likely, it will be in the October-November time frame. But, again, we will formally announce the merge window schedule in September.

With this schedule, you should be able to merge the new functions that will be merged into the 3.11 and 3.12 upstream kernels.

3) After the 60-day merge window period, LTSI will take a 30-day testing period. Most likely during December.

With this scenario, it looks like around next January we will see the next LTSI kernel released. Let's work together to build a good common industry kernel which everybody can get benefit from!

Please stay tuned for further announcements!

New Long Term Stable Initiative (LTSI) Linux Kernel Released

LTSI Kernel Maintainer Greg Kroah-Hartman has released the latest version of LTSI Kernel (3.0.79-LTSI and 3.4.46-LTSI) on May 21.


The followings are the changes that have been merged for each release.



Update to 3.0.79 kernel release

New kzm9g board-specific patches

Updated documentation



Update to 3.4.46

Updated documentation

af_bus Kconfig dependancy fixed

armadillo800 patches added

Clock bugfix

USB gadget fixes

lttng bugfixes

shmobile fixes

marzen i2c and sata support added

arm smp updates

irqchip patches added


With these releases, a large amount of upstream bug/security fixes have been applied (1,368 with 3.0,79-LTSI; 944 with 3.4.46-LTSI). This should result in a dramatic reduction of in-house maintenance costs for the companies who use LTSI Kernel.


In addition to the back port of bug/security fixes, LTSI has many patch collections now that are not merged and can be very useful and easy to apply to products.


A couple resources that can be helpful when applying these patches to your products:


LTSI Patch Collection


How to adopt LTSI Kernel to your products:


The new version of LTS (hence LTSI) kernel version is expected to be selected within a few months, followed shortly after by the the opening of the merge window of the new LTSI Kernel.


If any of your organizations would like your patches to be merged into the latest LTS (and LTSI) Kernel, please look for the new announcement in a few months or so.


Also, the 3.4 series will be maintained for another year. If you wish to merge your patches to 3.4, we always welcome you codes.


If there is anything we can help you, please contact us!

LTSI v3.4 Released

Part of supporting the demand for Linux in consumer electronics is ensuring there is a common Linux base that is maintained and supported for the typical lifetime of a consumer device, usually two years, and that supports a large variety of consumer electronics products. The Linux kernel is released at such a rapid pace that until now, device makers were doing significant back-porting, bug testing and driver development on their own, which carried substantial cost in terms of time-to-market, as well as development and engineering effort to maintain those custom kernels.

The Linux Foundation's Consumer Electronics (CE) workgroup founded the Long Term Support Initiative (LTSI) to address this issue collaboratively. Today, the project provides for both an annual release of a Linux kernel suitable for supporting the lifespan of consumer electronics products and regular updates of those releases for two years. Linux kernel maintainer Greg Kroah-Hartman oversees this maintenance and the LTSI kernel tree for this industry-wide project created and supported by Hitachi, LG Electronics, NEC, Panasonic, Qualcomm Atheros, Renesas Electronics Corporation, Samsung Electronics, Sony and Toshiba. 

This week the CE working group is releasing the LTSI 3.4 kernel. It is based on the Linux 3.4.25 kernel release and includes a number of backported features from newer  releases.

 Highlights from today's release include: 

* The Contiguous Memory Allocator (CMA), which is extremely useful for embedded devices that have very limited hardware resources and will better handle the large memory requirements of multimedia applications. CMA originally was merged into the 3.4.0 kernel release, but its functionality was quite limited. Since then, the feature has been significantly improved in the releases and those fixes have been added to the LTSI 3.4 kernelrelease. For more information about this kernel option, please visit 

* AF_BUS, a kernel-based implementation of the D-Bus protocol. This feature was created for systems that required a faster D-Bus speed than the existing userspace method could provide, specifically the automotive entertainment systems. For more information about this feature, please see 

* CoDel (controlled delay), a transmission algorithm that optimizes TCP/IP network buffer control, is backported for LTSI 3.4. This is a feature used to help control the "buffer bloat" problem that has been identified by the networking community as an issue that all devices need to be aware of. This feature was backported from the 3.5.0  kernel.orgrelease.  For more information about it, please see this post. 

Platform specific board support was backported from newer kernel versions, allowing the Armadillo 800, AT91, kzm9d, kzm9g, and Marzen platforms to work properly with this release.

For more information about LTSI and the latest release, please visit the LTSI website. 

Syndicate content