Re: [linux-yocto] [linux-yocto-dev standard/xlnx-soc] xlnx-soc: SDK patches for kernel v5.5
Hi Michal, On 1/20/20 2:39 PM, Michal Simek wrote: On 18. 01. 20 0:53, Bruce Ashfield wrote: On Tue, Jan 14, 2020 at 9:38 PM Quanyang Wang wrote: Hi Bruce & Michal, Would you please help to remove the obsolete branch standard/xlnx-soc in linux-yocto-dev and apply these patches for v5.5 as below to the new branch standard/xlnx-soc? All patches are picked up from v5.4 linux-yocto-dev/standard/xlnx-soc, unless the commit "spi: zynq-qspi: use SDK driver to overwrite mainline driver". In v5.4 kernel, I reverted all mainline patch for spi-zynq-qspi.c and then apply SDK patches. Now in v5.5, since mainline add many patches to this .c file, so I make the patch as above to directly replace spi-zynq-qspi.c with SDK's. At a glance, these look ok to me. But we need to wait to hear from Michal. As you know we are reviewing all patches for v5.4 also with adding more details. It means you can do what you think is best for yocto but in future we will release new v5.4 rebased tree. Not sure how this should be handled in yocto. For now, I still apply xilinx v4.19 SDK patches to v5.5 since v5.4 xilinx SDK are not released. Once they are released , I will switch to these v5.4 SDK patches and apply them to the next yocto kernel version (maybe v5.6). Thanks, Quanyang Thanks, Michal -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8345): https://lists.yoctoproject.org/g/linux-yocto/message/8345 Mute This Topic: https://lists.yoctoproject.org/mt/69710186/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto-dev standard/xlnx-soc] xlnx-soc: SDK patches for kernel v5.5
On 18. 01. 20 0:53, Bruce Ashfield wrote: > On Tue, Jan 14, 2020 at 9:38 PM Quanyang Wang > wrote: >> >> Hi Bruce & Michal, >> >> Would you please help to remove the obsolete branch standard/xlnx-soc in >> linux-yocto-dev >> and apply these patches for v5.5 as below to the new branch >> standard/xlnx-soc? >> >> All patches are picked up from v5.4 linux-yocto-dev/standard/xlnx-soc, >> unless the commit >> "spi: zynq-qspi: use SDK driver to overwrite mainline driver". >> >> In v5.4 kernel, I reverted all mainline patch for spi-zynq-qspi.c and then >> apply SDK patches. >> Now in v5.5, since mainline add many patches to this .c file, so I make the >> patch as above to >> directly replace spi-zynq-qspi.c with SDK's. > > At a glance, these look ok to me. > > But we need to wait to hear from Michal. As you know we are reviewing all patches for v5.4 also with adding more details. It means you can do what you think is best for yocto but in future we will release new v5.4 rebased tree. Not sure how this should be handled in yocto. Thanks, Michal -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8344): https://lists.yoctoproject.org/g/linux-yocto/message/8344 Mute This Topic: https://lists.yoctoproject.org/mt/69710186/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [kernel-cache][PATCH 2/3] features/intel-pinctrl: remove CONFIG_GPIO_LYNXPOINT
Hi Bruce, I see you also merged this patch to branch yocto-5.2 of kernel-cache. However, I found no corresponding kernel changes in linux-yocto v5.2. So, currently kernel v5.2 uses GPIO_LYNXPOINT, and yocto-kernel-cache uses PINCTRL_LYNXPOINT. Thanks, Yongxin > -Original Message- > From: linux-yocto@lists.yoctoproject.org [mailto:linux- > yo...@lists.yoctoproject.org] On Behalf Of Bruce Ashfield > Sent: Thursday, January 16, 2020 03:19 > To: Tim Orling > Cc: Naveen Saini; Linux Yocto > Subject: Re: [linux-yocto] [kernel-cache][PATCH 2/3] features/intel- > pinctrl: remove CONFIG_GPIO_LYNXPOINT > > Sorry for the delay, 5.4 and 5.5 were consuming a lot of my time. > > This is now merged. My SRCREV updates will follow, but since you have > your own .. you can pickup the changes whenever you want. > > Bruce > > On Thu, Jan 9, 2020 at 10:09 PM Tim Orling > wrote: > > > > > > > > > On Jan 9, 2020, at 6:12 PM, Naveen Saini > wrote: > > > > > > Lynxpoint GPIO driver moved under Intel pin control umbrella for > > > further transformation to a real pin control driver. > > > > > > CONFIG_GPIO_LYNXPOINT renamed to PINCTRL_LYNXPOINT > > > > > > https://github.com/intel/linux-intel-lts/commit/cb81404ffe750270f072 > > > d1fc839a4afe288046f3 > > > > > > > Thank you. This was on my TODO list,. > > > > > Signed-off-by: Naveen Saini > > > > Acked-by: Tim Orling > > > > > --- > > > features/intel-pinctrl/intel-pinctrl.cfg | 1 + > > > features/soc/skylake/skylake.cfg | 1 - > > > 2 files changed, 1 insertion(+), 1 deletion(-) > > > > > > diff --git a/features/intel-pinctrl/intel-pinctrl.cfg > > > b/features/intel-pinctrl/intel-pinctrl.cfg > > > index 6d46eec7..406cf3ce 100644 > > > --- a/features/intel-pinctrl/intel-pinctrl.cfg > > > +++ b/features/intel-pinctrl/intel-pinctrl.cfg > > > @@ -11,3 +11,4 @@ CONFIG_PINCTRL_DENVERTON=y > > > CONFIG_PINCTRL_GEMINILAKE=y CONFIG_PINCTRL_ICELAKE=y > > > CONFIG_PINCTRL_LEWISBURG=y > > > +CONFIG_PINCTRL_LYNXPOINT=m > > > diff --git a/features/soc/skylake/skylake.cfg > > > b/features/soc/skylake/skylake.cfg > > > index b2140b05..34066635 100644 > > > --- a/features/soc/skylake/skylake.cfg > > > +++ b/features/soc/skylake/skylake.cfg > > > @@ -24,7 +24,6 @@ CONFIG_CRC8=m > > > CONFIG_BT_HCIUART=m > > > CONFIG_BT_HCIUART_INTEL=y > > > CONFIG_USB_EHCI_PCI=y > > > -CONFIG_GPIO_LYNXPOINT=m > > > > > > # Other misc support > > > CONFIG_INTEL_MEI_TXE=m > > > -- > > > 2.17.1 > > > > > > > > > > > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8342): https://lists.yoctoproject.org/g/linux-yocto/message/8342 Mute This Topic: https://lists.yoctoproject.org/mt/69593269/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] v5.2.x - stable updates comprising v5.2.30
Bruce, Yocto kernel folks: Here is the next 5.2.x stable update "extension" primarily created for the Yocto project, as the 9th v5.2.x post-EOL release. This release is "normal" -- where it consists of an audit of what went into 5.3.1[56] releases, resulting in about 230 commits for v5.2.30. I've put this 5.2.30 queue through the usual testing; build testing on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis and finally some sanity runtime tests on x86-64. I did the signed tag just as per the previously released versions. Please find a signed v5.2.27 tag using this key: http://pgp.mit.edu/pks/lookup?op=vindex=0xEBCE84042C07D1D6 in the repo in the kernel.org directory here: https://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git/?h=linux-5.2.y git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git for merge to standard/base in linux-yocto-5.2 and then out from there into the other base and BSP branches. For those who are interested, the evolution of the commits is here: https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-5.2.git/ This repo isn't needed for anything; it just exists for transparency and so people can see the evolution of the raw commits that were originally selected to create this 5.2.x release. Paul. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8341): https://lists.yoctoproject.org/g/linux-yocto/message/8341 Mute This Topic: https://lists.yoctoproject.org/mt/69920126/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
