Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/1] sound: soc: xilinx: give a name to stream_name in xilinx_dp_dai_links
On Mon, Nov 11, 2019 at 5:30 AM wrote: > > From: Quanyang Wang > > Hi Bruce & Michal, > > When running "aplay -l" in zcu102 board, there will be a "(null)" in output: > root@xilinx-zynqmp:~# aplay -l > List of PLAYBACK Hardware Devices > card 0: monitor [DisplayPort monitor], device 0: (null) > xilinx-dp-snd-codec-dai-0 [(null) xilinx-dp-snd-codec-dai-0] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: monitor [DisplayPort monitor], device 1: (null) > xilinx-dp-snd-codec-dai-1 [(null) xilinx-dp-snd-codec-dai-1] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > > Just give a name to .stream_name, not to fix any issue but just decorate the > output. > After applying this patch, the output becomes: > root@xilinx-zynqmp:~# aplay -l > List of PLAYBACK Hardware Devices > card 0: monitor [DisplayPort monitor], device 0: xilinx-dp0 > xilinx-dp-snd-codec-dai-0 [xilinx-dp0 xilinx-dp-snd-codec-dai-0] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: monitor [DisplayPort monitor], device 1: xilinx-dp1 > xilinx-dp-snd-codec-dai-1 [xilinx-dp1 xilinx-dp-snd-codec-dai-1] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > > Would you please help review and merge these patches to linux-yocto > v5.2/standard/xlnx-soc branch? > I see the review is in, so this is now merged to the soc branch Bruce > Quanyang Wang (1): > sound: soc: xilinx: give a name to stream_name in xilinx_dp_dai_links > > sound/soc/xilinx/xilinx-dp-card.c | 2 ++ > 1 file changed, 2 insertions(+) > > -- > 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 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: Revert "cgroup: Disable cgroup "memory" by default"
On Tue, Nov 19, 2019 at 11:43 PM wrote: > > From: Limeng > > Hi Bruce, > > After kts test, we found out cgroup case failed. > The reason is that raspberrypi SDK kernel disable cgroup "memory" feature. > > It is not reasonable to disable a common cgroup feature. > Because there is enough memory on latest raspberrypi 4 platform. > reverted. Bruce > Could you please help to merge this patch into branch standard/bcm-2xxx-rpi, > linux-ycoto-dev kernel. > > diffstat info ad below: > > cgroup.c | 30 -- > 1 file changed, 30 deletions(-) > > > thanks, > Limeng -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-5.2]: [kernel v5.2/standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: fix build warning
On Fri, Nov 15, 2019 at 4:20 AM wrote: > > From: Limeng > > Hi Bruce, > > I fix some building warnings for raspberrypi plarform. > > Could you please help to merge the 2 patches into branch > v5.2/standard/bcm-2xxx-rpi, linux-ycoto kernel. > > diffstat info ad below: > Merged! Bruce > dma/bcm2835-dma.c|2 +- > usb/host/dwc_otg/dwc_otg_hcd_linux.c |4 ++-- > usb/host/dwc_otg/dwc_otg_pcd_intr.c |6 -- > 3 files changed, 7 insertions(+), 5 deletions(-) > > thanks, > Limeng -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [v5.2 preempt-rt][PATCH] ptrace: Remove unmatched preempt_count() issue in ptrace_stop
On Wed, Nov 13, 2019 at 12:52 AM Yongxin Liu wrote:
>
> Upstream commit 53da1d9456fe7f8 ("fix ptrace slowness") introduced
> preempt_disable() and preempt_enable_no_resched() in function
> ptrace_stop(), and they should be used together.
>
> In RT kernel, commit 500d5c546e46 ("signal: Revert ptrace preempt
> magic") reverted commit 53da1d9456fe7f8. To make Yocto RT kernel the
> same as upstream RT kernel, remove preempt_enable_no_resched(), in
> stread of adding preempt_disable().
>
merged.
Bruce
> Signed-off-by: Yongxin Liu
> ---
> kernel/signal.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel/signal.c b/kernel/signal.c
> index 4e7dddf6b3a9..7bf4b399d307 100644
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2243,7 +2243,6 @@ static void ptrace_stop(int exit_code, int why, int
> clear_code, kernel_siginfo_t
>
> read_unlock(_lock);
> cgroup_enter_frozen();
> - preempt_enable_no_resched();
> freezable_schedule();
> cgroup_leave_frozen(true);
> } else {
> --
> 2.14.4
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [yocto-kernel-cache yocto-5.2/master][PATCH] arm-versatile-926ejs: Optimize for performance -O2 to fix runtime error
On Wed, Nov 13, 2019 at 1:22 AM wrote: > > From: He Zhe > > arm-versatile-926ejs systems hang at random places when > CONFIG_CC_OPTIMIZE_FOR_SIZE is enabled. > standard.scc -> arm.scc -> arm.cfg -> CONFIG_CC_OPTIMIZE_FOR_SIZE=y > Use CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE instead before we find the root cause. > This is fine with me .. I'd rather have the boot work while we keep looking. merged Bruce > Signed-off-by: He Zhe > --- > bsp/arm-versatile-926ejs/arm-versatile-926ejs.cfg | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/bsp/arm-versatile-926ejs/arm-versatile-926ejs.cfg > b/bsp/arm-versatile-926ejs/arm-versatile-926ejs.cfg > index e3fa6e4c..99f8aeb7 100644 > --- a/bsp/arm-versatile-926ejs/arm-versatile-926ejs.cfg > +++ b/bsp/arm-versatile-926ejs/arm-versatile-926ejs.cfg > @@ -73,3 +73,5 @@ CONFIG_FRAME_POINTER=y > > # CONFIG_NO_HZ is not set > # CONFIG_HIGH_RES_TIMERS is not set > + > +CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y > -- > 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 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [yocto-kernel-cache][yocto-5.2/master][PATCH] features/wifi: Change ATH9K_HTC, RTL8187 and RTL_CARDS to be modules
On Wed, Nov 13, 2019 at 3:42 AM Yongxin Liu wrote: > > CONFIG_ATH9K_HTC, CONFIG_RTL8187 and CONFIG_RTL_CARDS have dependency > on CONFIG_MAC80211 which is set to "m". > merged. Bruce > Signed-off-by: Yongxin Liu > --- > features/wifi/atheros-usb.cfg | 2 +- > features/wifi/realtek-usb.cfg | 4 ++-- > 2 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/features/wifi/atheros-usb.cfg b/features/wifi/atheros-usb.cfg > index 38280940..4b58bb7f 100644 > --- a/features/wifi/atheros-usb.cfg > +++ b/features/wifi/atheros-usb.cfg > @@ -5,5 +5,5 @@ CONFIG_WLAN_VENDOR_ATH=y > CONFIG_ATH9K=m > CONFIG_ATH9K_RFKILL=y > CONFIG_ATH9K_PCOEM=y > -CONFIG_ATH9K_HTC=y > +CONFIG_ATH9K_HTC=m > > diff --git a/features/wifi/realtek-usb.cfg b/features/wifi/realtek-usb.cfg > index 98a95c48..bfdd9f47 100644 > --- a/features/wifi/realtek-usb.cfg > +++ b/features/wifi/realtek-usb.cfg > @@ -2,11 +2,11 @@ > CONFIG_WLAN_VENDOR_REALTEK=y > > # rtl818x > -CONFIG_RTL8187=y > +CONFIG_RTL8187=m > > # rtl8xxxu > CONFIG_RTL8XXXU=m > > # rtlwifi > -CONFIG_RTL_CARDS=y > +CONFIG_RTL_CARDS=m > CONFIG_RTL8192CU=m > -- > 2.14.4 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] v5.2.x - stable updates comprising v5.2.23
In message: v5.2.x - stable updates comprising v5.2.23 on 15/11/2019 Paul Gortmaker wrote: > Bruce, Yocto kernel folks: > > Here is the next 5.2.x stable update "extension" primarily created for > the Yocto project, continuing from the first v5.2.22 post-EOL release. > > This 5.2.22 release only contains about 22 mainline commits. Rather > than continue the audit of what went into 5.3.8 - I jumped ahead to > 5.3.11 in order to get the latest CVE embargo commits relating to > iTLB/tsx/TAA, as I assumed they would be of interest to people. > > Folks will find in /sys/devices/system/cpu/vulnerabilities - alongside > spectre and meltdown, new files itlb_multihit and tsx_async_abort, and > can look them up in the documentation for more details. > > I will circle back to 5.3.8+ content for the next v5.2.24 release I'll > be starting shortly. > > The CVE was significant to KVM, and as such, the commits had a fairly > high footprint in that subsystem. I used a code refactoring mainline > commit from between 5.2 and 5.3 in order to enable using the CVE related > KVM commits with as little alteration as possible. Also possibly worth > a mention, is that post-5.2 the main kvm_lock went from being a spinlock > to a mutex. Rather than risk any possible impact to -rt, I simply > retained it being a spin, and adjusted the CVE commits accordingly. > > I've put this 5.2.23 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. > > In addition, since there was a significant KVM footprint in the > changelog, I also built a defconfig with KVM and KVM_INTEL enabled, and > booted that same kernel as host and guest, on both kvm-intel enabled and > older non-kvm-intel enabled systems, and saw no obvious issues. Sounds good. Thanks for the extra testing! This is now merged and pushed. Bruce > > I did the signed tag just as per the previously released versions. > Please find a signed v5.2.23 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. -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-5.2]: [kernel v5.2/standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: dma-direct: Temporary DMA fix on arm64
On Tue, Nov 12, 2019 at 12:09 AM wrote:
>
> From: Limeng
>
> Hi Bruce,
>
> After bts test, we found out dma case failed.
> Because below commit is pushed into mainline kernel
> 66bdb1478fd1("swiotlb: Use dma_direct_supported() for swiotlb_ops")
> But raspberrypi SDK kernel haven't done corresponding modification to
> compatible with mainline
> There is only a Temporary fixing for DMA. So, I got it to fix the DMA
> initialization issue temporarily.
>
> Could you please help to merge this patch into branch
> v5.2/standard/bcm-2xxx-rpi, linux-ycoto kernel.
>
Looks fine to me.
Merged!
Bruce
> diffstat info ad below:
>
> direct.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> thanks,
> Limeng
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] v5.2.x - stable updates comprising v5.2.22
On Tue, Nov 12, 2019 at 1:18 PM Paul Gortmaker wrote: > > [Re: v5.2.x - stable updates comprising v5.2.22] On 10/11/2019 (Sun 22:36) > Bruce Ashfield wrote: > > > This is merged, that being said .. there are a couple of things that > > could use a second set of eyes. > > > > 1) I had a preempt-rt conflict in fs/libfs.c. It looks like > > scan_positives() was introduced. The merge picked up a conflict, when > > really it should have just been the introduction of that new function > > and a drop of the old ones. But again, a 2nd set of eyes to see if I > > read it right would be nice. > > Yes, it seems this -rt commit: > > commit 037e1e5242b669920374c993cace7c3872257747 > Author: Sebastian Andrzej Siewior > Date: Fri Oct 20 11:29:53 2017 +0200 > > fs/dcache: disable preemption on i_dir_seq's write side > > bumps into this stable backport: > > commit 60624198d203847694fe8f637fed6d67d8027370 > Author: Al Viro > Date: Sun Sep 15 12:12:39 2019 -0400 > > Fix the locking in dcache_readdir() and friends > > ...and as usual, the merge conflict isn't really all that informative. > However, if you revert the -rt change, and then merge, and then re-apply > the -rt change, it is more clear. > > In any case, here is a small patch to fixup the current preempt-rt > compile failures against v5.2/standard/preempt-rt/base > Thanks Paul! I've applied and pushed that fixup. Bruce > > diff --git a/fs/libfs.c b/fs/libfs.c > index 81d210ba8e83..7ac2d4bb4735 100644 > --- a/fs/libfs.c > +++ b/fs/libfs.c > @@ -125,8 +125,9 @@ static struct list_head *scan_positives(struct dentry > *cursor, > } > } > spin_unlock(>d_lock); > - dput(last); > - return found; > + dput(*res); > + *res = found; > + return p; > } > > loff_t dcache_dir_lseek(struct file *file, loff_t offset, int whence) -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] v5.2.x - stable updates comprising v5.2.22
On Mon, Nov 11, 2019 at 1:35 AM Quanyang Wang
wrote:
>
> Hi Bruce,
>
> On 11/11/19 11:36 AM, Bruce Ashfield wrote:
> > On Sun, Nov 10, 2019 at 12:05 AM Paul Gortmaker
> > wrote:
> >> Bruce, Yocto kernel folks:
> >>
> >> Here is the first 5.2.x stable update "extension" primarily created for
> >> the Yocto project, continuing from the last v5.2.21 EOL release from the
> >> normal stable-kernel feed/stream.
> >>
> >> As the 1st extension update, it is probably worthwhile to remind people
> >> that the work here is stacked on top of the existing vanilla
> >> linux-stable work and isn't Yocto specific in any way -- other than
> >> filling a need for the Yocto project kernel needs.
> >>
> >> Non Yocto users with a 5.2.x kernel are also encouraged to make use of
> >> the work, just as the 4.8, 4.12 and 4.18 stable extension work done in
> >> the past. Content is chosen by monitoring non-EOL stable releases, CVEs
> >> and similar, and is released in a fashion as close as possible to the
> >> primary stable-kernel feed that people are used to.
> >>
> >> More specifically, for this 5.2.22 release, it contains about 235 mainline
> >> commits based on what was found in 5.3.6 and 5.3.7 stable content.
> >>
> >> I've put this 5.2.22 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.22 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.
> > This is merged, that being said .. there are a couple of things that
> > could use a second set of eyes.
> >
> > 1) I had a preempt-rt conflict in fs/libfs.c. It looks like
> > scan_positives() was introduced. The merge picked up a conflict, when
> > really it should have just been the introduction of that new function
> > and a drop of the old ones. But again, a 2nd set of eyes to see if I
> > read it right would be nice.
> >
> > 2) there was a conflict in v5.2/standard/xlnx-soc in
> > drivers/tty/serial/uartlite.c. There's a minor change in the driver
> > unregistration. I resolved he conflict, but there now might be two
> > unregister calls .. and I'm not sure how well that'll work. I copied
> > Quanyang, to have a look and see if I got it right.
>
> The commit 7dba6bf5f7d8 ("serial: uartlite: fix exit path null pointer")
> should be
>
> dropped because that the commit 4eed93c3703b ("serial-uartlite: Remove
> ULITE_NR_PORTS macro")
>
> which is picked from SDK has moved "uart_unregister_driver" from
> ulite_exit to ulite_remove, and
>
> there is no global variable "ulite_uart_driver" anymore.
>
> Do I need to send a revert patch to revert it in v5.2/standard/xlnx-soc
> branch?
Nope. If it's a clean revert, I'll take care of it locally.
Thanks for taking a look. I'll follow up if something isn't clean
about the revert.
Bruce
>
> Thanks,
>
> Quanyang
>
> >
> > Cheers,
> >
> > Bruce
> >
> >> 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.
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] v5.2.x - stable updates comprising v5.2.22
On Sun, Nov 10, 2019 at 12:05 AM Paul Gortmaker wrote: > > Bruce, Yocto kernel folks: > > Here is the first 5.2.x stable update "extension" primarily created for > the Yocto project, continuing from the last v5.2.21 EOL release from the > normal stable-kernel feed/stream. > > As the 1st extension update, it is probably worthwhile to remind people > that the work here is stacked on top of the existing vanilla > linux-stable work and isn't Yocto specific in any way -- other than > filling a need for the Yocto project kernel needs. > > Non Yocto users with a 5.2.x kernel are also encouraged to make use of > the work, just as the 4.8, 4.12 and 4.18 stable extension work done in > the past. Content is chosen by monitoring non-EOL stable releases, CVEs > and similar, and is released in a fashion as close as possible to the > primary stable-kernel feed that people are used to. > > More specifically, for this 5.2.22 release, it contains about 235 mainline > commits based on what was found in 5.3.6 and 5.3.7 stable content. > > I've put this 5.2.22 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.22 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. This is merged, that being said .. there are a couple of things that could use a second set of eyes. 1) I had a preempt-rt conflict in fs/libfs.c. It looks like scan_positives() was introduced. The merge picked up a conflict, when really it should have just been the introduction of that new function and a drop of the old ones. But again, a 2nd set of eyes to see if I read it right would be nice. 2) there was a conflict in v5.2/standard/xlnx-soc in drivers/tty/serial/uartlite.c. There's a minor change in the driver unregistration. I resolved he conflict, but there now might be two unregister calls .. and I'm not sure how well that'll work. I copied Quanyang, to have a look and see if I got it right. Cheers, Bruce > > 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. -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-5.2]: [kernel v5.2/standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: Revert "cgroup: Disable cgroup "memory" by default"
In message: [linux-yocto-5.2]: [kernel v5.2/standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: Revert "cgroup: Disable cgroup "memory" by default" on 08/11/2019 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > After kts test, we found out cgroup case failed. > The reason is that raspberrypi SDK kernel disable cgroup "memory" feature. > > It is not reasonable to disable a common cgroup feature. > Because there is enough memory on latest raspberrypi 4 platform. > > Could you please help to merge this patch into branch > v5.2/standard/bcm-2xxx-rpi, linux-ycoto kernel. Reverted! Thanks for the details in the cover letter. Bruce > > diffstat info ad below: > > cgroup.c | 30 -- > 1 file changed, 30 deletions(-) > > > thanks, > Limeng -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-meta master] marvell-cn96xx: Enable the VFIO No-IOMMU support
In message: [kernel-meta master] marvell-cn96xx: Enable the VFIO No-IOMMU support on 06/11/2019 Kevin Hao wrote: > This is needed by some ODP applications and enable it as requested > by some customers. merged Bruce > > Signed-off-by: Kevin Hao > --- > bsp/marvell-cn96xx/marvell-cn96xx.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/marvell-cn96xx/marvell-cn96xx.cfg > b/bsp/marvell-cn96xx/marvell-cn96xx.cfg > index 93d77ad4c62d..1d1f7af0598a 100644 > --- a/bsp/marvell-cn96xx/marvell-cn96xx.cfg > +++ b/bsp/marvell-cn96xx/marvell-cn96xx.cfg > @@ -96,6 +96,7 @@ CONFIG_REGULATOR_GPIO=y > # VFIO > CONFIG_VFIO=y > CONFIG_VFIO_PCI=y > +CONFIG_VFIO_NOIOMMU=y > > # Misc > CONFIG_EEPROM_AT24=y > -- > 2.14.4 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [V2][[kernel v5.2/standard/xlnx-soc]][PATCH 0/3] xililnx-zynqmp: fix compile warning in zynqmp platform
On Mon, Nov 4, 2019 at 10:01 AM wrote: > > From: Quanyang Wang > > Hi Bruce & Michal, > > In V1 patch, I define the maximum length of data buffer to 12. But when > I try to search if there is existing macro defined for the maxium length, > I find that the maximum length should be 32. > In drivers/remoteproc/zynqmp_r5_remoteproc.c, it use IPI_BUF_LEN_MAX which is > defined as 32. > In drivers/mailbox/zynqmp-ipi-mailbox.c, it will use the "size" property > value (0x20) > of "local_request_region" node in ./arch/arm64/boot/dts/xilinx/zynqmp.dtsi. > So change the value from 12 to 32 in V2 patch. > v2 is merged. Bruce > Thanks, > Quanyang > > Quanyang Wang (1): > drivers: soc: xilinx: fix compile warning by defining payload array > length to 32 > > drivers/remoteproc/zynqmp_r5_remoteproc.c | 2 -- > drivers/soc/xilinx/zynqmp_power.c | 2 +- > include/linux/mailbox/zynqmp-ipi-message.h | 3 +++ > 3 files changed, 4 insertions(+), 3 deletions(-) > > -- > 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 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/1] xilinx-zynqmp: remove CONFIG_VIRTIO=y from xilinx-zynqmp.cfg
On Tue, Nov 5, 2019 at 10:45 AM qwang2 wrote: > > Hi Bruce, > > On 2019/11/5 下午5:07, quanyang.w...@windriver.com wrote: > > From: Quanyang Wang > > > > Hi Bruce & Michal, > > > > This patch delete kernel option CONFIG_VIRTIO. This is because that > > CONFIG_VIRTIO > > can be set to "Y" or "m". If set it to be "Y" explicitly, there will be > > build warning: > > > > WARNING: linux-yocto-5.2.x+gitAUTOINC+343a633207_b039f25b0a-r0 > > do_kernel_configcheck: [kernel config]: specified values did not make it > > into the kernel's final configuration: > > -- CONFIG_VIRTIO - > > Config: CONFIG_VIRTIO > > Requested value: CONFIG_VIRTIO=y > > Actual value: CONFIG_VIRTIO=m > > Would you please help merge this patch to yocto-kernel-cache's branch > yocto-5.2 and master? > merged to both branches. Bruce > Thanks, > Quanyang > > > > > Thanks, > > Quanyang > > > > Quanyang Wang (1): > >xilinx-zynqmp: remove CONFIG_VIRTIO=y from xilinx-zynqmp.cfg > > > > bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 1 - > > 1 file changed, 1 deletion(-) > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] : [kernel-cache yocto-5.2/master]: renesas-rcar: remove CONFIG_DRM_PANEL_LVDS kernel configure
In message: [linux-yocto]: [kernel-cache yocto-5.2/master]: renesas-rcar: remove CONFIG_DRM_PANEL_LVDS kernel configure on 05/11/2019 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > I want to update renesas-rcar bsp kernel configure. > > Could you please merge this patch into yocto-kernel-cache, branches are > yocto-5.2 and master? merged! Bruce > > 0001-renesas-rcar-remove-CONFIG_DRM_PANEL_LVDS-kernel-con.patch > > renesas-rcar.cfg |1 - > 1 file changed, 1 deletion(-) > > > thanks, > Limeng -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [[kernel v5.2/standard/xlnx-soc]][PATCH 0/3] xililnx-zynqmp: fix compile warning in zynqmp platform
In message: [linux-yocto][[kernel v5.2/standard/xlnx-soc]][PATCH 0/3] xililnx-zynqmp: fix compile warning in zynqmp platform on 29/10/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > > Hi Bruce, Michal, > > There are 3 patches to fix compile warnings in xilinx-zynqmp platform. > > Would you please help review and merge these patches to > linux-yocto v5.2/standard/xlnx-soc branch? I've merged the patches that Michal Ack'd. Just resend v2 for the single patch. Bruce > > Thanks, > Quanyang > > > Quanyang Wang (3): > net: emaclite: fix compile warning in BUFFER_ALIGN > drivers: soc: xilinx: fix compile warning by defining payload array > length to 12 > fpga: zynqmp-fpga: fix compile warning in fpga_mgr_register > > drivers/fpga/fpga-mgr.c | 5 +++-- > drivers/net/ethernet/xilinx/xilinx_emaclite.c | 2 +- > drivers/soc/xilinx/zynqmp_power.c | 2 +- > 3 files changed, 5 insertions(+), 4 deletions(-) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/1][V2]patches for xilinx
On Mon, Nov 4, 2019 at 1:21 AM Quanyang Wang wrote: > > Hi Bruce, > > On 10/25/19 1:20 AM, Bruce Ashfield wrote: > > On Thu, Oct 24, 2019 at 6:26 AM wrote: > >> From: Quanyang Wang > >> > >> Hi all, > >> > >> V1 ---> V2: > >> > >> 1. delete the patch "arch: arm64: dts: add overlay dts file" because it is > >> improper > >> to add into kernel source. > >> > >> 2. modify the patch " i2c: cadence: do not clear bus_hold_flag in mrecv" > >> by adding > >> a I2C_M_NOSTART flag check according to Shubhrajyoti's suggestion. And > >> test it at > >> zcu102 board (read bus 0x8 device 0x65 (ucd10120) register 0xd6)as below: > >> Before applying this patch: > >> root@xilinx-zynq:~# i2cget -f -y 0x8 0x65 0xd6 > >> 0xff > >> After applying this patch: > >> root@xilinx-zynq:~# i2cget -f -y 0x8 0x65 0xd6 > >> 0x05 > >> > > I'll wait for comments on this patch. > > This patch has been reviewed. Would you please help merge it to > v5.2/standard/xlnx-soc? I saw the review, but was traveling last week. I'll pick up the reviewed changes today. Bruce > > Thanks, > > Quanyang > > > > > I just wanted to follow up to say that I *think* that I have all of > > the reviewed and ack'd patches merged now .. but gmail is doing some > > very strange things and hiding replies to some of the threads. > > > > So if you see something that is reviewed/acked and is missing, send it > > again with a clear "v2" (or whatever version it is) in the subject. > > > > Bruce > > > >> Thanks, > >> Quanyang > >> > >> Quanyang Wang (1): > >>i2c: cadence: keep bus_hold_flag unless I2C_M_NOSTART is set > >> > >> drivers/i2c/busses/i2c-cadence.c | 8 +--- > >> 1 file changed, 5 insertions(+), 3 deletions(-) > >> > >> -- > >> 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 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: enable GCC -O2 optimization
On Thu, Oct 31, 2019 at 11:12 PM He Zhe wrote: > > Hi Bruce, > > This now happens on qemuarmv5 and possibly on all arm arches. > > standard.scc -> arm.scc -> arm.cfg -> CONFIG_CC_OPTIMIZE_FOR_SIZE=y > > It hangs the whole system. > But turning off CONFIG_CC_OPTIMIZE_FOR_SIZE would affect all arches. > > What do you think? It used to be the opposite. The boards only booted with this enabled. So my worry about changing it globally is that I fix some boards, and break others. We can always just change the setting in the BSP .cfg's that we can prove they build and boot. Bruce > > Thanks, > Zhe > > > On 10/30/19 8:25 AM, Bruce Ashfield wrote: > > merged. > > > > We should also either have a plan to figure out the root cause > > of this, or we should patch the Kconfig to be broken if enabled > > .. that way we'll prevent others from turning it on by mistake. > > > > > > Bruce > > > > > > In message: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] > > ti-am335x: enable GCC -O2 optimization > > on 29/10/2019 Jun Miao wrote: > > > >> Ti-am335x bsp includes the standard.scc file, which will set > >> CONFIG_CC_OPTIMIZE_FOR_SIZE=y. > >> As a result, the system boot hangs like below in v5.4.0-rc4 kernel version: > >> When we enable CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE for -O2 Optimization > >> level, > >> the boot succeeds. > >> > >> boot log: > >> systemd[1]: Set hostname to . > >> systemd[1]: Failed to open netlink: Operation not permitted > >> systemd-fstab-generator[120]: Failed to write unit file -.mount: Bad > >> address > >> systemd-fstab-generator[120]: Failed to write unit file > >> var-volatile.mount: Bad address > >> ... ... > >> systemd[1]: Failed to start device monitor: Bad address > >> systemd[1]: SO_PASSCRED failed: Bad address > >> [!!] Failed to start up manager. > >> systemd[1]: Freezing execution. > >> > >> Signed-off-by: Jun Miao > >> --- > >> bsp/ti-am335x/ti-am335x.cfg | 2 ++ > >> 1 file changed, 2 insertions(+) > >> > >> diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg > >> index 71884fd7..190cb876 100644 > >> --- a/bsp/ti-am335x/ti-am335x.cfg > >> +++ b/bsp/ti-am335x/ti-am335x.cfg > >> @@ -258,3 +258,5 @@ CONFIG_OMAP_CONTROL_PHY=y > >> > >> CONFIG_TI_PIPE3=y > >> CONFIG_ARM_PMU=y > >> + > >> +CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y > >> -- > >> 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 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto v5.2] Another patch series for the Marvell cn96xx support
In message: [linux-yocto v5.2] Another patch series for the Marvell cn96xx support on 31/10/2019 Kevin Hao wrote: > Hi Bruce, > > Here is another patch series for the Marvell cn96xx SoC support. It mainly > focus on the coresight and Ethernet drivers. Please help me merge this to: > v5.2/standard/cn96xx > v5.2/standard/preempt-rt/cn96xx > > The following changes since commit ea644ca0c23daa58925be27754d0cac01ed50e9b: > > Merge branch 'v5.2/standard/base' into v5.2/standard/cn96xx (2019-10-29 > 20:34:04 -0400) > > are available in the Git repository at: > > g...@github.com:haokexin/linux v5.2/standard/cn96xx Thanks Kevin, this is now merged to both branches. Bruce > > for you to fetch changes up to 9c320cb186dc953deb487ffd15ee8ee1c6281fe4: > > coresight: Fix assumptions on coresight topology (2019-10-31 19:39:41 +0800) > > > Christina Jacob (3): > octeontx2-pf: remove redundant changes from speed change suppcrt. > octeontx-af: Interface mode change feature via ethtool > octeontx2-pf: Interface Mode change using ethtool. > > Geetha sowjanya (3): > iommu/arm-smmu-v3: Force 32 byte command queue memory reads > octeontx2-pf: Add shutdown sequence for PF/VF > octeontx2-pf: Reset the PF/VF on MTU change > > Hao Zheng (2): > octeontx2-af: kpu profile update for protocol nvgre > octeontx2-af: kpu profile fix for a missing action entry > > Kiran Kumar K (1): > octeontx2-af: match nvgre as ltype > > Linu Cherian (4): > coresight: etm4x: Add Marvell OcteontTx CN9xxx ETM device > coresight: tmc: Add Marvell OcteonTx CN9xxx TMC device > coresight: tmc: Fixes for Marvell OcteonTx CN9xxx ETR HW issues. > coresight: Fix assumptions on coresight topology > > Nithin Dabilpuram (1): > octeontx2-af: fix backpressure cfg on lf alloc and free > > Peter Swain (3): > mmc: cavium: calibrate otx2 just once > mmc: dt-bindings: describe cavium vmmc/vqmmc > gpio: add no-frills i2c->gpio expander > > Stanislaw Kardach (1): > octeontx2-af: reserve top LD/LTYPEs for custom KPU > > Subbaraya Sundeep (5): > octeontx2-pf: Do not set mac address again > octeontx2-pf: Clear mbox interrupt status early > octeontx2-af: Do not exit when firmware unavailable > octeontx2-af: Init mcam resources after loading profile > octeontx2-af: Fix default profile loading checks > > Sunil Goutham (1): > net: thunderx: Fix RSS flow hash settings display > > hariprasad (2): > octeontx2-pf: Add rx vlan offload support > octeontx2-af: update address of global CGX RX_STATS > > Documentation/devicetree/bindings/arm/coresight.txt | 4 ++ > Documentation/devicetree/bindings/gpio/gpio-i2c.txt | 32 > +++ > Documentation/devicetree/bindings/mmc/cavium-mmc.txt | 48 > -- > MAINTAINERS | 5 +++ > drivers/gpio/Kconfig | 12 ++ > drivers/gpio/Makefile | 1 + > drivers/gpio/gpio-i2c.c | 206 > > drivers/hwtracing/coresight/coresight-etm-perf.c | 2 +- > drivers/hwtracing/coresight/coresight-etm4x.c | 1 + > drivers/hwtracing/coresight/coresight-priv.h | 3 +- > drivers/hwtracing/coresight/coresight-tmc-etr.c | 72 > +++- > drivers/hwtracing/coresight/coresight-tmc.c | 21 ++ > drivers/hwtracing/coresight/coresight-tmc.h | 94 > +- > drivers/hwtracing/coresight/coresight.c | 25 +++- > drivers/iommu/arm-smmu-v3.c | 18 +--- > drivers/mmc/host/cavium.h | 1 - > drivers/net/ethernet/cavium/thunder/nicvf_ethtool.c | 34 > +--- > drivers/net/ethernet/marvell/octeontx2/af/cgx.c | 132 > ++- > drivers/net/ethernet/marvell/octeontx2/af/cgx_fw_if.h | 33 > ++- > drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 14 ++- > drivers/net/ethernet/marvell/octeontx2/af/npc.h | 16 > drivers/net/ethernet/marvell/octeontx2/af/npc_profile.h | 10 - > drivers/net/ethernet/marvell/octeontx2/af/rvu.c | 26 ++-- > drivers/net/ethernet/marvell/octeontx2/af/rvu_nix.c | 13 -- > drivers/net/ethernet/marvell/octeontx2/af/rvu_npa.c | 2 + > drivers/net/ethernet/marvell/octeontx2/af/rvu_npc.c | 11 ++--- > drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c | 17 >
Re: [linux-yocto] [linux-yocto-v5.2]: [kernel v5.2/standard/base]: Revert "arm64: dts: r8a7795: Add CPUIdle support for all CPU core"
In message: [linux-yocto-v5.2]: [kernel v5.2/standard/base]: Revert "arm64: dts: r8a7795: Add CPUIdle support for all CPU core" on 30/10/2019 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > Some days ago, I sent a patch to add CPUIdle feature for renesas-rcar > platform. This patch only add cpu-idle-states property > in dts file. But after testing, we find out it causes kernel unstable when > run some stress testing cases. > So, I think maybe I omit other cpuidle related patches. > I intend to revert this patch firstly, and submit all patches related with > cpu idle featue in later. Sounds good. the revert is now pushed, and I'll wait for the followup. Bruce > > 0001-Revert-arm64-dts-r8a7795-Add-CPUIdle-support-for-all.patch > > Could you please merge this patch into linux-yocto branch are > v5.2/standard/base? > > r8a7795.dtsi | 32 > 1 file changed, 32 deletions(-) > > thanks, > Limeng -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] kernel-dev rpm does not have much contents
On Wed, Oct 30, 2019 at 10:44 AM Michael Lim wrote:
> >>>You want the kernel-devsrc package, not kernel-dev in this case.
> >>
> >>>Bruce
> >>
> >> Thank you for responding Bruce.
> >>
> >> I do not see kernel-devsrc defined in the kernel.bbclass
> >
> >It's a separate recipe. Not part of the bbclass. Build that recipe,
> >and install the package and you'll get what you want.
>
> Thank you Bruce. After enable kernel-devsrc, the necessary rpm had been
> created.
>
> I have one question though, the kernel-devsrc does not seem to include all
> the kernel src, that has been fetched and applied patches. Why does it call
> kernel-devsrc instead of just kernel-dev? Is there a way to generate rpm
> for a complete kernel src with patches applied?
>
>
Correct. It only has enough of the build artifacts to develop against the
running kernel, i.e. out of tree modules (either on the build host, or on
target).
The name is historical, and isn't aligned with any specific distro (i.e. no
matter what folks say, there is no agreed upon naming for these packages,
so rather than break expectations in the ecosystem, we keep ours as it was:
kernel-devsrc).
To keep it minimal, we do use a curated version of the source (just like
redhat, etc). Footprint is very important for that package.
That being said, I do have a patch that creates a 'linux-source' package
that is the complete source, but that is really only for reference and
isn't extensively tested for building/development. I'm not in a place that
I can get that patch right now, but I can send it out a bit later today.
Out of curiosity. What is the use case that you have for the source ? With
that information, I can tweak what we are offering as needed.
Bruce
> Anyway, I really appreciate you spent your value time to help out.
>
>
> Best Regards,
> Michael Y. Lim
>
> HW VPD Template
> Boston SFO
>
>
> Office: 045/C-08
> Tie Line: 363-7244
> Phone: (512) 286-7244
> email: youh...@us.ibm.com
>
>
> [image: Inactive hide details for Bruce Ashfield ---10/29/2019 03:12:19
> AM---On Mon, Oct 28, 2019 at 3:29 PM Michael Lim Ashfield ---10/29/2019 03:12:19 AM---On Mon, Oct 28, 2019 at 3:29 PM
> Michael Lim wrote: >
>
> From: Bruce Ashfield
> To: Michael Lim
> Cc: Development list for the linux-yocto repositories <
> linux-yocto@yoctoproject.org>
> Date: 10/29/2019 03:12 AM
> Subject: Re: [EXTERNAL] Re: [linux-yocto] kernel-dev rpm does not have
> much contents
> --
>
>
>
> On Mon, Oct 28, 2019 at 3:29 PM Michael Lim wrote:
> >
> > >On Mon, Oct 28, 2019 at 11:36 AM Michael Lim
> wrote:
> > >>
> > >> I am building a power pc core-image-minimal in yocto using
> linux-yoct_4.19. The project was built successfully, However, the
> kernel-dev rpm does not have much content.
> > >>
> > >> Its contents below:
> > >> fips_ppcnf]$ rpmv
> kernel-dev-4.19.61+git0+960be42184_4ec6f25516-r0.fips_ppcnf.rpm
> > >> drwxr-xr-x 2 root root 0 Oct 26 17:04 /boot
> > >> -rw-r--r-- 1 root root 375741 Oct 26 17:04
> /boot/Module.symvers-4.19.61-yocto-standard
> > >> -rw-r--r-- 1 root root 1542246 Oct 26 17:04
> /boot/System.map-4.19.61-yocto-standard
> > >> -rw-r--r-- 1 root root 60694 Oct 26 17:04
> /boot/config-4.19.61-yocto-standard
> > >>
> > >> There are no contents relate to the header files nor any built code.
> > >>
> > >> The kernel.bbclass has this line
> > >> FILES_${KERNEL_PACKAGE_NAME}-dev = "/boot/System.map*
> /boot/Module.symvers* /boot/config* ${KERNEL_SRC_PATH}
> ${nonarch_base_libdir}/modules/${KERNEL_VERSION}/build"
> > >>
> > >> KERNEL_SRC_PATH="/usr/src/kernel"
> > >> KERNEL_VERSION="4.19.61-yocto-standard"
> > >>
> > >> Seems like the contents in the bold path were not included in the rpm.
> > >>
> > >> I'm not sure where the ${KERNEL_SRC_PATH} is. So I changed it to
> ${STAGING_KERNEL_BUILDDIR}. As I know there are contents there.
> Unfortunately, kernel-dev rpm does not contains the file in
> ${STAGING_KERNEL_BUILDDIR}.
> > >>
> > >>
> STAGING_KERNEL_BUILDDIR="/tmp/youhour/b20191023a/fips-build/fips-ppcnf/build/tmp/work-shared/fips-ppcnf/kernel-build-artifacts"
> > >>
> > >> I am very very new to the yocto build. Can someone help pointing out
> what I need to do to get all the code in ${STAGING_KERNEL_BUILDDIR} the
> kernel-dev rpm?
> >
> > >You want the kernel-devsrc package, not kernel-dev in this case.
> >
Re: [linux-yocto] [V2][kernel v5.2/standard/xlnx-soc][PATCH 0/1] fix kmemleak in zcu102
In message: [V2][linux-yocto][kernel v5.2/standard/xlnx-soc][PATCH 0/1] fix kmemleak in zcu102 on 29/10/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > > This patch is missing to be merged. So I send it again. > > Would you please help merge these patches to linux-yocto > v5.2/standard/xlnx-soc branch? Thanks for the resend. I had indeed missed this one. It is now merged (it applies to standard/base, so I merged it there). Bruce > > Quanyang Wang (1): > clk: zynqmp: fix memory leak in zynqmp_register_clocks > > drivers/clk/zynqmp/clkc.c | 16 ++-- > 1 file changed, 10 insertions(+), 6 deletions(-) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: enable GCC -O2 optimization
merged. We should also either have a plan to figure out the root cause of this, or we should patch the Kconfig to be broken if enabled .. that way we'll prevent others from turning it on by mistake. Bruce In message: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: enable GCC -O2 optimization on 29/10/2019 Jun Miao wrote: > Ti-am335x bsp includes the standard.scc file, which will set > CONFIG_CC_OPTIMIZE_FOR_SIZE=y. > As a result, the system boot hangs like below in v5.4.0-rc4 kernel version: > When we enable CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE for -O2 Optimization level, > the boot succeeds. > > boot log: > systemd[1]: Set hostname to . > systemd[1]: Failed to open netlink: Operation not permitted > systemd-fstab-generator[120]: Failed to write unit file -.mount: Bad address > systemd-fstab-generator[120]: Failed to write unit file var-volatile.mount: > Bad address > ... ... > systemd[1]: Failed to start device monitor: Bad address > systemd[1]: SO_PASSCRED failed: Bad address > [!!] Failed to start up manager. > systemd[1]: Freezing execution. > > Signed-off-by: Jun Miao > --- > bsp/ti-am335x/ti-am335x.cfg | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg > index 71884fd7..190cb876 100644 > --- a/bsp/ti-am335x/ti-am335x.cfg > +++ b/bsp/ti-am335x/ti-am335x.cfg > @@ -258,3 +258,5 @@ CONFIG_OMAP_CONTROL_PHY=y > > CONFIG_TI_PIPE3=y > CONFIG_ARM_PMU=y > + > +CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] : [kernel-cache yocto-5.2/master]: renesas-rcar: remove unused kernel configure
merged Bruce In message: [linux-yocto]: [kernel-cache yocto-5.2/master]: renesas-rcar: remove unused kernel configure on 28/10/2019 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > I want to update renesas-rcar bsp kernel configure. > > Could you please merge this patch into yocto-kernel-cache, branches are > yocto-5.2 and master? > > 0001-renesas-rcar-remove-unused-kernel-configure.patch > > renesas-rcar.cfg |9 - > 1 file changed, 9 deletions(-) > > > thanks, > Limeng -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [EXTERNAL] Re: kernel-dev rpm does not have much contents
On Mon, Oct 28, 2019 at 3:29 PM Michael Lim wrote:
>
> >On Mon, Oct 28, 2019 at 11:36 AM Michael Lim wrote:
> >>
> >> I am building a power pc core-image-minimal in yocto using
> >> linux-yoct_4.19. The project was built successfully, However, the
> >> kernel-dev rpm does not have much content.
> >>
> >> Its contents below:
> >> fips_ppcnf]$ rpmv
> >> kernel-dev-4.19.61+git0+960be42184_4ec6f25516-r0.fips_ppcnf.rpm
> >> drwxr-xr-x 2 root root 0 Oct 26 17:04 /boot
> >> -rw-r--r-- 1 root root 375741 Oct 26 17:04
> >> /boot/Module.symvers-4.19.61-yocto-standard
> >> -rw-r--r-- 1 root root 1542246 Oct 26 17:04
> >> /boot/System.map-4.19.61-yocto-standard
> >> -rw-r--r-- 1 root root 60694 Oct 26 17:04
> >> /boot/config-4.19.61-yocto-standard
> >>
> >> There are no contents relate to the header files nor any built code.
> >>
> >> The kernel.bbclass has this line
> >> FILES_${KERNEL_PACKAGE_NAME}-dev = "/boot/System.map*
> >> /boot/Module.symvers* /boot/config* ${KERNEL_SRC_PATH}
> >> ${nonarch_base_libdir}/modules/${KERNEL_VERSION}/build"
> >>
> >> KERNEL_SRC_PATH="/usr/src/kernel"
> >> KERNEL_VERSION="4.19.61-yocto-standard"
> >>
> >> Seems like the contents in the bold path were not included in the rpm.
> >>
> >> I'm not sure where the ${KERNEL_SRC_PATH} is. So I changed it to
> >> ${STAGING_KERNEL_BUILDDIR}. As I know there are contents there.
> >> Unfortunately, kernel-dev rpm does not contains the file in
> >> ${STAGING_KERNEL_BUILDDIR}.
> >>
> >> STAGING_KERNEL_BUILDDIR="/tmp/youhour/b20191023a/fips-build/fips-ppcnf/build/tmp/work-shared/fips-ppcnf/kernel-build-artifacts"
> >>
> >> I am very very new to the yocto build. Can someone help pointing out what
> >> I need to do to get all the code in ${STAGING_KERNEL_BUILDDIR} the
> >> kernel-dev rpm?
>
> >You want the kernel-devsrc package, not kernel-dev in this case.
>
> >Bruce
>
> Thank you for responding Bruce.
>
> I do not see kernel-devsrc defined in the kernel.bbclass
It's a separate recipe. Not part of the bbclass. Build that recipe,
and install the package and you'll get what you want.
>
> Is there a bug in the kernel.bbclass where it includes ${KERNEL_SRC_PATH} in
> the kernel-dev? If that part is correct, is there a bug that prevent code
> copy to ${KERNEL_SRC_PATH}?
>
There's no bug. kernel-dev doesn't the kernel source by design. Yocto
/ oe has always had its own naming for these packages, and kernel-dev
is the images / artifacts and the directory structure. Now that
kernel-devsrc is available (it wasn't a few years ago), we actually
could remove those directories from kernel.bbclass to clarify things.
Bruce
> ${KERNEL_SRC_PATH} seems to be a relative path in the yocto build. is
> ${D}${KERNEL_SRC_PATH} the absolute path?
>
> Thank you in advance.
>
> Best Regards,
> Michael Y. Lim
>
> HW VPD Template
> Boston SFO
>
>
> Office: 045/C-08
> Tie Line: 363-7244
> Phone: (512) 286-7244
> email: youh...@us.ibm.com
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] kernel-dev rpm does not have much contents
On Mon, Oct 28, 2019 at 11:36 AM Michael Lim wrote:
>
> I am building a power pc core-image-minimal in yocto using linux-yoct_4.19.
> The project was built successfully, However, the kernel-dev rpm does not have
> much content.
>
> Its contents below:
> fips_ppcnf]$ rpmv
> kernel-dev-4.19.61+git0+960be42184_4ec6f25516-r0.fips_ppcnf.rpm
> drwxr-xr-x 2 root root 0 Oct 26 17:04 /boot
> -rw-r--r-- 1 root root 375741 Oct 26 17:04
> /boot/Module.symvers-4.19.61-yocto-standard
> -rw-r--r-- 1 root root 1542246 Oct 26 17:04
> /boot/System.map-4.19.61-yocto-standard
> -rw-r--r-- 1 root root 60694 Oct 26 17:04 /boot/config-4.19.61-yocto-standard
>
> There are no contents relate to the header files nor any built code.
>
> The kernel.bbclass has this line
> FILES_${KERNEL_PACKAGE_NAME}-dev = "/boot/System.map* /boot/Module.symvers*
> /boot/config* ${KERNEL_SRC_PATH}
> ${nonarch_base_libdir}/modules/${KERNEL_VERSION}/build"
>
> KERNEL_SRC_PATH="/usr/src/kernel"
> KERNEL_VERSION="4.19.61-yocto-standard"
>
> Seems like the contents in the bold path were not included in the rpm.
>
> I'm not sure where the ${KERNEL_SRC_PATH} is. So I changed it to
> ${STAGING_KERNEL_BUILDDIR}. As I know there are contents there.
> Unfortunately, kernel-dev rpm does not contains the file in
> ${STAGING_KERNEL_BUILDDIR}.
>
> STAGING_KERNEL_BUILDDIR="/tmp/youhour/b20191023a/fips-build/fips-ppcnf/build/tmp/work-shared/fips-ppcnf/kernel-build-artifacts"
>
> I am very very new to the yocto build. Can someone help pointing out what I
> need to do to get all the code in ${STAGING_KERNEL_BUILDDIR} the kernel-dev
> rpm?
You want the kernel-devsrc package, not kernel-dev in this case.
Bruce
>
> By the way, I am using yocto 'WARRIOR' branch.
>
> Thank you in advance.
>
>
>
>
> Best Regards,
> Michael Y. Lim
>
> HW VPD Template
> Boston SFO
>
>
> Office: 045/C-08
> Tie Line: 363-7244
> Phone: (512) 286-7244
> email: youh...@us.ibm.com
>
> --
> ___
> linux-yocto mailing list
> linux-yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/linux-yocto
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/1][V2]patches for xilinx
On Thu, Oct 24, 2019 at 6:26 AM wrote: > > From: Quanyang Wang > > Hi all, > > V1 ---> V2: > > 1. delete the patch "arch: arm64: dts: add overlay dts file" because it is > improper > to add into kernel source. > > 2. modify the patch " i2c: cadence: do not clear bus_hold_flag in mrecv" by > adding > a I2C_M_NOSTART flag check according to Shubhrajyoti's suggestion. And test > it at > zcu102 board (read bus 0x8 device 0x65 (ucd10120) register 0xd6)as below: > Before applying this patch: > root@xilinx-zynq:~# i2cget -f -y 0x8 0x65 0xd6 > 0xff > After applying this patch: > root@xilinx-zynq:~# i2cget -f -y 0x8 0x65 0xd6 > 0x05 > I'll wait for comments on this patch. I just wanted to follow up to say that I *think* that I have all of the reviewed and ack'd patches merged now .. but gmail is doing some very strange things and hiding replies to some of the threads. So if you see something that is reviewed/acked and is missing, send it again with a clear "v2" (or whatever version it is) in the subject. Bruce > Thanks, > Quanyang > > Quanyang Wang (1): > i2c: cadence: keep bus_hold_flag unless I2C_M_NOSTART is set > > drivers/i2c/busses/i2c-cadence.c | 8 +--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > -- > 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 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [yocto-kernel-cache master/yocto-5.2][PATCH] cgl: Remove non-existing kernel options
On Thu, Oct 24, 2019 at 3:49 AM wrote:
>
> From: He Zhe
>
> Thess options have been remove from mainline kernel.
>
> CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION removed by
> 4c145dce2601 ("xfrm: make xfrm modes builtin")
>
> CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE removed by
> be6ec88f41ba ("selinux: Remove SECURITY_SELINUX_BOOTPARAM_VALUE")
>
thanks for the commit references .. they make it much easier for me to
quickly grab and merge changes like this.
Cheers,
Bruce
> Signed-off-by: He Zhe
> ---
> cgl/features/mip6/mip6.cfg | 1 -
> cgl/features/selinux/selinux-dev.cfg | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/cgl/features/mip6/mip6.cfg b/cgl/features/mip6/mip6.cfg
> index 09a11b8d..f9c344b6 100644
> --- a/cgl/features/mip6/mip6.cfg
> +++ b/cgl/features/mip6/mip6.cfg
> @@ -4,6 +4,5 @@ CONFIG_XFRM_MIGRATE=y
> CONFIG_NET_KEY=m
> CONFIG_NET_KEY_MIGRATE=y
> CONFIG_IPV6_MIP6=m
> -CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
> CONFIG_IPV6_MULTIPLE_TABLES=y
> CONFIG_IPV6_SUBTREES=y
> diff --git a/cgl/features/selinux/selinux-dev.cfg
> b/cgl/features/selinux/selinux-dev.cfg
> index 913e5e13..4c77d989 100644
> --- a/cgl/features/selinux/selinux-dev.cfg
> +++ b/cgl/features/selinux/selinux-dev.cfg
> @@ -1,4 +1,3 @@
> # SPDX-License-Identifier: MIT
> CONFIG_SECURITY_SELINUX_BOOTPARAM=y
> -CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
> CONFIG_SECURITY_SELINUX_DEVELOP=y
> --
> 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
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-v5.2]: [kernel standard/base]: renesas-rcar: add some patches to improve features on renesas-rcar platform
On Thu, Oct 24, 2019 at 2:00 AM wrote: > > From: Limeng > > Hi Bruce, > > I am working on BSP renesas-rcar platform, and intend to merge this BSP > supporting into yocto community. > Below 4 patches are used to improve gpio, CAN BUS, audio and PCIe features > This first patch is from mainline upstream, the other 3 patches merged into > linux-yocto-dev(standard/base) some days ago. > > 0001-arm64-dts-renesas-ulcb-kf-Add-support-for-TI-WL1837.patch > 0002-arch-arm64-dts-Set-gpio5-pin9-as-input-by-default.patch > 0003-driver-net-can-disable-clock-when-it-is-in-enable-st.patch > 0004-pci-pcie-rcar-add-regulators-support.patch > > Could you please merge the 4 patches into linux-yocto, branch is > v5.2/standard/base? These already seem to be in v5.2/standard/base (Signed off by you and myself) .. was this sent in error ? or did gmail do something strange and dig up old email for me and mark them as new ? Bruce > > arch/arm64/boot/dts/renesas/ulcb-kf.dtsi | 105 > +++ > drivers/net/can/rcar/rcar_can.c |5 + > drivers/pci/controller/pcie-rcar.c | 64 ++ > 3 files changed, 173 insertions(+), 1 deletion(-) > > > thanks, > Limeng -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/2] xilinx-zynq: fix kdump hang issue
In message: [linux-yocto][PATCH 0/2] xilinx-zynq: fix kdump hang issue on 22/10/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, Michal, > > There are 2 patches. > > The patch "ARM: zynq: use physical cpuid in zynq_slcr_cpu_stop/start" > fix the kdump hang issue when not using disable_nonboot_cpus. > And the patch "xilinx-zynq: Revert "zynq: SMP crashkernel support"" > revert the patch which using disable_nonboot_cpus. Although one of the two patches applies to v5.2/standard/base, I kept them both together on the xlnx-soc branch. Bruce > > Thanks, > Quanyang > > Quanyang Wang (2): > ARM: zynq: use physical cpuid in zynq_slcr_cpu_stop/start > xilinx-zynq: Revert "zynq: SMP crashkernel support" > > arch/arm/kernel/machine_kexec.c | 3 --- > arch/arm/mach-zynq/platsmp.c| 6 -- > 2 files changed, 4 insertions(+), 5 deletions(-) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/1] [V2] xilinx-zynqmp: fix calltrace
In message: [linux-yocto][kernel v5.2/standard/xlnx-soc][PATCH 0/1] [V2] xilinx-zynqmp: fix calltrace on 23/10/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > > This patch is a V2 patch but no change against V1. Just add some comments > in the temporary section of the patch. Thanks, the temporary section comments were very useful. This is now merged. Bruce > > Would you please help merge these patches to linux-yocto > v5.2/standard/xlnx-soc branch? > > Quanyang Wang (1): > dma: xilinx: dpdma: alloc xilinx_dpdma_tx_desc using GFP_ATOMIC > > drivers/dma/xilinx/xilinx_dpdma.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] arm64: dts: r8a7795: Add CPUIdle support for all CPU core
This should already be on the branches: Author: Takeshi Kihara Date: Tue Oct 15 13:46:44 2019 +0800 arm64: dts: r8a7795: Add CPUIdle support for all CPU core commit 3c3b44c752c4eef9a29694f4262934445c5f5da9 from git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git This patch enables CPUIdle (Core shutdown) support for R-Car H3. Signed-off-by: Takeshi Kihara Signed-off-by: Meng Li Signed-off-by: Bruce Ashfield :100644 100644 097538cc4b1f 7596216409cd M arch/arm64/boot/dts/renesas/r8a7795.dtsi On Tue, Oct 22, 2019 at 10:47 PM wrote: > > From: Takeshi Kihara > > commit 3c3b44c752c4eef9a29694f4262934445c5f5da9 from > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git > > This patch enables CPUIdle (Core shutdown) support for R-Car H3. > > Signed-off-by: Takeshi Kihara > Signed-off-by: Meng Li > --- > arch/arm64/boot/dts/renesas/r8a7795.dtsi | 32 > > 1 file changed, 32 insertions(+) > > diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi > b/arch/arm64/boot/dts/renesas/r8a7795.dtsi > index e8c3d5f..7fe7428 100644 > --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi > +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi > @@ -123,6 +123,7 @@ > power-domains = < R8A7795_PD_CA57_CPU0>; > next-level-cache = <_CA57>; > enable-method = "psci"; > + cpu-idle-states = <_SLEEP_0>; > clocks = < CPG_CORE R8A7795_CLK_Z>; > operating-points-v2 = <_opp>; > capacity-dmips-mhz = <1024>; > @@ -135,6 +136,7 @@ > power-domains = < R8A7795_PD_CA57_CPU1>; > next-level-cache = <_CA57>; > enable-method = "psci"; > + cpu-idle-states = <_SLEEP_0>; > clocks = < CPG_CORE R8A7795_CLK_Z>; > operating-points-v2 = <_opp>; > capacity-dmips-mhz = <1024>; > @@ -147,6 +149,7 @@ > power-domains = < R8A7795_PD_CA57_CPU2>; > next-level-cache = <_CA57>; > enable-method = "psci"; > + cpu-idle-states = <_SLEEP_0>; > clocks = < CPG_CORE R8A7795_CLK_Z>; > operating-points-v2 = <_opp>; > capacity-dmips-mhz = <1024>; > @@ -159,6 +162,7 @@ > power-domains = < R8A7795_PD_CA57_CPU3>; > next-level-cache = <_CA57>; > enable-method = "psci"; > + cpu-idle-states = <_SLEEP_0>; > clocks = < CPG_CORE R8A7795_CLK_Z>; > operating-points-v2 = <_opp>; > capacity-dmips-mhz = <1024>; > @@ -171,6 +175,7 @@ > power-domains = < R8A7795_PD_CA53_CPU0>; > next-level-cache = <_CA53>; > enable-method = "psci"; > + cpu-idle-states = <_SLEEP_1>; > clocks = < CPG_CORE R8A7795_CLK_Z2>; > operating-points-v2 = <_opp>; > capacity-dmips-mhz = <535>; > @@ -182,6 +187,7 @@ > power-domains = < R8A7795_PD_CA53_CPU1>; > next-level-cache = <_CA53>; > enable-method = "psci"; > + cpu-idle-states = <_SLEEP_1>; > clocks = < CPG_CORE R8A7795_CLK_Z2>; > operating-points-v2 = <_opp>; > capacity-dmips-mhz = <535>; > @@ -193,6 +199,7 @@ > power-domains = < R8A7795_PD_CA53_CPU2>; > next-level-cache = <_CA53>; > enable-method = "psci"; > + cpu-idle-states = <_SLEEP_1>; > clocks = < CPG_CORE R8A7795_CLK_Z2>; > operating-points-v2 = <_opp>; > capacity-dmips-mhz = <535>; > @@ -204,6 +211,7 @@ > power-domains = < R8A7795_PD_CA53_CPU3>; > next-level-cache = <_CA53>; > enable-method = "psci"; > +
Re: [linux-yocto] [PATCH] arm64: dts: r8a7795: Add CPUIdle support for all CPU core
On Tue, Oct 22, 2019 at 10:57 PM Bruce Ashfield wrote: > > This should already be on the branches: > .. and I forgot the commit id: c93bf81feabf89b5ee77838d3bb62825d04dab09 Bruce > Author: Takeshi Kihara > Date: Tue Oct 15 13:46:44 2019 +0800 > > arm64: dts: r8a7795: Add CPUIdle support for all CPU core > > commit 3c3b44c752c4eef9a29694f4262934445c5f5da9 from > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git > > This patch enables CPUIdle (Core shutdown) support for R-Car H3. > > Signed-off-by: Takeshi Kihara > Signed-off-by: Meng Li > Signed-off-by: Bruce Ashfield > > :100644 100644 097538cc4b1f 7596216409cd M > arch/arm64/boot/dts/renesas/r8a7795.dtsi > > On Tue, Oct 22, 2019 at 10:47 PM wrote: > > > > From: Takeshi Kihara > > > > commit 3c3b44c752c4eef9a29694f4262934445c5f5da9 from > > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git > > > > This patch enables CPUIdle (Core shutdown) support for R-Car H3. > > > > Signed-off-by: Takeshi Kihara > > Signed-off-by: Meng Li > > --- > > arch/arm64/boot/dts/renesas/r8a7795.dtsi | 32 > > > > 1 file changed, 32 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi > > b/arch/arm64/boot/dts/renesas/r8a7795.dtsi > > index e8c3d5f..7fe7428 100644 > > --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi > > +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi > > @@ -123,6 +123,7 @@ > > power-domains = < R8A7795_PD_CA57_CPU0>; > > next-level-cache = <_CA57>; > > enable-method = "psci"; > > + cpu-idle-states = <_SLEEP_0>; > > clocks = < CPG_CORE R8A7795_CLK_Z>; > > operating-points-v2 = <_opp>; > > capacity-dmips-mhz = <1024>; > > @@ -135,6 +136,7 @@ > > power-domains = < R8A7795_PD_CA57_CPU1>; > > next-level-cache = <_CA57>; > > enable-method = "psci"; > > + cpu-idle-states = <_SLEEP_0>; > > clocks = < CPG_CORE R8A7795_CLK_Z>; > > operating-points-v2 = <_opp>; > > capacity-dmips-mhz = <1024>; > > @@ -147,6 +149,7 @@ > > power-domains = < R8A7795_PD_CA57_CPU2>; > > next-level-cache = <_CA57>; > > enable-method = "psci"; > > + cpu-idle-states = <_SLEEP_0>; > > clocks = < CPG_CORE R8A7795_CLK_Z>; > > operating-points-v2 = <_opp>; > > capacity-dmips-mhz = <1024>; > > @@ -159,6 +162,7 @@ > > power-domains = < R8A7795_PD_CA57_CPU3>; > > next-level-cache = <_CA57>; > > enable-method = "psci"; > > + cpu-idle-states = <_SLEEP_0>; > > clocks = < CPG_CORE R8A7795_CLK_Z>; > > operating-points-v2 = <_opp>; > > capacity-dmips-mhz = <1024>; > > @@ -171,6 +175,7 @@ > > power-domains = < R8A7795_PD_CA53_CPU0>; > > next-level-cache = <_CA53>; > > enable-method = "psci"; > > + cpu-idle-states = <_SLEEP_1>; > > clocks = < CPG_CORE R8A7795_CLK_Z2>; > > operating-points-v2 = <_opp>; > > capacity-dmips-mhz = <535>; > > @@ -182,6 +187,7 @@ > > power-domains = < R8A7795_PD_CA53_CPU1>; > > next-level-cache = <_CA53>; > > enable-method = "psci"; > > + cpu-idle-states = <_SLEEP_1>; > > clocks = < CPG_CORE R8A7795_CLK_Z2>; > > operating-points-v2 = <_opp>; > > capacity-dmips-mhz = <535>; > > @@ -193,6 +199,7 @@ > > power-domains = < R8A7795_PD_CA53_CPU2>; > > next-
Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/1] xilinx-zynqmp: fix calltrace
In message: [linux-yocto][kernel v5.2/standard/xlnx-soc][PATCH 0/1] xilinx-zynqmp: fix calltrace on 15/10/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, Michal, > > This patch fixes a calltrace when enable CONFIG_TRACING kernel option. > > Would you please help review and merge these patches to linux-yocto > v5.2/standard/xlnx-soc branch? I've dropped this from my pending queue. Can you send a v2 (clearly marked .. these series are starting to get tangled) with the comments of this thread summarized in the temporary section of the patch. That way, I'll know that I'm merging the proper version. Bruce > > Quanyang Wang (1): > dma: xilinx: dpdma: alloc xilinx_dpdma_tx_desc using GFP_ATOMIC > > drivers/dma/xilinx/xilinx_dpdma.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [yocto-kernel-cache master/yocto-5.2][PATCH] marvell-cn96xx: Add profiling feature
In message: [linux-yocto][yocto-kernel-cache master/yocto-5.2][PATCH] marvell-cn96xx: Add profiling feature on 21/10/2019 zhe...@windriver.com wrote: > From: He Zhe > > Add profiling related options for convenience for perf and etc. merged. Bruce > > Signed-off-by: He Zhe > --- > bsp/marvell-cn96xx/marvell-cn96xx.scc | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/marvell-cn96xx/marvell-cn96xx.scc > b/bsp/marvell-cn96xx/marvell-cn96xx.scc > index b98c442f..08d2e721 100644 > --- a/bsp/marvell-cn96xx/marvell-cn96xx.scc > +++ b/bsp/marvell-cn96xx/marvell-cn96xx.scc > @@ -5,3 +5,4 @@ kconf hardware features/edac/edac.cfg > include cfg/usb-mass-storage.scc > > include features/hugetlb/hugetlb.scc > +include features/profiling/profiling.scc > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/1] xilinx-zyqn: Move disable_nonboot_cpus() in front of local_irq_disable()
On Mon, Oct 21, 2019 at 11:27 PM Quanyang Wang wrote: > > > On 10/21/19 8:05 PM, Bruce Ashfield wrote: > > On Mon, Oct 21, 2019 at 6:45 AM Michal Simek > > wrote: > >> On 21. 10. 19 10:45, Quanyang Wang wrote: > >>> Hi Michal, > >>> > >>> On 10/21/19 4:16 PM, Michal Simek wrote: > >>>> On 21. 10. 19 7:50, quanyang.w...@windriver.com wrote: > >>>>> From: Quanyang Wang > >>>>> > >>>>> When run kdump with enabling CONFIG_DEBUG_PREEMPT, there is a calltrace > >>>>> as below: > >>>>> > >>>>> BUG: using smp_processor_id() in preemptible [] code: sh/303 > >>>>> caller is machine_crash_shutdown+0x2c/0xe8 > >>>>> CPU: 0 PID: 303 Comm: sh Kdump: loaded Not tainted > >>>>> 5.2.20-yocto-standard #1 > >>>>> Hardware name: Xilinx Zynq Platform > >>>>> [<80112ff4>] (unwind_backtrace) from [<8010ca4c>] (show_stack+0x18/0x1c) > >>>>> [<8010ca4c>] (show_stack) from [<809b000c>] (dump_stack+0x70/0x8c) > >>>>> [<809b000c>] (dump_stack) from [<80549a14>] > >>>>> (debug_smp_processor_id+0xd4/0x118) > >>>>> [<80549a14>] (debug_smp_processor_id) from [<80111428>] > >>>>> (machine_crash_shutdown+0x2c/0xe8) > >>>>> [<80111428>] (machine_crash_shutdown) from [<801afe24>] > >>>>> (__crash_kexec+0x70/0xd0) > >>>>> [<801afe24>] (__crash_kexec) from [<801259b4>] (panic+0x110/0x324) > >>>>> [<801259b4>] (panic) from [<805f7018>] (sysrq_handle_crash+0x18/0x1c) > >>>>> [<805f7018>] (sysrq_handle_crash) from [<805f7584>] > >>>>> (__handle_sysrq+0x9c/0x14c) > >>>>> [<805f7584>] (__handle_sysrq) from [<805f79e8>] > >>>>> (write_sysrq_trigger+0x5c/0x6c) > >>>>> [<805f79e8>] (write_sysrq_trigger) from [<8031e850>] > >>>>> (proc_reg_write+0x78/0x8c) > >>>>> [<8031e850>] (proc_reg_write) from [<802b1b28>] (vfs_write+0xc0/0x154) > >>>>> [<802b1b28>] (vfs_write) from [<802b2a64>] (ksys_write+0x6c/0xd4) > >>>>> [<802b2a64>] (ksys_write) from [<80101000>] (ret_fast_syscall+0x0/0x54) > >>>>> Exception stack(0xba157fa8 to 0xba157ff0) > >>>>> 7fa0: 0002 005ab930 0001 005ab930 0002 > >>>>> 7fc0: 0002 005ab930 76fa2290 0004 76f3d124 76f3cc8c > >>>>> > >>>>> 7fe0: 0004 7edec940 76edbfff 76e67d16 > >>>>> > >>>>> This is because that the function disable_nonboot_cpus is called in > >>>>> order to make sure that the crash kernel runs in the boot CPU(cpu0). > >>>>> And it will enable local irq by calling as below: > >>>>> > >>>>> disable_nonboot_cpus > >>>>>-> freeze_secondary_cpus > >>>>> -> _cpu_down > >>>>> -> percpu_down_write > >>>>> -> rcu_sync_enter > >>>>>-> spin_unlock_irq(>rss_lock) > >>>>> -> local_irq_enable() > >>>>> > >>>>> Then the functions including smp_processor_id() behind > >>>>> disable_nonboot_cpus > >>>>> will run at the irq-enabled context, and this will trigger the > >>>>> calltrace. > >>>>> > >>>>> So move disable_nonboot_cpus() in front of local_irq_disable() to avoid > >>>>> it since disable_nonboot_cpus() not need run at an atomic context. > >>>>> > >>>>> Signed-off-by: Quanyang Wang > >>>>> --- > >>>>>arch/arm/kernel/machine_kexec.c | 3 ++- > >>>>>1 file changed, 2 insertions(+), 1 deletion(-) > >>>>> > >>>>> diff --git a/arch/arm/kernel/machine_kexec.c > >>>>> b/arch/arm/kernel/machine_kexec.c > >>>>> index 654f2b1f9ac0..83d2025a4ab1 100644 > >>>>> --- a/arch/arm/kernel/machine_kexec.c > >>>>> +++ b/arch/arm/kernel/machine_kexec.c > >>>>> @@ -145,9 +145,10 @@ static void machine_kexec_mask_interrupts(void) > >>>>> void machine_crash_shutdown(struct pt_regs *regs) > >>
Re: [linux-yocto] [linux-yocto-v5.2/dev]: [kernel v5.2/standard/base and standard/base]: renesas-rcar: arm64: dts: r8a7795-h3ulcb: Add reserved memory regions
merged Bruce On Tue, Oct 22, 2019 at 1:07 AM wrote: > > From: Limeng > > Hi Bruce, > > I get below patch from SDK kernel to support reserved memory for renesas > platform firmware that is integrated in bootloader, and intend to merge it > into yocto community. > > 0001-arm64-dts-r8a7795-h3ulcb-Add-reserved-memory-regions.patch > > Could you please merge this patch into linux-yocto and linux-yocto-dev, > branch are v5.2/standard/base and standard/base? > > r8a7795-h3ulcb.dts | 29 - > 1 file changed, 28 insertions(+), 1 deletion(-) > > > thanks, > Limeng -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: arm64: dts: r8a7795: Add CPUIdle support for all CPU core
On Tue, Oct 22, 2019 at 8:06 AM Bruce Ashfield wrote: > > On Tue, Oct 22, 2019 at 3:06 AM Li, Meng wrote: > > > > > > > > > -Original Message- > > > From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com] > > > Sent: Saturday, October 19, 2019 12:51 PM > > > To: Li, Meng > > > Cc: linux-yocto@yoctoproject.org > > > Subject: Re: [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: > > > arm64: > > > dts: r8a7795: Add CPUIdle support for all CPU core > > > > > > In message: [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: > > > arm64: > > > dts: r8a7795: Add CPUIdle support for all CPU core > > > on 15/10/2019 meng...@windriver.com wrote: > > > > > > > From: Limeng > > > > > > > > Hi Bruce, > > > > > > > > I get below patch from SDK kernel to support cpu idle feature, and > > > > intend > > > to merge it into yocto community. > > > > > > > > 0001-arm64-dts-r8a7795-Add-CPUIdle-support-for-all-CPU-co.patch > > > > > > > > Could you please merge this patch into linux-yocto-dev, branch is > > > standard/base? > > > > > > Looks fine to me, this is now merged. > > > > > > > Hi Bruce, > > > > I found a strange thing. > > When build project, this patch existed yesterday. > > But now, the patch is missed. > > Could you please help to check it? > > linux-yocto-dev is now 5.4, so all existing branches are gone, support > and work in -dev now needs to rebased and sent as pull requests. > > > > > I also another similar patch that is requested to be merged into > > linux-yocto-5.2, branch is v5.2/standard/base, could you please help to > > check whether it is merged, too? > > I'll double check 5.2. I'm not sure where the patch went .. but I just added it to v5.2/standard/base and merged it to the BSPs. Bruce > > Bruce > > > > > Thanks, > > Limeng > > > > > > > Bruce > > > > > > > > > > > r8a7795.dtsi | 32 > > > > 1 file changed, 32 insertions(+) > > > > > > > > > > > > thanks, > > > > Limeng > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: arm64: dts: r8a7795: Add CPUIdle support for all CPU core
On Tue, Oct 22, 2019 at 3:06 AM Li, Meng wrote: > > > > > -Original Message- > > From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com] > > Sent: Saturday, October 19, 2019 12:51 PM > > To: Li, Meng > > Cc: linux-yocto@yoctoproject.org > > Subject: Re: [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: arm64: > > dts: r8a7795: Add CPUIdle support for all CPU core > > > > In message: [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: arm64: > > dts: r8a7795: Add CPUIdle support for all CPU core > > on 15/10/2019 meng...@windriver.com wrote: > > > > > From: Limeng > > > > > > Hi Bruce, > > > > > > I get below patch from SDK kernel to support cpu idle feature, and intend > > to merge it into yocto community. > > > > > > 0001-arm64-dts-r8a7795-Add-CPUIdle-support-for-all-CPU-co.patch > > > > > > Could you please merge this patch into linux-yocto-dev, branch is > > standard/base? > > > > Looks fine to me, this is now merged. > > > > Hi Bruce, > > I found a strange thing. > When build project, this patch existed yesterday. > But now, the patch is missed. > Could you please help to check it? linux-yocto-dev is now 5.4, so all existing branches are gone, support and work in -dev now needs to rebased and sent as pull requests. > > I also another similar patch that is requested to be merged into > linux-yocto-5.2, branch is v5.2/standard/base, could you please help to check > whether it is merged, too? I'll double check 5.2. Bruce > > Thanks, > Limeng > > > > Bruce > > > > > > > > r8a7795.dtsi | 32 > > > 1 file changed, 32 insertions(+) > > > > > > > > > thanks, > > > Limeng -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto preempt-rt v5.2][PATCH 0/1] kmemleak: Change the lock of kmemleak_object to raw_spinlock_t
I already have the latest 5.2 -stable and -rt under test, so I'll finish those rather than merging this. Bruce On Tue, Oct 22, 2019 at 3:23 AM Yongxin Liu wrote: > > Hi Bruce, > > Could you help to merge this patch to linux-yocto v5.2/standard/preempt-rt? > This patch is only for RT kernel. > It was added in v5.2 rt11. > I know you periodically pull RT patches. But could you help to merge this > patch in advance? > > > Liu Haitao (1): > kmemleak: Change the lock of kmemleak_object to raw_spinlock_t > > mm/kmemleak.c | 72 > +-- > 1 file changed, 36 insertions(+), 36 deletions(-) > > > Thanks, > Yongxin -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/1] xilinx-zyqn: Move disable_nonboot_cpus() in front of local_irq_disable()
On Mon, Oct 21, 2019 at 6:45 AM Michal Simek wrote:
>
> On 21. 10. 19 10:45, Quanyang Wang wrote:
> > Hi Michal,
> >
> > On 10/21/19 4:16 PM, Michal Simek wrote:
> >> On 21. 10. 19 7:50, quanyang.w...@windriver.com wrote:
> >>> From: Quanyang Wang
> >>>
> >>> When run kdump with enabling CONFIG_DEBUG_PREEMPT, there is a calltrace
> >>> as below:
> >>>
> >>> BUG: using smp_processor_id() in preemptible [] code: sh/303
> >>> caller is machine_crash_shutdown+0x2c/0xe8
> >>> CPU: 0 PID: 303 Comm: sh Kdump: loaded Not tainted
> >>> 5.2.20-yocto-standard #1
> >>> Hardware name: Xilinx Zynq Platform
> >>> [<80112ff4>] (unwind_backtrace) from [<8010ca4c>] (show_stack+0x18/0x1c)
> >>> [<8010ca4c>] (show_stack) from [<809b000c>] (dump_stack+0x70/0x8c)
> >>> [<809b000c>] (dump_stack) from [<80549a14>]
> >>> (debug_smp_processor_id+0xd4/0x118)
> >>> [<80549a14>] (debug_smp_processor_id) from [<80111428>]
> >>> (machine_crash_shutdown+0x2c/0xe8)
> >>> [<80111428>] (machine_crash_shutdown) from [<801afe24>]
> >>> (__crash_kexec+0x70/0xd0)
> >>> [<801afe24>] (__crash_kexec) from [<801259b4>] (panic+0x110/0x324)
> >>> [<801259b4>] (panic) from [<805f7018>] (sysrq_handle_crash+0x18/0x1c)
> >>> [<805f7018>] (sysrq_handle_crash) from [<805f7584>]
> >>> (__handle_sysrq+0x9c/0x14c)
> >>> [<805f7584>] (__handle_sysrq) from [<805f79e8>]
> >>> (write_sysrq_trigger+0x5c/0x6c)
> >>> [<805f79e8>] (write_sysrq_trigger) from [<8031e850>]
> >>> (proc_reg_write+0x78/0x8c)
> >>> [<8031e850>] (proc_reg_write) from [<802b1b28>] (vfs_write+0xc0/0x154)
> >>> [<802b1b28>] (vfs_write) from [<802b2a64>] (ksys_write+0x6c/0xd4)
> >>> [<802b2a64>] (ksys_write) from [<80101000>] (ret_fast_syscall+0x0/0x54)
> >>> Exception stack(0xba157fa8 to 0xba157ff0)
> >>> 7fa0: 0002 005ab930 0001 005ab930 0002
> >>> 7fc0: 0002 005ab930 76fa2290 0004 76f3d124 76f3cc8c
> >>>
> >>> 7fe0: 0004 7edec940 76edbfff 76e67d16
> >>>
> >>> This is because that the function disable_nonboot_cpus is called in
> >>> order to make sure that the crash kernel runs in the boot CPU(cpu0).
> >>> And it will enable local irq by calling as below:
> >>>
> >>> disable_nonboot_cpus
> >>> -> freeze_secondary_cpus
> >>>-> _cpu_down
> >>> -> percpu_down_write
> >>> -> rcu_sync_enter
> >>> -> spin_unlock_irq(>rss_lock)
> >>>-> local_irq_enable()
> >>>
> >>> Then the functions including smp_processor_id() behind
> >>> disable_nonboot_cpus
> >>> will run at the irq-enabled context, and this will trigger the
> >>> calltrace.
> >>>
> >>> So move disable_nonboot_cpus() in front of local_irq_disable() to avoid
> >>> it since disable_nonboot_cpus() not need run at an atomic context.
> >>>
> >>> Signed-off-by: Quanyang Wang
> >>> ---
> >>> arch/arm/kernel/machine_kexec.c | 3 ++-
> >>> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/arch/arm/kernel/machine_kexec.c
> >>> b/arch/arm/kernel/machine_kexec.c
> >>> index 654f2b1f9ac0..83d2025a4ab1 100644
> >>> --- a/arch/arm/kernel/machine_kexec.c
> >>> +++ b/arch/arm/kernel/machine_kexec.c
> >>> @@ -145,9 +145,10 @@ static void machine_kexec_mask_interrupts(void)
> >>> void machine_crash_shutdown(struct pt_regs *regs)
> >>> {
> >>> -local_irq_disable();
> >>> disable_nonboot_cpus();
> >>> +local_irq_disable();
> >>> +
> >>> crash_smp_send_stop();
> >>> crash_save_cpu(regs, smp_processor_id());
> >>>
> >> ok. Can you please check before this if your usecases work without
> >> disable_nonboot_cpus(). This patch was done pretty long time ago where
> >> there was an issue with kexec. Long time ago I was talking to arm-soc
> >> maintainers about this and they told me that mainline code should work
> >> fine without any need to call disable_nonboot_cpus().
> >> It means if kexec is working fine we can revert origin patch and use
> >> what mainline is using.
> >
> > It seems that the issue is still there. When crash at cpu1 and crash
> > kernel runs at cpu1,
> >
> > it will hang, the log is as below:
> >
> > root@xilinx-zynq:~# sh 1.sh
> > syscall kexec_file_load not available.
> > sysrq: Trigger a crash
> > Kernel panic - not syncing: sysrq triggered crash
> > CPU: 1 PID: 308 Comm: sh Kdump: loaded Not tainted 5.2.20-yocto-standard #4
> > Hardware name: Xilinx Zynq Platform
> > [<80112eb0>] (unwind_backtrace) from [<8010cc04>] (show_stack+0x18/0x1c)
> > [<8010cc04>] (show_stack) from [<8094f8f4>] (dump_stack+0x70/0x8c)
> > [<8094f8f4>] (dump_stack) from [<801256f4>] (panic+0xf8/0x320)
> > [<801256f4>] (panic) from [<805dbeb0>] (sysrq_handle_crash+0x18/0x1c)
> > [<805dbeb0>] (sysrq_handle_crash) from [<805dc3b8>]
> > (__handle_sysrq+0x9c/0x148)
> > [<805dc3b8>] (__handle_sysrq) from [<805dc804>]
> > (write_sysrq_trigger+0x5c/0x6c)
> > [<805dc804>] (write_sysrq_trigger) from [<8031b040>]
> > (proc_reg_write+0x78/0x8c)
> > [<8031b040>] (proc_reg_write) from [<802aeec4>] (vfs_write+0xc0/0x154)
> > [<802aeec4>]
Re: [linux-yocto] [kernel-cache master/yocto-5.2][PATCH 0/1] xilinx-zynqmp: delete obsolete kernel options
In message: [linux-yocto][kernel-cache master/yocto-5.2][PATCH 0/1] xilinx-zynqmp: delete obsolete kernel options on 15/10/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, Michal, > > This patch is to delete some obsolete kernel options. Now delete them > or else yocto will throw out build warning infos. > > Could you please merge this patch into yocto-kernel-cache, branch is master > and yocto-5.2? merged. Bruce > > Thanks, > Quanyang > > Quanyang Wang (1): > xilinx-zynqmp: delete obsolete kernel options > > bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 7 +-- > 1 file changed, 1 insertion(+), 6 deletions(-) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: arm64: dts: r8a7795: Add CPUIdle support for all CPU core
In message: [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: arm64: dts: r8a7795: Add CPUIdle support for all CPU core on 15/10/2019 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > I get below patch from SDK kernel to support cpu idle feature, and intend to > merge it into yocto community. > > 0001-arm64-dts-r8a7795-Add-CPUIdle-support-for-all-CPU-co.patch > > Could you please merge this patch into linux-yocto-dev, branch is > standard/base? Looks fine to me, this is now merged. Bruce > > r8a7795.dtsi | 32 > 1 file changed, 32 insertions(+) > > > thanks, > Limeng -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache][PATCH 0/1] xilinx-zynqmp: add kernel options for ZynqMP PL Programming
In message: [linux-yocto][kernel-cache][PATCH 0/1] xilinx-zynqmp: add kernel options for ZynqMP PL Programming on 17/10/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, Michal, > > Would you please help review and merge this patch to > yocto-kernel-cache's branch yocto-5.2 and master? merged. Bruce > > Thanks, > Quanyang > > Quanyang Wang (1): > xilinx-zynqmp: add kernel options for ZynqMP PL Programming > > bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 4 > 1 file changed, 4 insertions(+) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH v5.2] nvme-pci: Set the prp2 correctly when using more than 4k page
In message: [PATCH v5.2] nvme-pci: Set the prp2 correctly when using more than
4k page
on 19/10/2019 Kevin Hao wrote:
> commit a4f40484e7f1dff56bb9f286cc59ffa36e0259eb from
> git://git.infradead.org/nvme.git
>
> In the current code, the nvme is using a fixed 4k PRP entry size,
> but if the kernel use a page size which is more than 4k, we should
> consider the situation that the bv_offset may be larger than the
> dev->ctrl.page_size. Otherwise we may miss setting the prp2 and then
> cause the command can't be executed correctly.
>
> Fixes: dff824b2aadb ("nvme-pci: optimize mapping of small single segment
> requests")
> Cc: sta...@vger.kernel.org
> Reviewed-by: Christoph Hellwig
> Signed-off-by: Kevin Hao
> Signed-off-by: Keith Busch
> ---
> Hi Bruce,
>
> This patch has already been merged into nvme-5.4 and I also CCed
> sta...@vger.kernel.org,
> so in theory it could propagate to linux-yocto via the stable update.
> But this issue cause a critical malfunction for the nvme interface and
> block our validation for it. So I would like to pick this patch ASAP.
> We should merge this into v5.2/standard/base branch.
No problem. I was just looking at the queue, and since this was already
reviewed upstream and safe .. I jumped it to the front and have merged
and pushed it to the repo.
Bruce
>
> drivers/nvme/host/pci.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 4b181969c432..869f462e6b6e 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -773,7 +773,8 @@ static blk_status_t nvme_setup_prp_simple(struct nvme_dev
> *dev,
> struct bio_vec *bv)
> {
> struct nvme_iod *iod = blk_mq_rq_to_pdu(req);
> - unsigned int first_prp_len = dev->ctrl.page_size - bv->bv_offset;
> + unsigned int offset = bv->bv_offset & (dev->ctrl.page_size - 1);
> + unsigned int first_prp_len = dev->ctrl.page_size - offset;
>
> iod->first_dma = dma_map_bvec(dev->dev, bv, rq_dma_dir(req), 0);
> if (dma_mapping_error(dev->dev, iod->first_dma))
> --
> 2.14.4
>
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 2/2] arch: arm64: dts: add overlay dts file
On Mon, Oct 14, 2019 at 6:19 AM Quanyang Wang
wrote:
>
>
> On 10/14/19 6:00 PM, Michal Simek wrote:
> > On 14. 10. 19 11:34, Quanyang Wang wrote:
> >> On 10/14/19 3:58 PM, Michal Simek wrote:
> >>> On 14. 10. 19 9:55, Quanyang Wang wrote:
> On 10/14/19 2:05 PM, Michal Simek wrote:
> > On 13. 10. 19 15:33, quanyang.w...@windriver.com wrote:
> >> From: MengLi
> >>
> >> Add overlay dts file for updating FPGA bitstream file on
> >> zynqmp platform.
> >>
> >> Signed-off-by: Meng Li
> >> Signed-off-by: Quanyang Wang
> >> ---
> >>arch/arm64/boot/dts/xilinx/Makefile| 1 +
> >>.../dts/xilinx/zynqmp-zcu102-fpga-update.dts | 18
> >> ++
> >>2 files changed, 19 insertions(+)
> >>create mode 100644
> >> arch/arm64/boot/dts/xilinx/zynqmp-zcu102-fpga-update.dts
> >>
> >> diff --git a/arch/arm64/boot/dts/xilinx/Makefile
> >> b/arch/arm64/boot/dts/xilinx/Makefile
> >> index bec4746fe721..d56c449988d0 100644
> >> --- a/arch/arm64/boot/dts/xilinx/Makefile
> >> +++ b/arch/arm64/boot/dts/xilinx/Makefile
> >> @@ -13,6 +13,7 @@ dtb-$(CONFIG_ARCH_ZYNQMP) += zynqmp-zcu100-revC.dtb
> >>dtb-$(CONFIG_ARCH_ZYNQMP) += zynqmp-zcu102-revA.dtb
> >>dtb-$(CONFIG_ARCH_ZYNQMP) += zynqmp-zcu102-revB.dtb
> >>dtb-$(CONFIG_ARCH_ZYNQMP) += zynqmp-zcu102-rev1.0.dtb
> >> +dtb-$(CONFIG_ARCH_ZYNQMP) += zynqmp-zcu102-fpga-update.dtb
> >>dtb-$(CONFIG_ARCH_ZYNQMP) += zynqmp-zcu104-revA.dtb
> >>dtb-$(CONFIG_ARCH_ZYNQMP) += zynqmp-zcu104-revC.dtb
> >>dtb-$(CONFIG_ARCH_ZYNQMP) += zynqmp-zcu106-revA.dtb
> >> diff --git
> >> a/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-fpga-update.dts
> >> b/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-fpga-update.dts
> >> new file mode 100644
> >> index ..f1e1506b6210
> >> --- /dev/null
> >> +++ b/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-fpga-update.dts
> >> @@ -0,0 +1,18 @@
> >> +// overlay dts file.
> >> +/dts-v1/;
> >> +/plugin/;
> >> +
> >> +/ {
> >> +fragment@0 {
> >> +target-path = "/fpga-full";
> >> +#address-cells = <1>;
> >> +#size-cells = <1>;
> >> +
> >> +__overlay__ {
> >> +#address-cells = <2>;
> >> +#size-cells = <2>;
> >> +
> >> +firmware-name = "system.bit.bin";
> >> +};
> >> +};
> >> +};
> >>
> > I understand what you want to do but not sure why you think that
> > this is
> > the best way how to do it.
> Hi Michal,
>
> This patch is based on the url:
>
> https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841847/Solution+ZynqMP+PL+Programming#x-Programming+the+PL+through+Linux
>
>
> "FPGA programming using Device Tree Overlay (DTO)".
>
> We will describe how to programming FPGA by using 2 methods in README
> for our customer:
>
> one is FPGA programming using sysfs attributes
>
>
>
> And the other is FPGA programming using Device Tree Overlay (DTO)
>
>
>
> This patch is used for the second method.
>
> Is there any better way to do it?
>
> >>> It is not about that using fragments is incorrect. It is about reasons
> >>> to include this dts file to Linux source code. Because this fragment is
> >>> just doing programming without anything else. It means it is coupled
> >>> with also description what it is in DT which is missing here.
> >>> It means this is just part A (with system.bit.bin generic name - which
> >>> is not fully accurate) and part B is missing.
> >>> In part B there should be what you are including with clock/reset and IP
> >>> part.
> >>> That's why my question remains if make even sense to merge part A
> >>> without any details about part B.
> >> Hi Michal,
> >>
> >> The target for this patch is to just simply test the FPGA programming
> >> function. So it changes nothing.
> >>
> >> It seems to be improper to add such a dts file to kernel source.
> >>
> >> I will transform the dts file to a text description in README or make it
> >> to be a more detailed and integral dts file in a V2 patch.
> > ok. let's see where you want to add this readme. If this targets
> > "Documentation" folder then not a problem at all.
>
> Hi Michal,
>
> Sorry for making you confuse. The README which I said about is not in
> kernel source but in WRLinux project.
>
> I mean that maybe I can just describe how to test FPGA programming in
> some place of our own Product Document
Just
Re: [linux-yocto] [PATCH v5.2] pci: octeontx2: Use a more lightweight API to get the root bus
On Mon, Oct 14, 2019 at 4:56 AM Kevin Hao wrote:
>
> In the current code, the API pci_get_domain_bus_and_slot() is used to
> get the root bus. But we would get the below call trace on rt kernel
> due to the spin_lock is used in the klist.
> BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:968
> in_atomic(): 1, irqs_disabled(): 128, pid: 1, name: swapper/0
> 3 locks held by swapper/0/1:
>#0: (ptrval) (per_cpu_ptr(_lock.lock, cpu)){}, at:
> __device_driver_lock+0x34/0x60
>#1: (ptrval) (pci_lock){}, at:
> pci_bus_write_config_word+0x40/0xa8
>#2: (ptrval) (>k_lock){+.+.}, at: klist_next+0x24/0x110
> irq event stamp: 1293008
> hardirqs last enabled at (1293007): []
> _raw_spin_unlock_irqrestore+0xa8/0xb8
> hardirqs last disabled at (1293008): []
> _raw_spin_lock_irqsave+0x38/0x80
> softirqs last enabled at (1032902): []
> raw_unhash_sk+0x74/0xb0
> softirqs last disabled at (1032891): []
> raw_unhash_sk+0x0/0xb0
> Preemption disabled at:
> [] pci_bus_write_config_word+0x40/0xa8
> CPU: 8 PID: 1 Comm: swapper/0 Not tainted 5.2.20-rt9-yocto-preempt-rt+ #12
> Hardware name: Marvell OcteonTX CN96XX board (DT)
> Call trace:
>dump_backtrace+0x0/0x140
>show_stack+0x24/0x30
>dump_stack+0xbc/0x104
>___might_sleep+0x16c/0x1d0
>rt_spin_lock+0x64/0x78
>klist_next+0x24/0x110
>bus_find_device+0x70/0xe0
>pci_get_dev_by_id+0x60/0x88
>pci_get_domain_bus_and_slot+0x5c/0xb0
>octeontx2_pem_config_write+0x84/0x3e0
>pci_bus_write_config_word+0x64/0xa8
>pci_write_config_word+0x44/0x68
>pci_setup_device+0x214/0x718
>pci_scan_single_device+0xb4/0xf8
>pci_scan_slot+0x44/0x108
>pci_scan_child_bus_extend+0x58/0x290
>pci_scan_bridge_extend+0x350/0x4f8
>pci_scan_child_bus_extend+0x1e4/0x290
>pci_scan_root_bus_bridge+0x60/0xd0
>pci_host_probe+0x20/0xb8
>pci_host_common_probe+0xf4/0x1f0
>octeontx2_pem_probe+0x2c/0x38
>platform_drv_probe+0x58/0xa8
>really_probe+0xe0/0x288
>driver_probe_device+0x5c/0xf0
>device_driver_attach+0x74/0x80
>__driver_attach+0x64/0xe0
>bus_for_each_dev+0x84/0xd8
>driver_attach+0x30/0x40
>bus_add_driver+0x190/0x1f0
>driver_register+0x64/0x110
>__platform_driver_register+0x54/0x60
>octeontx2_pem_driver_init+0x20/0x28
>do_one_initcall+0xa8/0x468
>kernel_init_freeable+0x514/0x5b8
>kernel_init+0x18/0x108
>ret_from_fork+0x10/0x1c
>
> Actually we can use a more lightweight API to get the rootbus without
> acquiring any lock, then fix this issue.
>
> Signed-off-by: Kevin Hao
> ---
>
> Hi Bruce,
>
> Please help merge this to the following branches:
>
> linux-yocto:
> v5.2/standard/cn96xx
> v5.2/standard/preempt-rt/cn96xx
merged
>
> linux-yocto-dev:
> standard/cn96xx
.. and merged. But I'm about a day away from replacing linux-yocto-dev
with v5.4-rc3, so be prepared that this will change shortly.
Bruce
>
> drivers/pci/controller/pci-octeontx2-pem.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/controller/pci-octeontx2-pem.c
> b/drivers/pci/controller/pci-octeontx2-pem.c
> index 90b5537e8cdb..1e14dc065322 100644
> --- a/drivers/pci/controller/pci-octeontx2-pem.c
> +++ b/drivers/pci/controller/pci-octeontx2-pem.c
> @@ -335,10 +335,10 @@ static void octeontx2_be_workaround_init(struct pci_bus
> *bus)
> static void octeontx2_be_workaround(struct pci_bus *bus, int where,
> int size, u32 val)
> {
> - struct pci_dev *rc;
> + struct pci_host_bridge *rc;
> u32 reg, be = 0;
>
> - rc = pci_get_domain_bus_and_slot(pci_domain_nr(bus), 0, 0);
> + rc = pci_find_host_bridge(bus);
>
> /* Setup RAS to inject one error */
> octeontx2_be_workaround_init(rc->bus);
> --
> 2.14.4
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH v5.2 rt] mmc: cavium-thunderx: Drop the IRQF_NO_THREAD constraint
In message: [PATCH v5.2 rt] mmc: cavium-thunderx: Drop the IRQF_NO_THREAD
constraint
on 10/10/2019 Kevin Hao wrote:
> The IRQF_NO_THREAD is added by a Marvell SDK patch 238e623e1024 ("mmc:
> cavium: fix swiotlb buffer is full") in order to get back some of the
> performance loss. But in some cases (such as rt kernel), we do need the
> capability to thread irq handler. Otherwise we would get warnings because
> the normal spin lock is used in the irq handler. So drop this constraint.
>
> Signed-off-by: Kevin Hao
> ---
> Hi Bruce,
>
> Please merge this to v5.2/standard/preempt-rt/cn96xx
merged
Bruce
>
> drivers/mmc/host/cavium-thunderx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/cavium-thunderx.c
> b/drivers/mmc/host/cavium-thunderx.c
> index 7fbf33e34217..3afe788d0d9e 100644
> --- a/drivers/mmc/host/cavium-thunderx.c
> +++ b/drivers/mmc/host/cavium-thunderx.c
> @@ -49,7 +49,7 @@ static int thunder_mmc_register_interrupts(struct
> cvm_mmc_host *host,
> /* register interrupts */
> for (i = 0; i < nvec; i++) {
> ret = devm_request_irq(>dev, pci_irq_vector(pdev, i),
> -cvm_mmc_interrupt, IRQF_NO_THREAD,
> +cvm_mmc_interrupt, 0,
> cvm_mmc_irq_names[i], host);
> if (ret)
> return ret;
> --
> 2.14.4
>
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH v5.2] tracing/arm64: Have max stack tracer handle the case of return address after data
merged
Bruce
In message: [PATCH v5.2] tracing/arm64: Have max stack tracer handle the
case of return address after data
on 10/10/2019 Kevin Hao wrote:
> From: "Steven Rostedt (VMware)"
>
> commit f7edb451fa51e44e62177347ea7850aa0e901ea5 upstream
>
> Most archs (well at least x86) store the function call return address on the
> stack before storing the local variables for the function. The max stack
> tracer depends on this in its algorithm to display the stack size of each
> function it finds in the back trace.
>
> Some archs (arm64), may store the return address (from its link register)
> just before calling a nested function. There's no reason to save the link
> register on leaf functions, as it wont be updated. This breaks the algorithm
> of the max stack tracer.
>
> Add a new define ARCH_FTRACE_SHIFT_STACK_TRACER that an architecture may set
> if it stores the return address (link register) after it stores the
> function's local variables, and have the stack trace shift the values of the
> mapped stack size to the appropriate functions.
>
> Link: 20190802094103.163576-1-jiping@windriver.com
>
> Reported-by: Jiping Ma
> Acked-by: Will Deacon
> Signed-off-by: Steven Rostedt (VMware)
> Signed-off-by: Kevin Hao
> ---
> Hi Bruce,
>
> This fixes the issue that the stack usage can't be got from ftrace on
> arm64 arch.
>
> arch/arm64/include/asm/ftrace.h | 13 +
> kernel/trace/trace_stack.c | 14 ++
> 2 files changed, 27 insertions(+)
>
> diff --git a/arch/arm64/include/asm/ftrace.h b/arch/arm64/include/asm/ftrace.h
> index 5ab5200b2bdc..d48667b04c41 100644
> --- a/arch/arm64/include/asm/ftrace.h
> +++ b/arch/arm64/include/asm/ftrace.h
> @@ -14,6 +14,19 @@
> #define MCOUNT_ADDR ((unsigned long)_mcount)
> #define MCOUNT_INSN_SIZE AARCH64_INSN_SIZE
>
> +/*
> + * Currently, gcc tends to save the link register after the local variables
> + * on the stack. This causes the max stack tracer to report the function
> + * frame sizes for the wrong functions. By defining
> + * ARCH_FTRACE_SHIFT_STACK_TRACER, it will tell the stack tracer to expect
> + * to find the return address on the stack after the local variables have
> + * been set up.
> + *
> + * Note, this may change in the future, and we will need to deal with that
> + * if it were to happen.
> + */
> +#define ARCH_FTRACE_SHIFT_STACK_TRACER 1
> +
> #ifndef __ASSEMBLY__
> #include
>
> diff --git a/kernel/trace/trace_stack.c b/kernel/trace/trace_stack.c
> index 5d16f73898db..642a850af81a 100644
> --- a/kernel/trace/trace_stack.c
> +++ b/kernel/trace/trace_stack.c
> @@ -158,6 +158,20 @@ static void check_stack(unsigned long ip, unsigned long
> *stack)
> i++;
> }
>
> +#ifdef ARCH_FTRACE_SHIFT_STACK_TRACER
> + /*
> + * Some archs will store the link register before calling
> + * nested functions. This means the saved return address
> + * comes after the local storage, and we need to shift
> + * for that.
> + */
> + if (x > 1) {
> + memmove(_trace_index[0], _trace_index[1],
> + sizeof(stack_trace_index[0]) * (x - 1));
> + x--;
> + }
> +#endif
> +
> stack_trace_nr_entries = x;
>
> if (task_stack_end_corrupted(current)) {
> --
> 2.14.4
>
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH v5.2] arm64: Remove unneeded rcu_read_lock from debug handlers
merged.
Bruce
In message: [PATCH v5.2] arm64: Remove unneeded rcu_read_lock from debug
handlers
on 09/10/2019 Kevin Hao wrote:
> From: Masami Hiramatsu
>
> commit 760d8ed069c4e32a92e2ba251a3b0d9a87a3e771 upstream
>
> Remove rcu_read_lock()/rcu_read_unlock() from debug exception
> handlers since we are sure those are not preemptible and
> interrupts are off.
>
> Acked-by: Paul E. McKenney
> Signed-off-by: Masami Hiramatsu
> Signed-off-by: Will Deacon
> Signed-off-by: Kevin Hao
> ---
>
> This fixes a call trace when running the kgdb testcase.
>
> arch/arm64/kernel/debug-monitors.c | 14 --
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm64/kernel/debug-monitors.c
> b/arch/arm64/kernel/debug-monitors.c
> index f8719bd30850..48222a4760c2 100644
> --- a/arch/arm64/kernel/debug-monitors.c
> +++ b/arch/arm64/kernel/debug-monitors.c
> @@ -207,16 +207,16 @@ static int call_step_hook(struct pt_regs *regs,
> unsigned int esr)
>
> list = user_mode(regs) ? _step_hook : _step_hook;
>
> - rcu_read_lock();
> -
> + /*
> + * Since single-step exception disables interrupt, this function is
> + * entirely not preemptible, and we can use rcu list safely here.
> + */
> list_for_each_entry_rcu(hook, list, node) {
> retval = hook->fn(regs, esr);
> if (retval == DBG_HOOK_HANDLED)
> break;
> }
>
> - rcu_read_unlock();
> -
> return retval;
> }
> NOKPROBE_SYMBOL(call_step_hook);
> @@ -305,14 +305,16 @@ static int call_break_hook(struct pt_regs *regs,
> unsigned int esr)
>
> list = user_mode(regs) ? _break_hook : _break_hook;
>
> - rcu_read_lock();
> + /*
> + * Since brk exception disables interrupt, this function is
> + * entirely not preemptible, and we can use rcu list safely here.
> + */
> list_for_each_entry_rcu(hook, list, node) {
> unsigned int comment = esr & ESR_ELx_BRK64_ISS_COMMENT_MASK;
>
> if ((comment & ~hook->mask) == hook->imm)
> fn = hook->fn;
> }
> - rcu_read_unlock();
>
> return fn ? fn(regs, esr) : DBG_HOOK_ERROR;
> }
> --
> 2.14.4
>
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH v5.2] arm64: Remove unneeded rcu_read_lock from debug handlers
merged.
Bruce
In message: [PATCH v5.2] arm64: Remove unneeded rcu_read_lock from debug
handlers
on 09/10/2019 Kevin Hao wrote:
> From: Masami Hiramatsu
>
> commit 760d8ed069c4e32a92e2ba251a3b0d9a87a3e771 upstream
>
> Remove rcu_read_lock()/rcu_read_unlock() from debug exception
> handlers since we are sure those are not preemptible and
> interrupts are off.
>
> Acked-by: Paul E. McKenney
> Signed-off-by: Masami Hiramatsu
> Signed-off-by: Will Deacon
> Signed-off-by: Kevin Hao
> ---
>
> This fixes a call trace when running the kgdb testcase.
>
> arch/arm64/kernel/debug-monitors.c | 14 --
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm64/kernel/debug-monitors.c
> b/arch/arm64/kernel/debug-monitors.c
> index f8719bd30850..48222a4760c2 100644
> --- a/arch/arm64/kernel/debug-monitors.c
> +++ b/arch/arm64/kernel/debug-monitors.c
> @@ -207,16 +207,16 @@ static int call_step_hook(struct pt_regs *regs,
> unsigned int esr)
>
> list = user_mode(regs) ? _step_hook : _step_hook;
>
> - rcu_read_lock();
> -
> + /*
> + * Since single-step exception disables interrupt, this function is
> + * entirely not preemptible, and we can use rcu list safely here.
> + */
> list_for_each_entry_rcu(hook, list, node) {
> retval = hook->fn(regs, esr);
> if (retval == DBG_HOOK_HANDLED)
> break;
> }
>
> - rcu_read_unlock();
> -
> return retval;
> }
> NOKPROBE_SYMBOL(call_step_hook);
> @@ -305,14 +305,16 @@ static int call_break_hook(struct pt_regs *regs,
> unsigned int esr)
>
> list = user_mode(regs) ? _break_hook : _break_hook;
>
> - rcu_read_lock();
> + /*
> + * Since brk exception disables interrupt, this function is
> + * entirely not preemptible, and we can use rcu list safely here.
> + */
> list_for_each_entry_rcu(hook, list, node) {
> unsigned int comment = esr & ESR_ELx_BRK64_ISS_COMMENT_MASK;
>
> if ((comment & ~hook->mask) == hook->imm)
> fn = hook->fn;
> }
> - rcu_read_unlock();
>
> return fn ? fn(regs, esr) : DBG_HOOK_ERROR;
> }
> --
> 2.14.4
>
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto v5.2][PATCH 0/3] iwlwifi/mvm related patches from mainline kernel
In message: [linux-yocto][linux-yocto v5.2][PATCH 0/3] iwlwifi/mvm related patches from mainline kernel on 09/10/2019 Yongxin Liu wrote: > Hi Bruce, > > Those three patches are from mainline kernel without any change. > They exist since v5.3-rc4. Please help to backport to linux-yocto v5.2. > > The second commit fixes the following calltrace. > > Call Trace: > dump_stack+0x4f/0x6a > ? worker_thread+0xd9/0x3e0 > ___might_sleep.cold+0xd1/0xe2 > __might_sleep+0x4b/0x80 > mutex_lock+0x21/0x50 > iwl_mvm_rs_rate_init+0x87/0xc50 [iwlmvm] merged. Bruce > > Gregory Greenman (3): > iwlwifi: mvm: add a wrapper around rs_tx_status to handle locks > iwlwifi: mvm: replace RS mutex with a spin_lock > iwlwifi: mvm: fix possible out-of-bounds read when accessing lq_info > > drivers/net/wireless/intel/iwlwifi/mvm/rs.c | 542 > ++- > drivers/net/wireless/intel/iwlwifi/mvm/rs.h | 6 +- > drivers/net/wireless/intel/iwlwifi/mvm/sta.c | 6 +- > drivers/net/wireless/intel/iwlwifi/mvm/sta.h | 1 - > 4 files changed, 275 insertions(+), 280 deletions(-) > > -- > 2.14.4 > > > Thanks, > Yongxin -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 2/2] arm: dts: zynq: update coresight device node
On Wed, Oct 9, 2019 at 9:39 AM Michal Simek wrote:
>
> Hi,
>
> On 09. 10. 19 4:38, quanyang.w...@windriver.com wrote:
> > From: Quanyang Wang
> >
> > Using new compatible value for funnel and replicator device nodes,
> > and use correct unit-address.
> >
> > Signed-off-by: Quanyang Wang
> > ---
> > arch/arm/boot/dts/zynq-7000.dtsi | 14 +++---
> > 1 file changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/zynq-7000.dtsi
> > b/arch/arm/boot/dts/zynq-7000.dtsi
> > index 5602f4f3ad1c..9b8f46d25d38 100644
> > --- a/arch/arm/boot/dts/zynq-7000.dtsi
> > +++ b/arch/arm/boot/dts/zynq-7000.dtsi
> > @@ -447,8 +447,8 @@
> > };
> > };
> >
> > - funnel@0,f8804000 {
> > - compatible = "arm,coresight-funnel", "arm,primecell";
> > + funnel@f8804000 {
> > + compatible = "arm,coresight-static-funnel",
> > "arm,primecell";
> > reg = <0xf8804000 0x1000>;
> > clocks = < 27>, < 46>, < 47>;
> > clock-names = "apb_pclk", "dbg_trc", "dbg_apb";
> > @@ -503,7 +503,7 @@
> > };
> >
> > replicator {
> > - compatible = "arm,coresight-replicator";
> > + compatible = "arm,coresight-static-replicator";
> > clocks = < 27>, < 46>, < 47>;
> > clock-names = "apb_pclk", "dbg_trc", "dbg_apb";
> >
> > @@ -536,8 +536,8 @@
> > };
> > };
> >
> > - itm@0,f8805000 {
> > - compatible = "arm,coresight-etm3x", "arm,primecell";
> > + /* ITM is not supported by kernel, only leave device node
> > here */
> > + itm@f8805000 {
> > reg = <0xf8805000 0x1000>;
> > clocks = < 27>, < 46>, < 47>;
> > clock-names = "apb_pclk", "dbg_trc", "dbg_apb";
> > @@ -549,7 +549,7 @@
> > };
> > };
> >
> > - ptm@0,f889c000 {
> > + ptm@f889c000 {
> > compatible = "arm,coresight-etm3x", "arm,primecell";
> > reg = <0xf889c000 0x1000>;
> > clocks = < 27>, < 46>, < 47>;
> > @@ -562,7 +562,7 @@
> > };
> > };
> >
> > - ptm@0,f889d000 {
> > + ptm@f889d000 {
> > compatible = "arm,coresight-etm3x", "arm,primecell";
> > reg = <0xf889d000 0x1000>;
> > clocks = < 27>, < 46>, < 47>;
> >
>
>
> I don't think this is enough. I have attached the patch against mainline
> how I think it should look like.
Crap. I was a minute too early. I've reverted what I queued and will
wait for a v2.
Bruce
>
> M
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/2] patches for zynq
In message: [linux-yocto][kernel v5.2/standard/xlnx-soc][PATCH 0/2] patches for zynq on 09/10/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, Michal, > > There are 2 patches. One is fixing compile warning which is triggered by > new version gcc 9.2.0. And the other is changed according to Michal's > suggestions. > > Would you please help review and merge these patches to linux-yocto > v5.2/standard/xlnx-soc branch? They look fine to me, so I've pushed them to the branch. Bruce > > Thanks, > Quanyang > > Quanyang Wang (2): > arm: zynq: delete AFLAGS_suspend.o to fix compile warning > arm: dts: zynq: update coresight device node > > arch/arm/boot/dts/zynq-7000.dtsi | 14 +++--- > arch/arm/mach-zynq/Makefile | 1 - > 2 files changed, 7 insertions(+), 8 deletions(-) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH][v5.2/standard/preempt-rt/base] printk: devkmsg: read: Return EPIPE when the first message user-space wants has gone
I didn't merge this directly, but instead updated the -rt branches to
-rt9 .. so I got your change that way.
Cheers,
Bruce
On Sun, Sep 29, 2019 at 5:36 AM wrote:
>
> From: He Zhe
>
> This fixes ltp failure,
> kmsg01.c:444: FAIL: read returned: 56: SUCCESS
>
> When user-space wants to read the first message, that is when user->seq
> is 0, and that message has gone, it currently automatically resets
> user->seq to current first seq. This mis-aligns with mainline kernel.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/dev-kmsg#n39
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/printk/printk.c#n899
>
> We should inform user-space that what it wants has gone by returning EPIPE
> in such scenario.
>
> Link: https://lore.kernel.org/linux-rt-users/8736gls1aj@linutronix.de/T/#t
>
> Signed-off-by: He Zhe
> ---
> kernel/printk/printk.c | 12
> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index e3fa33f..58c545a 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -703,14 +703,10 @@ static ssize_t devkmsg_read(struct file *file, char
> __user *buf,
> goto out;
> }
>
> - if (user->seq == 0) {
> - user->seq = seq;
> - } else {
> - user->seq++;
> - if (user->seq < seq) {
> - ret = -EPIPE;
> - goto restore_out;
> - }
> + user->seq++;
> + if (user->seq < seq) {
> + ret = -EPIPE;
> + goto restore_out;
> }
>
> msg = (struct printk_log *)>msgbuf[0];
> --
> 2.7.4
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] powerpc/603: Fix handling of the DIRTY flag
In message: [linux-yocto][PATCH] powerpc/603: Fix handling of the DIRTY flag
on 24/09/2019 zhe...@windriver.com wrote:
> From: Christophe Leroy
>
> commit 415480dce2ef03bb8335deebd2f402f475443ce0 upstream
>
> If a page is already mapped RW without the DIRTY flag, the DIRTY
> flag is never set and a TLB store miss exception is taken forever.
>
> This is easily reproduced with the following app:
>
> void main(void)
> {
> volatile char *ptr = mmap(0, 4096, PROT_READ | PROT_WRITE, MAP_SHARED |
> MAP_ANONYMOUS, -1, 0);
>
> *ptr = *ptr;
> }
>
> When DIRTY flag is not set, bail out of TLB miss handler and take
> a minor page fault which will set the DIRTY flag.
>
> Fixes: f8b58c64eaef ("powerpc/603: let's handle PAGE_DIRTY directly")
> Cc: sta...@vger.kernel.org # v5.1+
> Reported-by: Doug Crawford
> Signed-off-by: Christophe Leroy
> Signed-off-by: Michael Ellerman
> Link:
> https://lore.kernel.org/r/80432f71194d7ee75b2f5043ecf1501cf1cca1f3.1566196646.git.christophe.le...@c-s.fr
> Signed-off-by: He Zhe
> ---
> This is for v5.2/standard/fsl-mpc8315e-rdb. It fixes potential system hang
> without any direct warning or error which has not been observed on qemuppc.
>
> It has not been ported to stable tree.
but at least is has been cc'd to stable. I'll watch for it to show up in my
future 5.2 -stabe updates.
Cheers,
Bruce
>
> arch/powerpc/kernel/head_32.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/kernel/head_32.S b/arch/powerpc/kernel/head_32.S
> index f255e22..534dd27 100644
> --- a/arch/powerpc/kernel/head_32.S
> +++ b/arch/powerpc/kernel/head_32.S
> @@ -557,9 +557,9 @@ DataStoreTLBMiss:
> cmplw 0,r1,r3
> mfspr r2, SPRN_SPRG_PGDIR
> #ifdef CONFIG_SWAP
> - li r1, _PAGE_RW | _PAGE_PRESENT | _PAGE_ACCESSED
> + li r1, _PAGE_RW | _PAGE_DIRTY | _PAGE_PRESENT | _PAGE_ACCESSED
> #else
> - li r1, _PAGE_RW | _PAGE_PRESENT
> + li r1, _PAGE_RW | _PAGE_DIRTY | _PAGE_PRESENT
> #endif
> bge-112f
> lis r2, (swapper_pg_dir - PAGE_OFFSET)@ha /* if kernel address,
> use */
> --
> 2.7.4
>
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/3] patches for zynq7000
In message: [linux-yocto][kernel v5.2/standard/xlnx-soc][PATCH 0/3] patches for zynq7000 on 23/09/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > > Would you please help merge these patches to linux-yocto > v5.2/standard/xlnx-soc branch? These are now merged. Are these changes already done upstream, or applicable to upstream ? I just want to make sure we aren't only fixes these in the yocto kernel when there are other places that we can fix as well. Bruce > > Thanks, > Quanyang > > Quanyang Wang (2): > ARM: dts: zc702: Fix I2C bus warnings > mmc: sdhci-of-arasan: Fix the incorrect soft reset operation when > runtime resuming > > Zumeng Chen (1): > arm: dts: zynq: enablement of coresight topology > > arch/arm/boot/dts/zynq-7000.dtsi | 155 + > arch/arm/boot/dts/zynq-zc702.dts | 12 +-- > drivers/mmc/host/sdhci-of-arasan.c | 2 +- > 3 files changed, 162 insertions(+), 7 deletions(-) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH v5.2] cn96xx: Another patch series for the cn96xx SoC support
In message: [PATCH v5.2] cn96xx: Another patch series for the cn96xx SoC support on 23/09/2019 Kevin Hao wrote: > Hi Bruce, > > Here is another patch series got from Marvell for the cn96xx SoC support. > It mainly include some fixes for the mmc and Ethernet. Please help me > merge this into both v5.2/standard/cn96xx and v5.2/standard/preempt-rt/cn96xx > branch. > > The following changes since commit d186856ba1914ca0fbf715fe9b0f31067dd517a4: > > mmc: cavium: Drop the aligned check for the dma address (2019-09-20 > 00:23:49 -0400) > > are available in the Git repository at: > > https://github.com/haokexin/linux v5.2/standard/cn96xx merged To ssh://git.yoctoproject.org/linux-yocto.git d186856ba191..8ddd7904ae8f v5.2/standard/cn96xx -> v5.2/standard/cn96xx 11c5ad93ebda..07da8f9ebdf6 v5.2/standard/preempt-rt/cn96xx -> v5.2/standard/preempt-rt/cn96xx Bruce > > for you to fetch changes up to 8ddd7904ae8f42c95c7b13bb877e663d39e802ac: > > octeontx2-af: Add T98 devid to PTP id table (2019-09-23 17:02:17 +0800) > > > Christina Jacob (2): > octeontx2-pf: Disply the link detected status in ethtool command > net: thunderx: Do a PCS reset upon SGMII link toggle > > Geetha sowjanya (1): > octeontx2-pf: Ignore NPC parser layer errors > > Hao Zheng (2): > octeontx2-af: add parser support for DSA, extended DSA and eDSA > octeontx2-af: combine LB_STAG and LB_QINQ to one LB ltype > > Peter Swain (4): > mmc: cavium: reorganize before vqmmc switching > mmc: cavium: slot switch by vqmmc/gpio > mmc: cavium: do not drop bus lock in tuning > mmc: cavium: use calibrated timing taps > > Subbaraya Sundeep (8): > octeontx2-pf: Fix memory leaks > octeontx2-af: Change message level to debug > octeontx2-af: Enable odd number of AF VFs also > octeontx2-pf: Use helper function for LBK VF > octeontx2-af: Use nix_smq_flush function > octeontx2-af: Always enable mcam rules for TX > octeontx2-af: Transmit packets during SMQ flush > octeontx2-pf: Add barrier to sync interface status > > Sunil Goutham (8): > octeontx2-af: Fix programming and logical issues > octeontx2-pf: Fix VF id in the FLR handler > octeontx2-pf: Fix interface init and shutdown sequence > octeontx2-pf: Use post increment STP to free pointers to Aura > octeontx2-pf: Add debug messages for MSIX alloc failure > arm64: Increase NR_IRQS to a large number > octeontx2-af: Fix compilation issue > octeontx2-pf: Fix memory leak while freeing SQBs > > Tomasz Michalec (1): > octeontx2-af: Add T98 devid to PTP id table > > Vidhya Vidhyaraman (1): > octeontx2-af: Add programmed macaddr to RVU pfvf > > Documentation/devicetree/bindings/mmc/cavium-mmc.txt | 10 +- > arch/arm64/include/asm/irq.h | 9 ++ > drivers/mmc/host/cavium-thunderx.c| 97 ++--- > drivers/mmc/host/cavium.c | 227 > - > drivers/mmc/host/cavium.h | 7 +- > drivers/net/ethernet/cavium/thunder/thunder_bgx.c | 35 ++--- > drivers/net/ethernet/marvell/octeontx2/af/cgx.c | 6 +- > drivers/net/ethernet/marvell/octeontx2/af/mbox.c | 2 +- > drivers/net/ethernet/marvell/octeontx2/af/npc.h | 9 +- > drivers/net/ethernet/marvell/octeontx2/af/npc_profile.h | 731 > +--- > drivers/net/ethernet/marvell/octeontx2/af/ptp.c | 4 + > drivers/net/ethernet/marvell/octeontx2/af/rvu.c | 12 -- > drivers/net/ethernet/marvell/octeontx2/af/rvu_cgx.c | 26 ++-- > drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c | 23 ++- > drivers/net/ethernet/marvell/octeontx2/af/rvu_fixes.c | 14 ++ > drivers/net/ethernet/marvell/octeontx2/af/rvu_fixes.h | 21 +++ > drivers/net/ethernet/marvell/octeontx2/af/rvu_nix.c | 26 ++-- > drivers/net/ethernet/marvell/octeontx2/af/rvu_npc.c | 17 +-- > drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c| 15 +- > drivers/net/ethernet/marvell/octeontx2/nic/Makefile | 2 +- > drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c | 49 ++- > drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h | 29 ++-- > drivers/net/ethernet/marvell/octeontx2/nic/otx2_ethtool.c | 33 - > drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 57 +--- > drivers/net/ethernet/marvell/octeontx2/nic/otx2_smqvf.c | 291 > + > drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.c| 9 ++ > drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.h| 6 +- > drivers/net/ethernet/marvell/octeontx2/nic/otx2_vf.c | 32 ++-- > 28
Re: [linux-yocto] [kernel-cache][PATCH 0/1] xilinx-zynq: enable coresight and xadc kernel options for xilinx-zynq bsp
In message: [linux-yocto][kernel-cache][PATCH 0/1] xilinx-zynq: enable coresight and xadc kernel options for xilinx-zynq bsp on 23/09/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > > Would you please help merge this patch to yocto-kernel-cache's branch > yocto-5.2 ? merged. Bruce > > Thanks, > Quanyang > > Quanyang Wang (1): > xilinx-zynq: enable coresight and xadc kernel options for xilinx-zynq > bsp > > bsp/xilinx-zynq/xilinx-zynq.cfg | 9 + > 1 file changed, 9 insertions(+) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] v4.18.x - stable updates comprising v4.18.45
On Sat, Sep 21, 2019 at 2:37 PM Paul Gortmaker wrote: > Bruce, Yocto kernel folks: > > Here is the *final* 4.18.x stable update "extension" primarily created > for the Yocto project, continuing from the previous v4.18.44 release. > > This final release closes out a run of 25 releases and about 4600 > backports since GregKH stopped maintenance at v4.18.20, just under a > year ago. I hope people have found the update extentsions useful during > that period; both Yocto users and "vanilla" 4.18.x users alike. > > I didn't send an announce for 4.18.44, since I wanted to finish this > 4.18.x run with the addition of the recent spectre-v1 (swapgs) variant > fixes. But I wanted to also keep them separate to ease testing and > evaluation for integrators. So the 44 is "normal" content, and the 45 > is specific to spectre-v1/swapgs content, basically. > > More specifically, the 4.18.44 release contains about 235 mainline > commits based on what was found in 4.19.51 --> 4.19.55 stable content. > > The 4.18.45 release contains the swapgs (CVE-2019-1125) content, plus a > couple powerpc CVE fixes that caught my eye. The x86 users can check: > > # cat /sys/devices/system/cpu/vulnerabilities/spectre_v1 > Mitigation: usercopy/swapgs barriers and __user pointer sanitization > > Check Documentation/admin-guide/hw-vuln/spectre.rst for more info. > > I've put this *final* 4.18.45 queue through the usual testing; build > final tag merged!! Bruce > testing on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis > and finally some sanity runtime tests on x86-64. The 4.18.44 release > also got the same independent testing prior to starting 4.18.45. > > I did the signed tag just as per the previously released versions. > Please find a signed v4.18.45 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-4.18.y.git/?h=linux-4.18.y > git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git > > for merge to standard/base in linux-yocto-4.18 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-4.18.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 4.18.x release. > > Paul. > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/2 v5.2] Add the RT support for the cn96xx
In message: [PATCH 0/2 v5.2] Add the RT support for the cn96xx
on 19/09/2019 Kevin Hao wrote:
> From: Kevin Hao
>
> This patch series adds the RT support for the Marvell cn96xx SoC. It
> includes the kernel and kernel cache patches. All the kernel patches
> except the following have already been merged into the v5.2/standard/cn96xx
> branch.
>
> 1. The patch 77eaa178a3f8 ("mmc: cavium: Drop the aligned check for the dma
> address")
>This is a new patch and also has been sent to the linux-yocto for the
>merging into v5.2/standard/cn96xx branch.
>
> 2. The patch 088d9e94823e ("arm64: Enlarge the FORCE_MAX_ZONEORDER on the
> Cavium SoC for RT:)
>This is a workaround for the bootloader setting a too big coheret_pool
>for the kernel.
My tree was in a slightly different state, so it was easier for me
to manually create the new branch, and then merge the standard kernel
BSP into it.
That included the patch you sent earlier, and I've cherry picked the
other from your github branch.
Cheers,
Bruce
>
> Thanks,
> Kevin
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/2] fix compile warning
In message: [linux-yocto][kernel v5.2/standard/xlnx-soc][PATCH 0/2] fix compile warning on 19/09/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > > Would you please help me merge the two patches into > linux-ycoto-5.2 kernel, branch v5.2/standard/xlnx-soc ? These are now merged. Bruce > > Thanks, > Quanyang > > Quanyang Wang (2): > mtd: spi-nor: change flash_info.flags from u16 to u32 to avoid compile > warning > spi: spi-mem: zynq-qspi: add is-dual support for zc706 board > > drivers/mtd/spi-nor/spi-nor.c | 2 +- > drivers/spi/spi-zynq-qspi.c | 43 +-- > 2 files changed, 42 insertions(+), 3 deletions(-) > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH v5.2] mmc: cavium: Drop the aligned check for the dma address
In message: [PATCH v5.2] mmc: cavium: Drop the aligned check for the dma
address
on 19/09/2019 Kevin Hao wrote:
> From: Kevin Hao
>
> In commit 73c1489f17e8 ("mmc: cavium: forbid unaligned DMA"), the codes
> are added to check the unaligned dma request. But at that time,
> we still don't do the dma map for the scatterlist yet. So it is
> meaningless to check the dma address. So drop of it.
>
> Signed-off-by: Kevin Hao
> ---
>
> Hi Bruce,
>
> This targets for standard/cn96xx branch.
Merged to v5.2 and linux-yocto-dev
Bruce
>
> drivers/mmc/host/cavium.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/cavium.c b/drivers/mmc/host/cavium.c
> index fc6464957df9..d724155d7eb6 100644
> --- a/drivers/mmc/host/cavium.c
> +++ b/drivers/mmc/host/cavium.c
> @@ -853,7 +853,7 @@ static void cvm_mmc_dma_request(struct mmc_host *mmc,
> /* unaligned multi-block DMA has problems, so forbid all unaligned */
> for (seg = 0; seg < mrq->data->sg_len; seg++) {
> struct scatterlist *sg = >data->sg[seg];
> - u64 align = (sg->offset | sg->length | sg->dma_address);
> + u64 align = (sg->offset | sg->length);
>
> if (!(align & 7))
> continue;
> --
> 2.14.4
>
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache master] ti-am335x: add CPU freq/idle support and correct arch bits
In message: [linux-yocto] [kernel-cache master] ti-am335x: add CPU freq/idle support and correct arch bits on 16/09/2019 Jun Miao wrote: > > > Hi Bruce. >Please help me merge the two patches to master branch of yocto-kernel-cache merged to master. Bruce > >5721cc33a0511c5964e96f439b61b97d20e500d7 ti-am335x: add CPU Freq/Idle > support >15fed008b84b8ef7ae760227d750f8840d635e43 ti-am335x: correct the arch > 64-bit to 32-bit > > > Jun Miao (2): > ti-am335x: correct the arch 64-bit to 32-bit > ti-am335x: add CPU Freq/Idle support > > bsp/ti-am335x/ti-am335x-standard.scc | 2 +- > bsp/ti-am335x/ti-am335x.cfg | 21 + > 2 files changed, 22 insertions(+), 1 deletion(-) > > -- > 2.22.0 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] : [kernel-cache master/yocto-5.2]: bcm-2xxx-rpi: add configure file for bcm-2xxx-rpi BSP in kernel-cache
In message: [linux-yocto]: [kernel-cache master/yocto-5.2]: bcm-2xxx-rpi: add configure file for bcm-2xxx-rpi BSP in kernel-cache on 16/09/2019 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > I am working on BSP bcm-2xxx-rpi platform, and intend to merge this BSP > supporting into yocto community. > Below patch includes scc and cfg files for Raspberrypi 4b platform. > > Could you please merge this patch into yocto-kernel-cache, branch is master > and yocto-5.2? The baseline configuration looks sane to me (I checked for obvious errors and non hardware configs). So I've gone ahead and merged this to the 5.2 and master branches. Bruce > > 0001-bcm-2xxx-rpi-add-configure-file-for-bcm-2xxx-rpi-BSP.patch > > bcm-2xxx-rpi.cfg | 268 > +++ > bcm-2xxx-rpi.scc | 13 ++ > bcm-2xxx-rpi4-preempt-rt.scc |8 + > bcm-2xxx-rpi4-standard.scc |9 + > 4 files changed, 298 insertions(+) > > > thanks, > Limeng -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] v4.18.x - stable updates comprising v4.18.43
On Thu, Sep 12, 2019 at 5:06 PM Paul Gortmaker wrote: > > Bruce, Yocto kernel folks: > > Here is the next 4.18.x stable update "extension" primarily created > for the Yocto project, continuing from the previous v4.18.42 release. > > There are about 125 commits here, based on the commits that were used > in the 4.19.[48/49/50] linux-stable releases. > > A note to distro builders - normally there are no new Kconfig options > in stable, but here there is a new "NOUVEAU_LEGACY_CTX_SUPPORT" option. > The upstream decided that the easiest solution to avoid potential > security issues with the legacy code was to provide a way for distro > builders to opt out. But it remains enabled by default so as to not > break any exising users who rely on it. > > I suspect I'll have time to do one more final 4.18 stable backport > release. Hopefully with the EOL messaging being in the last few > releases, this is no surprise to anyone, and people have their own > maintenance or migration plans in place and rolled out. Thanks Paul, We'll see if anyone else reads this part of the release message :D This is now merged. Bruce > > I've put this 4.18.x 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 v4.18.43 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-4.18.y.git/?h=linux-4.18.y > git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git > > for merge to standard/base in linux-yocto-4.18 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-4.18.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 4.18.x release. > > Paul. -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache][yocto-5.2] Add NUMA node number and enable NUMA balancing
On Fri, Sep 6, 2019 at 3:12 AM Yongxin Liu wrote: > > Hi Bruce, > > The follow two patches were merged to master branch of yocto-kernel-cache. > > 07aeebc4cefbfa4f56a640917355ada547586b60 bsp/intel-x86: Enable NUMA balancing > for intel-x86-64 > 09126d352f7092f8bfe0f79128d7d1aa3b262c53 bsp/intel-x86: Set > CONFIG_NODES_SHIFT to 6 > > Please help to merge them to yocto-5.2 branch. These are now merged. I'll send SRCREV updates along with the 5.2 -stable updates I have pending. Bruce > > > Thanks, > Yongxin -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache yocto-5.2] nxp-ls20xx: add kernel-cache configuration files for BSP nxp-ls20xx
merged. Bruce In message: [linux-yocto] [kernel-cache yocto-5.2] nxp-ls20xx: add kernel-cache configuration files for BSP nxp-ls20xx on 04/09/2019 Xulin Sun wrote: > This adds the cfg & scc files to support the LS2088A-RDB. > > Signed-off-by: Xulin Sun > --- > bsp/nxp-ls20xx/nxp-ls20xx-standard.scc | 8 ++ > bsp/nxp-ls20xx/nxp-ls20xx.cfg | 162 + > bsp/nxp-ls20xx/nxp-ls20xx.scc | 7 ++ > 3 files changed, 177 insertions(+) > create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.cfg > create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.scc > > diff --git a/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > new file mode 100755 > index ..e0d9b2b7 > --- /dev/null > +++ b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > @@ -0,0 +1,8 @@ > +define KMACHINE nxp-ls20xx > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard/standard.scc > +branch nxp-ls20xx > + > +include nxp-ls20xx.scc > diff --git a/bsp/nxp-ls20xx/nxp-ls20xx.cfg b/bsp/nxp-ls20xx/nxp-ls20xx.cfg > new file mode 100755 > index ..f554c916 > --- /dev/null > +++ b/bsp/nxp-ls20xx/nxp-ls20xx.cfg > @@ -0,0 +1,162 @@ > +.. > +.WARNING > +. > +. This file is a kernel configuration fragment, and not a full kernel > +. configuration file. The final kernel configuration is made up of > +. an assembly of processed fragments, each of which is designed to > +. capture a specific part of the final configuration (e.g. platform > +. configuration, feature configuration, and board specific hardware > +. configuration). For more information on kernel configuration, please > +. consult the product documentation. > +. > +.. > + > +CONFIG_ARM64=y > +CONFIG_ARM64_VA_BITS_48=y > +CONFIG_ARCH_LAYERSCAPE=y > +CONFIG_SCHED_MC=y > +CONFIG_ARM_SMMU=y > +CONFIG_ARM_SMMU_V3=y > + > +CONFIG_PCI=y > +CONFIG_PCI_LAYERSCAPE=y > +CONFIG_PCI_HOST_GENERIC=y > +CONFIG_PCI_XGENE=y > +CONFIG_PCI_MSI=y > + > +CONFIG_CPU_FREQ=y > +CONFIG_CPU_FREQ_STAT=y > +CONFIG_CPU_FREQ_GOV_POWERSAVE=y > +CONFIG_CPU_FREQ_GOV_USERSPACE=y > +CONFIG_CPU_FREQ_GOV_ONDEMAND=y > +CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y > +CONFIG_CPUFREQ_DT=y > +CONFIG_QORIQ_CPUFREQ=y > + > +CONFIG_MTD=y > +CONFIG_MTD_CMDLINE_PARTS=y > +CONFIG_MTD_BLOCK=y > +CONFIG_MTD_CFI=y > +CONFIG_MTD_CFI_ADV_OPTIONS=y > +CONFIG_MTD_CFI_INTELEXT=y > +CONFIG_MTD_CFI_AMDSTD=y > +CONFIG_MTD_CFI_STAA=y > +CONFIG_MTD_DATAFLASH=y > +CONFIG_MTD_M25P80=y > +CONFIG_MTD_SST25L=y > +CONFIG_MTD_SPI_NOR=y > +CONFIG_MTD_RAW_NAND=y > +CONFIG_MTD_NAND_FSL_IFC=y > +CONFIG_SPI_FSL_QUADSPI=y > +CONFIG_SCSI_SAS_ATA=y > +CONFIG_SCSI_HISI_SAS=y > +CONFIG_ATA=y > +CONFIG_SATA_AHCI=y > +CONFIG_SATA_AHCI_PLATFORM=y > +CONFIG_AHCI_CEVA=y > +CONFIG_AHCI_XGENE=y > +CONFIG_AHCI_QORIQ=y > +CONFIG_SATA_SIL24=y > + > +CONFIG_FSL_XGMAC_MDIO=y > +CONFIG_HNS_DSAF=y > +CONFIG_HNS_ENET=y > +CONFIG_E1000=y > +CONFIG_E1000E=y > + > +CONFIG_SERIAL_8250=y > +CONFIG_SERIAL_8250_CONSOLE=y > +CONFIG_SERIAL_8250_DW=y > +CONFIG_SERIAL_OF_PLATFORM=y > +CONFIG_SERIAL_FSL_LPUART=y > +CONFIG_SERIAL_FSL_LPUART_CONSOLE=y > + > +CONFIG_SPI=y > +CONFIG_SPI_FSL_DSPI=y > +CONFIG_SPI_PL022=y > +CONFIG_SPI_NXP_FLEXSPI=y > + > +CONFIG_POWER_RESET_XGENE=y > +CONFIG_POWER_RESET_SYSCON=y > +CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y > + > +CONFIG_THERMAL=y > +CONFIG_THERMAL_OF=y > +CONFIG_CPU_THERMAL=y > +CONFIG_THERMAL_EMULATION=y > +CONFIG_WATCHDOG=y > +CONFIG_ARM_SP805_WATCHDOG=y > + > +CONFIG_USB=y > +CONFIG_USB_OTG=y > +CONFIG_USB_XHCI_HCD=y > +CONFIG_USB_STORAGE=y > +CONFIG_USB_DWC3=y > +CONFIG_USB_DWC2=y > +CONFIG_USB_GADGET=y > + > +CONFIG_MMC=y > +CONFIG_MMC_ARMMMCI=y > +CONFIG_MMC_SDHCI=y > +CONFIG_MMC_SDHCI_PLTFM=y > +CONFIG_MMC_SDHCI_OF_ARASAN=y > +CONFIG_MMC_SDHCI_OF_ESDHC=y > +CONFIG_MMC_SDHCI_CADENCE=y > +CONFIG_MMC_SPI=y > +CONFIG_MMC_DW=y > + > +CONFIG_GPIOLIB=y > +CONFIG_OF_GPIO=y > + > +CONFIG_MDIO_DEVICE=y > +CONFIG_MDIO_BITBANG=y > +CONFIG_PHYLIB=y > +CONFIG_AQUANTIA_PHY=y > +CONFIG_CORTINA_PHY=y > + > +# > +# I2C support > +# > +CONFIG_I2C=y > +CONFIG_I2C_MUX=y > +CONFIG_I2C_IMX=y > +CONFIG_I2C_MUX_PCA954x=y > + > +CONFIG_RTC_CLASS=y > +CONFIG_RTC_DRV_DS3232=y > +CONFIG_RTC_DRV_PL031=y > +CONFIG_RTC_DRV_PCF2127=y > + > +CONFIG_DMADEVICES=y > +CONFIG_FSL_EDMA=y > +CONFIG_CMA=y > +CONFIG_DMA_CMA=y > + > +CONFIG_VFIO=y > +CONFIG_VFIO_PCI=y > + > +CONFIG_STAGING=y > +CONFIG_FSL_MC_BUS=y > +CONFIG_FSL_MC_DPIO=y > + > +CONFIG_CLK_QORIQ=y > + > +CONFIG_PHY_XGENE=y > + > +CONFIG_CRYPTO_DEV_FSL_CAAM=y > +CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=y > +CONFIG_ARM64_CRYPTO=y > +CONFIG_CRYPTO_SHA1_ARM64_CE=y > +CONFIG_CRYPTO_SHA2_ARM64_CE=y > +CONFIG_CRYPTO_GHASH_ARM64_CE=y > +CONFIG_CRYPTO_AES_ARM64_CE_CCM=y > +CONFIG_CRYPTO_AES_ARM64_CE_BLK=y > +#
Re: [linux-yocto] [kernel-cache v5.2] ti-am335x: add base support
In message: [linux-yocto][kernel-cache v5.2] ti-am335x: add base support on 04/09/2019 Jun Miao wrote: > Hi Bruce, > > I am working ti boards(AM335x evm/sk/BBB) with am335x soc. > > Could you help me add scc/cfg to yocto-kernel-cache v5.2 branch. Looks good to me. This is now merged. Bruce > > > Jun Miao (1): > ti-am335x: add the basic scc/cfg enablement > > bsp/ti-am335x/ti-am335x-standard.scc | 7 + > bsp/ti-am335x/ti-am335x.cfg | 230 +++ > bsp/ti-am335x/ti-am335x.scc | 7 + > 3 files changed, 244 insertions(+) > create mode 100644 bsp/ti-am335x/ti-am335x-standard.scc > create mode 100644 bsp/ti-am335x/ti-am335x.cfg > create mode 100644 bsp/ti-am335x/ti-am335x.scc > > -- > 2.22.0 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache yocto-5.2][PATCH 0/1] xilinx-zynq: add kernel-cache support for zc702 and zc706 boards
In message: [linux-yocto][kernel-cache yocto-5.2][PATCH 0/1] xilinx-zynq: add kernel-cache support for zc702 and zc706 boards on 05/09/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > > The patch as below includes scc and cfg files for xilinx zc702/zc706 boards. > > Could you please merge this patch into yocto-kernel-cache, branch is > yocto-5.2? merged. Bruce > > Quanyang Wang (1): > xilinx-zynq: add the support for xlinx-zynq bsp > > bsp/xilinx-zynq/xilinx-zynq-standard.scc | 7 + > bsp/xilinx-zynq/xilinx-zynq.cfg | 199 +++ > bsp/xilinx-zynq/xilinx-zynq.scc | 8 + > 3 files changed, 214 insertions(+) > create mode 100644 bsp/xilinx-zynq/xilinx-zynq-standard.scc > create mode 100644 bsp/xilinx-zynq/xilinx-zynq.cfg > create mode 100644 bsp/xilinx-zynq/xilinx-zynq.scc > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] spp: optimize strip_common_prefix function
I have this queued for testing now.
Bruce
On Fri, Aug 30, 2019 at 1:09 AM Zhaolong Zhang wrote:
>
> strip_common_prefix() is the hot path that executes on every input file.
> This patch sorts and uniqs the $include_paths by length descreasingly.
> And with the sorted $include_paths, the for-loop inside strip_common_prefix
> can break earlier, thus kernel_metadata task can be sped up by multiple times.
>
> Signed-off-by: Zhaolong Zhang
> ---
> tools/spp | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/tools/spp b/tools/spp
> index 1150ff3..cba52bb 100755
> --- a/tools/spp
> +++ b/tools/spp
> @@ -125,6 +125,7 @@ strip_common_prefix()
> if [ $this_len -lt $out_len ]; then
> relocated_name=$t
> out_len=$this_len
> + break
> fi
> # add a trailing slash to get corner cases where one may
> # have been added or not dropped
> @@ -133,6 +134,7 @@ strip_common_prefix()
> if [ $this_len -lt $out_len ]; then
> relocated_name=$t
> out_len=$this_len
> + break
> fi
> done
>
> @@ -297,6 +299,16 @@ infiles=$@
>
> processed_files=""
>
> +# this function also removes duplicated lines by `sort -u`
> +sort_by_len_dec()
> +{
> +for i in $@; do
> +echo $i
> +done | sort -u | awk '{ print length($0) " " $0; }' | sort -nr | cut
> -d ' ' -f 2-
> +}
> +
> +include_paths=$(sort_by_len_dec $include_paths)
> +
> ##
> ## create variables for use in scripts
> ##
> --
> 1.9.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
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] [for all x86 branches] x86/boot: Save fields explicitly, zero out everything else
Since this is destined for -stable, I'm not going to merge the individual patch.
I'm holding nearly all 5.2 updates until the last introduction issues
are fixed. By that time, I'll have the next round of -stable updates
ready to go as well.
Cheers,
Bruce
On Thu, Sep 5, 2019 at 6:02 AM wrote:
>
> From: John Hubbard
>
> commit a90118c445cc7f07781de26a9684d4ec58bfcfd1 upstream.
>
> Recent gcc compilers (gcc 9.1) generate warnings about an out of bounds
> memset, if the memset goes accross several fields of a struct. This
> generated a couple of warnings on x86_64 builds in sanitize_boot_params().
>
> Fix this by explicitly saving the fields in struct boot_params
> that are intended to be preserved, and zeroing all the rest.
>
> [ tglx: Tagged for stable as it breaks the warning free build there as well ]
>
> Suggested-by: Thomas Gleixner
> Suggested-by: H. Peter Anvin
> Signed-off-by: John Hubbard
> Signed-off-by: Thomas Gleixner
> Cc: sta...@vger.kernel.org
> Link: https://lkml.kernel.org/r/20190731054627.5627-2-jhubb...@nvidia.com
> Signed-off-by: Greg Kroah-Hartman
> ---
> Fix the following build warning. It has been merge to 5.2.11.
> Please consider merging if it's worth.
>
> ./arch/x86/include/asm/bootparam_utils.h:40:3: warning: ‘memset’ offset [197,
> 448] from the object at ‘boot_params’ is out of the bounds of referenced
> subobject ‘ext_ramdisk_image’ with type
> ‘unsigned int’ at offset 192 [-Warray-bounds]
>
> ./arch/x86/include/asm/bootparam_utils.h:43:3: warning: ‘memset’ offset [493,
> 497] from the object at ‘boot_params’ is out of the bounds of referenced
> subobject ‘kbd_status’ with type ‘unsig
> ned char’ at offset 491 [-Warray-bounds]
>
> arch/x86/include/asm/bootparam_utils.h | 63
> ++
> 1 file changed, 48 insertions(+), 15 deletions(-)
>
> diff --git a/arch/x86/include/asm/bootparam_utils.h
> b/arch/x86/include/asm/bootparam_utils.h
> index f6f6ef4..7fed0fc 100644
> --- a/arch/x86/include/asm/bootparam_utils.h
> +++ b/arch/x86/include/asm/bootparam_utils.h
> @@ -18,6 +18,20 @@
> * Note: efi_info is commonly left uninitialized, but that field has a
> * private magic, so it is better to leave it unchanged.
> */
> +
> +#define sizeof_mbr(type, member) ({ sizeof(((type *)0)->member); })
> +
> +#define BOOT_PARAM_PRESERVE(struct_member) \
> + { \
> + .start = offsetof(struct boot_params, struct_member), \
> + .len = sizeof_mbr(struct boot_params, struct_member), \
> + }
> +
> +struct boot_params_to_save {
> + unsigned int start;
> + unsigned int len;
> +};
> +
> static void sanitize_boot_params(struct boot_params *boot_params)
> {
> /*
> @@ -35,21 +49,40 @@ static void sanitize_boot_params(struct boot_params
> *boot_params)
> * problems again.
> */
> if (boot_params->sentinel) {
> - /* fields in boot_params are left uninitialized, clear them */
> - boot_params->acpi_rsdp_addr = 0;
> - memset(_params->ext_ramdisk_image, 0,
> - (char *)_params->efi_info -
> - (char *)_params->ext_ramdisk_image);
> - memset(_params->kbd_status, 0,
> - (char *)_params->hdr -
> - (char *)_params->kbd_status);
> - memset(_params->_pad7[0], 0,
> - (char *)_params->edd_mbr_sig_buffer[0] -
> - (char *)_params->_pad7[0]);
> - memset(_params->_pad8[0], 0,
> - (char *)_params->eddbuf[0] -
> - (char *)_params->_pad8[0]);
> - memset(_params->_pad9[0], 0, sizeof(boot_params->_pad9));
> + static struct boot_params scratch;
> + char *bp_base = (char *)boot_params;
> + char *save_base = (char *)
> + int i;
> +
> + const struct boot_params_to_save to_save[] = {
> + BOOT_PARAM_PRESERVE(screen_info),
> + BOOT_PARAM_PRESERVE(apm_bios_info),
> + BOOT_PARAM_PRESERVE(tboot_addr),
> + BOOT_PARAM_PRESERVE(ist_info),
> + BOOT_PARAM_PRESERVE(acpi_rsdp_addr),
> + BOOT_PARAM_PRESERVE(hd0_info),
> + BOOT_PARAM_PRESERVE(hd1_info),
> + BOOT_PARAM_PRESERVE(sys_desc_table),
> + BOOT_PARAM_PRESERVE(olpc_ofw_header),
> + BOOT_PARAM_PRESERVE(efi_info),
> + BOOT_PARAM_PRESERVE(alt_mem_k),
> + BOOT_PARAM_PRESERVE(scratch),
> + BOOT_PARAM_PRESERVE(e820_entries),
> + BOOT_PARAM_PRESERVE(eddbuf_entries),
> + BOOT_PARAM_PRESERVE(edd_mbr_sig_buf_entries),
> +
Re: [linux-yocto] [kernel-cache master/yocto-5.0][PATCH] intel-x86: add MGA G200 series VGA support
Indeed. I appear to have messed it up .. I had a lot of merges to do today, so I was sure to get something wrong. This is now really merged. Bruce On Tue, Sep 3, 2019 at 9:57 PM Liwei Song wrote: > > Hi Bruce, > > It seems that this patch was missed by master branch, so does 5.2 branch also > miss it. > Could you help merge it to both master and yocto-5.2 branch? > > > Thanks, > Liwei. > > > On 07/08/2019 04:22 PM, Liwei Song wrote: > > Enable CONFIG_DRM_MGAG200=m to support Matrox Electronics MGA G200 > > and include it in intel-x86 bsp. > > > > Signed-off-by: Liwei Song > > --- > > bsp/intel-x86/intel-x86.scc | 1 + > > features/mgag200/mgag200.cfg | 1 + > > features/mgag200/mgag200.scc | 4 > > 3 files changed, 6 insertions(+) > > create mode 100644 features/mgag200/mgag200.cfg > > create mode 100644 features/mgag200/mgag200.scc > > > > diff --git a/bsp/intel-x86/intel-x86.scc b/bsp/intel-x86/intel-x86.scc > > index aee6d5e93db3..a93319d483a5 100644 > > --- a/bsp/intel-x86/intel-x86.scc > > +++ b/bsp/intel-x86/intel-x86.scc > > @@ -39,6 +39,7 @@ include features/tpm/tpm.scc > > include features/mfd/mfd-intel-lpss.scc > > include features/mmc/mmc-realtek.scc > > include features/intel-pinctrl/intel-pinctrl.scc > > +include features/mgag200/mgag200.scc > > > > kconf hardware intel-x86.cfg > > kconf hardware intel-x86-mga.cfg > > diff --git a/features/mgag200/mgag200.cfg b/features/mgag200/mgag200.cfg > > new file mode 100644 > > index ..48b6c6106fe0 > > --- /dev/null > > +++ b/features/mgag200/mgag200.cfg > > @@ -0,0 +1 @@ > > +CONFIG_DRM_MGAG200=m > > diff --git a/features/mgag200/mgag200.scc b/features/mgag200/mgag200.scc > > new file mode 100644 > > index ..6bb0e79608e9 > > --- /dev/null > > +++ b/features/mgag200/mgag200.scc > > @@ -0,0 +1,4 @@ > > +define KFEATURE_DESCRIPTION "Matrox Electronics Systems Ltd. MGA G200e > > support" > > +define KFEATURE_COMPATIBILITY board > > + > > +kconf hardware mgag200.cfg > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/2 linux-yocto-dev all branches] aufs: bugfix, opts: Fix missing break statement
merged to linux-yocto-dev Bruce On Tue, Sep 3, 2019 at 3:28 AM wrote: > > From: He Zhe > > commit 4a80018d718f6be2e862d0c70bb11cd6e6d1fae5 upstream > > Add missing break statement for case Opt_wsum in au_opt_simple. > > Signed-off-by: He Zhe > See-also: > https://www.mail-archive.com/aufs-users@lists.sourceforge.net/msg05684.html > (cherry picked from commit 9e7d29356ab57fa5db7e92e51267176e50c1497c) > --- > fs/aufs/opts.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/fs/aufs/opts.c b/fs/aufs/opts.c > index a089b8e..d370108 100644 > --- a/fs/aufs/opts.c > +++ b/fs/aufs/opts.c > @@ -1373,6 +1373,7 @@ static int au_opt_simple(struct super_block *sb, struct > au_opt *opt, > case Opt_wsum: > au_opt_clr(sbinfo->si_mntflags, SUM); > au_opt_set(sbinfo->si_mntflags, SUM_W); > + break; > case Opt_nosum: > au_opt_clr(sbinfo->si_mntflags, SUM); > au_opt_clr(sbinfo->si_mntflags, SUM_W); > -- > 2.7.4 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 2/2 linux-yocto-dev all branches] aufs: opts: Fix missing fallthrough
merged to linux-yocto-dev.
Bruce
On Tue, Sep 3, 2019 at 3:28 AM wrote:
>
> From: He Zhe
>
> commit 8d7b6374d5af2c31ce9501d3502808e3c7a9ea68 upstream
>
> A compilation -Wimplicit-fallthrough warning was enabled by commit
> a035d552a93b ("Makefile: Globally enable fall-through warning")
> and triggers the following warning.
>
> fs/aufs/opts.h:78:11:
> warning: this statement may fall through [-Wimplicit-fallthrough=]
>
> This patch adds comments according GNU manual.
> https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#Warning-Options
>
> Signed-off-by: He Zhe
> See-also:
> https://www.mail-archive.com/aufs-users@lists.sourceforge.net/msg05685.html
> (cherry picked from commit e7619996b014c5d8fd2f6ad89542c545a207667f)
> ---
> fs/aufs/opts.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/aufs/opts.c b/fs/aufs/opts.c
> index d370108..01fae8b 100644
> --- a/fs/aufs/opts.c
> +++ b/fs/aufs/opts.c
> @@ -1499,8 +1499,10 @@ static int au_opt_br(struct super_block *sb, struct
> au_opt *opt,
> if (opt->add.bindex < 0)
> opt->add.bindex = 0;
> goto add;
> + /* Always goto add, not fallthrough */
> case Opt_prepend:
> opt->add.bindex = 0;
> + /* fallthrough */
> add: /* indented label */
> case Opt_add:
> err = au_br_add(sb, >add,
> --
> 2.7.4
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache] [all branches] [PATCH] net_sched: Add FQ Controlled Delay packet scheduling algorithm
merged to 4.19/5.0/5.2 and master of the kernel-cache. SRCREV bumps will follow in the next few days. Bruce On Tue, Sep 3, 2019 at 3:00 AM wrote: > > From: He Zhe > > It has been widely used and selected by systemd as defalut scheduling > algorithm > since v217. > https://github.com/systemd/systemd/blob/master/NEWS#L5861 > > Signed-off-by: He Zhe > --- > features/net_sched/net_sched.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/features/net_sched/net_sched.cfg > b/features/net_sched/net_sched.cfg > index 49cd7d7..8ac740a 100644 > --- a/features/net_sched/net_sched.cfg > +++ b/features/net_sched/net_sched.cfg > @@ -19,6 +19,7 @@ CONFIG_NET_SCH_DSMARK=m > CONFIG_NET_SCH_NETEM=m > CONFIG_NET_SCH_INGRESS=m > CONFIG_NET_SCH_CODEL=m > +CONFIG_NET_SCH_FQ_CODEL=m > > # > # Classification > -- > 2.7.4 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-v5.2]: [kernel standard/base]: renesas-rcar: add some patches to improve features on renesas-rcar platform
These look fine to me. All four patches are on v5.2/standard/base Bruce On Tue, Sep 3, 2019 at 2:53 AM wrote: > > From: Limeng > > Hi Bruce, > > I am working on BSP renesas-rcar platform, and intend to merge this BSP > supporting into yocto community. > Below 4 patches are used to improve gpio, CAN BUS, audio and PCIe features > This first patch is from mainline upstream, the other 3 patches merged into > linux-yocto-dev(standard/base) some days ago. > > 0001-arm64-dts-renesas-ulcb-kf-Add-support-for-TI-WL1837.patch > 0002-arch-arm64-dts-Set-gpio5-pin9-as-input-by-default.patch > 0003-driver-net-can-disable-clock-when-it-is-in-enable-st.patch > 0004-pci-pcie-rcar-add-regulators-support.patch > > Could you please merge the 4 patches into linux-yocto, branch is > v5.2/standard/base? > > arch/arm64/boot/dts/renesas/ulcb-kf.dtsi | 105 > +++ > drivers/net/can/rcar/rcar_can.c |5 + > drivers/pci/controller/pcie-rcar.c | 64 ++ > 3 files changed, 173 insertions(+), 1 deletion(-) > > > thanks, > Limeng -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] : [kernel-cache yocto-5.2]: renesas-rcar: add configure file for renesas BSP in kernel-cache
This is now in the 5.2 branch of the kernel-cache. Bruce On Fri, Aug 30, 2019 at 5:19 AM wrote: > > From: Limeng > > Hi Bruce, > > I am working on BSP renesas-rcar platform, and intend to merge this BSP > supporting into yocto community. > Below patch includes scc and cfg files for renesas-rcar platform. > > Could you please merge this patch into yocto-kernel-cache, branch is > yocto-5.2? > This patch was merged into master some days ago. It also need to be merged > into yocto-5.2 branch > > 0001-renesas-rcar-add-configure-file-for-renesas-BSP-in-k.patch > > renesas-rcar-h3-standard.scc |7 + > renesas-rcar-m3-standard.scc |7 + > renesas-rcar.cfg | 252 > +++ > renesas-rcar.scc |8 + > 4 files changed, 274 insertions(+) > > > thanks, > Limeng -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-meta] bsp: Add the support for the marvell-cn96xx BSP
On Tue, Sep 3, 2019 at 3:40 AM Kevin Hao wrote: > > This adds the cfg files to support the Marvell OCTEON TX2 > CN96XX multicore arm64 SoC. merged to yocto-5.2 of the kernel-cache. Bruce > > Signed-off-by: Kevin Hao > --- > bsp/marvell-cn96xx/marvell-cn96xx-standard.scc | 7 ++ > bsp/marvell-cn96xx/marvell-cn96xx.cfg | 107 > + > bsp/marvell-cn96xx/marvell-cn96xx.scc | 6 ++ > 3 files changed, 120 insertions(+) > create mode 100644 bsp/marvell-cn96xx/marvell-cn96xx-standard.scc > create mode 100644 bsp/marvell-cn96xx/marvell-cn96xx.cfg > create mode 100644 bsp/marvell-cn96xx/marvell-cn96xx.scc > > diff --git a/bsp/marvell-cn96xx/marvell-cn96xx-standard.scc > b/bsp/marvell-cn96xx/marvell-cn96xx-standard.scc > new file mode 100644 > index ..8d92dc15f87b > --- /dev/null > +++ b/bsp/marvell-cn96xx/marvell-cn96xx-standard.scc > @@ -0,0 +1,7 @@ > +define KMACHINE marvell-cn96xx > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard > + > +include marvell-cn96xx.scc > diff --git a/bsp/marvell-cn96xx/marvell-cn96xx.cfg > b/bsp/marvell-cn96xx/marvell-cn96xx.cfg > new file mode 100644 > index ..7dc73ac245f5 > --- /dev/null > +++ b/bsp/marvell-cn96xx/marvell-cn96xx.cfg > @@ -0,0 +1,107 @@ > +.. > +.WARNING > +. > +. This file is a kernel configuration fragment, and not a full kernel > +. configuration file. The final kernel configuration is made up of > +. an assembly of processed fragments, each of which is designed to > +. capture a specific part of the final configuration (e.g. platform > +. configuration, feature configuration, and board specific hardware > +. configuration). For more information on kernel configuration, please > +. consult the product documentation. > +. > +.. > + > +CONFIG_ARM64=y > +CONFIG_ARM64_VA_BITS_48=y > +CONFIG_ARM_SMMU_V3=y > +CONFIG_NR_CPUS=24 > +CONFIG_ARCH_THUNDER=y > + > +# uboot set "coherent_pool=16M" kernel parameter by default, so we need to > +# make sure CONFIG_FORCE_MAX_ZONEORDER is big enough > +CONFIG_ARM64_64K_PAGES=y > +CONFIG_TRANSPARENT_HUGEPAGE=y > + > +# PCIe > +CONFIG_PCI=y > +CONFIG_PCIEPORTBUS=y > +CONFIG_HOTPLUG_PCI=y > +CONFIG_HOTPLUG_PCI_PCIE=y > +CONFIG_PCI_IOV=y > + > +CONFIG_PCI_HOST_GENERIC=y > +CONFIG_PCI_HOST_THUNDER_PEM=y > +CONFIG_PCI_HOST_OCTEONTX2_PEM=y > + > +# Ethernet > +CONFIG_OCTEONTX2_AF=y > +CONFIG_OCTEONTX2_PF=y > +CONFIG_OCTEONTX2_VF=y > +CONFIG_USB_USBNET=y > +CONFIG_USB_NET_AX88179_178A=y > + > +# NVMe > +CONFIG_BLK_DEV_NVME=y > + > +# DMA > +CONFIG_OCTEONTX2_DPI_PF=y > + > +# MTD > +CONFIG_MTD=y > +CONFIG_MTD_SPI_NOR=y > +CONFIG_MTD_M25P80=y > +CONFIG_MTD_BLOCK=y > + > +# USB > +CONFIG_USB=y > +CONFIG_USB_XHCI_HCD=y > + > +# SPI > +CONFIG_SPI=y > +CONFIG_SPI_OCTEONTX2=y > + > +# I2C > +CONFIG_I2C=y > +CONFIG_I2C_THUNDERX=y > + > +# Serial > +CONFIG_SERIAL_AMBA_PL011=y > +CONFIG_SERIAL_AMBA_PL011_CONSOLE=y > + > +# Watchdog > +CONFIG_ARM_SBSA_WATCHDOG=y > + > +# SD > +CONFIG_MMC=y > +CONFIG_MMC_CAVIUM_THUNDERX=y > + > +# GPIO > +CONFIG_GPIOLIB=y > +CONFIG_GPIO_THUNDERX=y > + > +# HWMON > +CONFIG_SENSORS_MAX6697=y > +CONFIG_SENSORS_JC42=y > + > +# RTC > +CONFIG_RTC_CLASS=y > +CONFIG_RTC_DRV_DS1307=y > + > +# Regulator > +CONFIG_REGULATOR=y > +CONFIG_REGULATOR_FIXED_VOLTAGE=y > +CONFIG_REGULATOR_GPIO=y > + > +# VFIO > +CONFIG_VFIO=y > +CONFIG_VFIO_PCI=y > + > +# Misc > +CONFIG_EEPROM_AT24=y > +CONFIG_HW_RANDOM=y > +CONFIG_HW_RANDOM_CAVIUM=y > +CONFIG_OCTEONTX2_RM=y > +CONFIG_OCTEONTX2_RM_DOM_SYSFS=y > + > +# BPHY > +CONFIG_MARVELL_OTX_BPHY_CTR=y > diff --git a/bsp/marvell-cn96xx/marvell-cn96xx.scc > b/bsp/marvell-cn96xx/marvell-cn96xx.scc > new file mode 100644 > index ..0d104fad583b > --- /dev/null > +++ b/bsp/marvell-cn96xx/marvell-cn96xx.scc > @@ -0,0 +1,6 @@ > +kconf hardware marvell-cn96xx.cfg > +kconf hardware features/edac/edac.cfg > + > +include cfg/usb-mass-storage.scc > + > +include features/hugetlb/hugetlb.scc > -- > 2.14.4 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel] The kernel patches for the Marvell cn96xx support
On Tue, Sep 3, 2019 at 3:40 AM Kevin Hao wrote:
>
> The following changes since commit 35276d20c01a78ee3640a074446b0c15c486c5d0:
>
> selftests/bpf: structure test_{progs, maps, verifier} test runners
> uniformly (2019-08-30 00:33:44 -0400)
>
> are available in the Git repository at:
>
> https://github.com/haokexin/linux.git v5.2/standard/cn96xx
v5.2/standard/cn96xx has been created in linux-yocto.git
Bruce
>
> for you to fetch changes up to a075be8d6f3bacea9a7ccc36f80bac2e3276c5e2:
>
> octeontx2-af: Fix the using of variable length arrays (2019-09-03 14:40:25
> +0800)
>
>
> Aleksey Makarov (6):
> octeontx2-pf: Set irq affinity hints for CQ interrupts
> octeontx2-pf: Implement ndo_tx_timeout callback
> octeontx2-pf: Support queue interrupts
> octeontx2-pf: Add reset count to stats
> octeontx2-af: Add low level support for Marvell PTP coprocessor
> octeontx2-pf: Add support for PTP clock
>
> Alex Belits (2):
> arm64: Add support for ASID locking
> kernel/exit.c: Add task cleanup callbacks
>
> Angela Czubak (2):
> octeontx2-af: fix rvu_sso_ggrp_taq_flush
> octeontx2-af: fix cgx_lmac_rx_tx_enable
>
> Chandrakala Chavva (1):
> mmc: cavium_thunderx: Use proper register to clear interrupts
>
> Christina Jacob (22):
> octeontx2-pf: BQL support.
> octeontx2-pf: IRQ coalescing config and tuning via ethtool
> octeontx2-af: Dump current resource provisioning status
> octeontx2-pf: Adding ethtool support for link status information.
> octeontx2-af: Patch to prevent redundant message from pf to af.
> octeontx2-pf: Fix redundant message from AF to PF
> octeontx2-af: Support to get link info like current speed, fec etc
> octeontx2-pf: Ethtool support for fec configuration
> octeontx2-pf: Fix smmuv3 messages while deferring pf driver probe.
> octeontx2-af: Move to rvu_fwdata version 1.
> octeontx2-pf: Add ethtool -m option support.
> octeontx2-af: Extend fwdata structure with additional information.
> octeontx2-af: Update fwadata structure with few more reserved fields.
> octeontx2-af: Fetch FEC stats of the physical link
> octeontx2-pf: Support to display fec counters also in ethtool stats.
> octeontx2-af: sync ATF and Kernel firmware data structure.
> octeontx2-pf: Support to display current settings of a vf network
> interface via ethtool
> net:thunderx: fix memory leak in nicvf driver.
> soc: octeontx2: Add mdio command interface using debugfs
> soc: octeontx2: Add mdio command interface using debugfs
> octeontx2-af: Introduce SET_LINK_MODE command to change various
> configurations of a network interface.
> octeontx2-pf: support to change link speed and autoneg
>
> Felix Manlunas (2):
> octeontx2-af: Add new CGX_CMDs to set and get PHY modulation type
> octeontx2-pf: Add ethtool priv flag to control PAM4 on/off
>
> Geetha sowjanya (26):
> octeontx2-af: Sync hw mbox with bounce buffer.
> octeontx2-pf: Add mailbox bounce buffer
> octeontx2-pf: Add interface stats to ndo_get_stats64
> octeontx2-af: Config receive and transmission of pause frames
> octeontx2-af: Add mbox message to enable/disable pause frames.
> octeontx2-af: Add mbox messages to configure backpressure for an
> interface.
> octeontx2-pf: Add ethtool support to enable/disable pause frames
> octeontx2-pf: Configure RED drop levels for packet reception.
> octeontx2-pf: Configure backpressure level for packet reception
> octeontx2-pf: Skip CQ_STATUS read if pending CQEs greater than budget
> octeontx2-pf: Set RVU PF/VF watchdog timeout
> octeontx2-af: Check SQ counters to detect the deadlock
> octeontx2-af: Enable pci bus mastering
> octeontx2-af: Fix rvu probe on cgx disable
> octeontx2-pf: Add VF function level reset (FLR) support
> octeontx2-vf: Configure backpressure level for packet reception
> octeontx2-af: Support configurable NDC cache way_mask
> octeontx2: Fix mbox driver compilation dependency.
> octeontx2-pf: Set minimum MTU size to 64 bytes
> octeontx2-pf: Schedule work to refill RQ if buffer alloc fails in
> atomic context.
> octeontx2-pf: Free HW resources on PF/VF initialization failure
> octeontx2-af: Update hardware workarounds for 95xx A1 silicon
> octeontx2-pf: Update hardware workarounds for 95xx A1 silicon
> PCI: quirks : Apply ACS quirk for all devices
> octeontx2-pf: Enable CQ interrupt coalescing
> octeontx2-pf: Fix RQ CQ RED and DROP levels for 96xx B0
>
> Hao Zheng (10):
> octeontx2-af: change NPC KPU profile format
> octeontx2-af: NPC KPU profile update (ver 1.3.0):
> octeontx2-af: NPC KPU profile fix
> octeontx2-af: add NPC parser support for QinQ with TPID of 0x8100
>
Re: [linux-yocto] [kernel-cache master] bsp: Add the support for the marvell-cn96xx BSP
merged to master Bruce On Tue, Aug 20, 2019 at 7:32 AM Kevin Hao wrote: > > This adds the cfg files to support the Marvell OCTEON TX2 > CN96XX multicore arm64 SoC. > > Signed-off-by: Kevin Hao > --- > bsp/marvell-cn96xx/marvell-cn96xx-standard.scc | 7 ++ > bsp/marvell-cn96xx/marvell-cn96xx.cfg | 104 > + > bsp/marvell-cn96xx/marvell-cn96xx.scc | 6 ++ > 3 files changed, 117 insertions(+) > create mode 100644 bsp/marvell-cn96xx/marvell-cn96xx-standard.scc > create mode 100644 bsp/marvell-cn96xx/marvell-cn96xx.cfg > create mode 100644 bsp/marvell-cn96xx/marvell-cn96xx.scc > > diff --git a/bsp/marvell-cn96xx/marvell-cn96xx-standard.scc > b/bsp/marvell-cn96xx/marvell-cn96xx-standard.scc > new file mode 100644 > index ..8d92dc15f87b > --- /dev/null > +++ b/bsp/marvell-cn96xx/marvell-cn96xx-standard.scc > @@ -0,0 +1,7 @@ > +define KMACHINE marvell-cn96xx > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard > + > +include marvell-cn96xx.scc > diff --git a/bsp/marvell-cn96xx/marvell-cn96xx.cfg > b/bsp/marvell-cn96xx/marvell-cn96xx.cfg > new file mode 100644 > index ..6b83cd0659aa > --- /dev/null > +++ b/bsp/marvell-cn96xx/marvell-cn96xx.cfg > @@ -0,0 +1,104 @@ > +.. > +.WARNING > +. > +. This file is a kernel configuration fragment, and not a full kernel > +. configuration file. The final kernel configuration is made up of > +. an assembly of processed fragments, each of which is designed to > +. capture a specific part of the final configuration (e.g. platform > +. configuration, feature configuration, and board specific hardware > +. configuration). For more information on kernel configuration, please > +. consult the product documentation. > +. > +.. > + > +CONFIG_ARM64=y > +CONFIG_ARM64_VA_BITS_48=y > +CONFIG_ARM_SMMU_V3=y > +CONFIG_NR_CPUS=24 > +CONFIG_ARCH_THUNDER=y > + > +# uboot set "coherent_pool=16M" kernel parameter by default, so we need to > +# make sure CONFIG_FORCE_MAX_ZONEORDER is big enough > +CONFIG_ARM64_64K_PAGES=y > +CONFIG_TRANSPARENT_HUGEPAGE=y > + > +# PCIe > +CONFIG_PCI=y > +CONFIG_PCIEPORTBUS=y > +CONFIG_HOTPLUG_PCI=y > +CONFIG_HOTPLUG_PCI_PCIE=y > +CONFIG_PCI_IOV=y > + > +CONFIG_PCI_HOST_GENERIC=y > +CONFIG_PCI_HOST_THUNDER_PEM=y > +CONFIG_PCI_HOST_OCTEONTX2_PEM=y > + > +# Ethernet > +CONFIG_OCTEONTX2_AF=y > +CONFIG_OCTEONTX2_PF=y > +CONFIG_OCTEONTX2_VF=y > +CONFIG_USB_USBNET=y > +CONFIG_USB_NET_AX88179_178A=y > + > +# NVMe > +CONFIG_BLK_DEV_NVME=y > + > +# DMA > +CONFIG_OCTEONTX2_DPI_PF=y > + > +# MTD > +CONFIG_MTD=y > +CONFIG_MTD_SPI_NOR=y > +CONFIG_MTD_M25P80=y > +CONFIG_MTD_BLOCK=y > + > +# USB > +CONFIG_USB=y > +CONFIG_USB_XHCI_HCD=y > + > +# SPI > +CONFIG_SPI=y > +CONFIG_SPI_OCTEONTX2=y > + > +# I2C > +CONFIG_I2C=y > +CONFIG_I2C_THUNDERX=y > + > +# Serial > +CONFIG_SERIAL_AMBA_PL011=y > +CONFIG_SERIAL_AMBA_PL011_CONSOLE=y > + > +# Watchdog > +CONFIG_ARM_SBSA_WATCHDOG=y > + > +# SD > +CONFIG_MMC=y > +CONFIG_MMC_CAVIUM_THUNDERX=y > + > +# GPIO > +CONFIG_GPIOLIB=y > +CONFIG_GPIO_THUNDERX=y > + > +# HWMON > +CONFIG_SENSORS_MAX6697=y > +CONFIG_SENSORS_JC42=y > + > +# RTC > +CONFIG_RTC_CLASS=y > +CONFIG_RTC_DRV_DS1307=y > + > +# Regulator > +CONFIG_REGULATOR=y > +CONFIG_REGULATOR_FIXED_VOLTAGE=y > +CONFIG_REGULATOR_GPIO=y > + > +# VFIO > +CONFIG_VFIO=y > +CONFIG_VFIO_PCI=y > + > +# Misc > +CONFIG_EEPROM_AT24=y > +CONFIG_HW_RANDOM=y > +CONFIG_HW_RANDOM_CAVIUM=y > +CONFIG_OCTEONTX2_RM=y > +CONFIG_OCTEONTX2_RM_DOM_SYSFS=y > diff --git a/bsp/marvell-cn96xx/marvell-cn96xx.scc > b/bsp/marvell-cn96xx/marvell-cn96xx.scc > new file mode 100644 > index ..0d104fad583b > --- /dev/null > +++ b/bsp/marvell-cn96xx/marvell-cn96xx.scc > @@ -0,0 +1,6 @@ > +kconf hardware marvell-cn96xx.cfg > +kconf hardware features/edac/edac.cfg > + > +include cfg/usb-mass-storage.scc > + > +include features/hugetlb/hugetlb.scc > -- > 2.14.4 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-dev] Add the support for the Marvell cn96xx SoC
On Tue, Aug 20, 2019 at 7:25 AM Kevin Hao wrote: > > Hi Bruce, > > This patch series adds the support for the Marvell cn96xx SoC. The OCTEON TX2 > cn96xx SoC is a scalable architecture that integrates high performance 64-bit > Armv8.2 processors, a cache-coherent interconnect, hardware accelerators, > virtualized networking, and scalable I/O. It support the following > industry-standard I/O interfaces: > DDR4 DRAM > PCI Express 4.0 version 1.0 > SGMII > QSGMII > XAUI > XFI > CAUI > > Most of the patches are for the Marvell specific drivers. So in theory, it > should be safe to merge these patches to the standard/base branch. But I > prefer to stage them to the specific standard/cn96xx branch. The reason is > that we plan to support other Marvell SoCs, and the SDK for them may be > based on different SDK versions. They will definitely touch some common > files affect by this patch series. So it would be a nightmare for us to > support them if these patches are merged to the standard/base branch. > > The following changes since commit ce4ec6ff9589e3b1dcc4e3a0b192b02823631c3e: > > Merge tag 'v5.3-rc5' into standard/base (2019-08-18 22:40:47 -0400) > > are available in the Git repository at: > > git://github.com/haokexin/linux standard/cn96xx standard/cn96xx now exists in linux-yocto-dev. Bruce > > for you to fetch changes up to 4fae437f7ea88d2aab10cac684e11d94b12114bd: > > octeontx2-af: Fix the using of variable length arrays (2019-08-20 11:25:36 > +0800) > > > Aleksey Makarov (6): > octeontx2-pf: Set irq affinity hints for CQ interrupts > octeontx2-pf: Implement ndo_tx_timeout callback > octeontx2-pf: Support queue interrupts > octeontx2-pf: Add reset count to stats > octeontx2-af: Add low level support for Marvell PTP coprocessor > octeontx2-pf: Add support for PTP clock > > Angela Czubak (2): > octeontx2-af: fix rvu_sso_ggrp_taq_flush > octeontx2-af: fix cgx_lmac_rx_tx_enable > > Chandrakala Chavva (1): > mmc: cavium_thunderx: Use proper register to clear interrupts > > Christina Jacob (21): > octeontx2-pf: BQL support. > octeontx2-pf: IRQ coalescing config and tuning via ethtool > octeontx2-af: Dump current resource provisioning status > octeontx2-pf: Adding ethtool support for link status information. > octeontx2-af: Patch to prevent redundant message from pf to af. > octeontx2-pf: Fix redundant message from AF to PF > octeontx2-af: Support to get link info like current speed, fec etc > octeontx2-pf: Ethtool support for fec configuration > octeontx2-pf: Fix smmuv3 messages while deferring pf driver probe. > octeontx2-af: Move to rvu_fwdata version 1. > octeontx2-pf: Add ethtool -m option support. > octeontx2-af: Extend fwdata structure with additional information. > octeontx2-af: Update fwadata structure with few more reserved fields. > octeontx2-af: Fetch FEC stats of the physical link > octeontx2-pf: Support to display fec counters also in ethtool stats. > octeontx2-af: sync ATF and Kernel firmware data structure. > octeontx2-pf: Support to display current settings of a vf network > interface via ethtool > net:thunderx: fix memory leak in nicvf driver. > soc: octeontx2: Add mdio command interface using debugfs > octeontx2-af: Introduce SET_LINK_MODE command to change various > configurations of a network interface. > octeontx2-pf: support to change link speed and autoneg > > Felix Manlunas (2): > octeontx2-af: Add new CGX_CMDs to set and get PHY modulation type > octeontx2-pf: Add ethtool priv flag to control PAM4 on/off > > Geetha sowjanya (26): > octeontx2-af: Sync hw mbox with bounce buffer. > octeontx2-pf: Add mailbox bounce buffer > octeontx2-pf: Add interface stats to ndo_get_stats64 > octeontx2-af: Config receive and transmission of pause frames > octeontx2-af: Add mbox message to enable/disable pause frames. > octeontx2-af: Add mbox messages to configure backpressure for an > interface. > octeontx2-pf: Add ethtool support to enable/disable pause frames > octeontx2-pf: Configure RED drop levels for packet reception. > octeontx2-pf: Configure backpressure level for packet reception > octeontx2-pf: Skip CQ_STATUS read if pending CQEs greater than budget > octeontx2-pf: Set RVU PF/VF watchdog timeout > octeontx2-af: Check SQ counters to detect the deadlock > octeontx2-af: Enable pci bus mastering > octeontx2-af: Fix rvu probe on cgx disable > octeontx2-pf: Add VF function level reset (FLR) support > octeontx2-vf: Configure backpressure level for packet reception > octeontx2-af: Support configurable NDC cache way_mask > octeontx2: Fix mbox driver compilation dependency. >
Re: [linux-yocto] [linux-yocto v5.2] Add the support for the Marvell cn96xx SoC
On Tue, Sep 3, 2019 at 3:39 AM Kevin Hao wrote: > > Hi Bruce, > > This patch series adds the kernel and kernel meta for the support of the > Marvell cn96xx SoC support. These patches are almost the same as what I > have sent for the linux-yocto-dev [1] [2]. The major difference between I assume that you still also want the linux-yocto-dev changes merged ? That is mhy plan. > them is that the BPHY driver is added. The BPHY driver handles ioctl to > set/clear irq handlers in EL3 using SMC calls. The purpose of this is to > handle some BPHY interrupts in userspace directly. In order to support this, > we have to make some ugly hack to some core files like arch/arm64/mm/context.c > or arch/arm64/mm/context.c, but the change is pretty simple and are protected > with the specific kernel option. perfect. Sounds safe for standard/base, so I'll look at merging it there. Bruce > > [1] > https://lists.yoctoproject.org/pipermail/linux-yocto/2019-August/007886.html > [2] > https://lists.yoctoproject.org/pipermail/linux-yocto/2019-August/007887.html > > Thanks, > Kevin -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-dev] Add the support for the Marvell cn96xx SoC
On Fri, Aug 30, 2019 at 1:01 AM Kevin Hao wrote: > > On Tue, Aug 20, 2019 at 07:21:04PM +0800, Kevin Hao wrote: > > Hi Bruce, > > > > This patch series adds the support for the Marvell cn96xx SoC. The OCTEON > > TX2 > > cn96xx SoC is a scalable architecture that integrates high performance > > 64-bit > > Armv8.2 processors, a cache-coherent interconnect, hardware accelerators, > > virtualized networking, and scalable I/O. It support the following > > industry-standard I/O interfaces: > > DDR4 DRAM > > PCI Express 4.0 version 1.0 > > SGMII > > QSGMII > > XAUI > > XFI > > CAUI > > > > Most of the patches are for the Marvell specific drivers. So in theory, it > > should be safe to merge these patches to the standard/base branch. But I > > prefer to stage them to the specific standard/cn96xx branch. The reason is > > that we plan to support other Marvell SoCs, and the SDK for them may be > > based on different SDK versions. They will definitely touch some common > > files affect by this patch series. So it would be a nightmare for us to > > support them if these patches are merged to the standard/base branch. > > Ping... Sorry. I managed to miss this after my vacation. Once I have the current critical issues in master (around the 5.2 kernel) sorted out, I'll get this merged. I hope to have that done today. Bruce > > Thanks, > Kevin > > > > > The following changes since commit ce4ec6ff9589e3b1dcc4e3a0b192b02823631c3e: > > > > Merge tag 'v5.3-rc5' into standard/base (2019-08-18 22:40:47 -0400) > > > > are available in the Git repository at: > > > > git://github.com/haokexin/linux standard/cn96xx > > > > for you to fetch changes up to 4fae437f7ea88d2aab10cac684e11d94b12114bd: > > > > octeontx2-af: Fix the using of variable length arrays (2019-08-20 > > 11:25:36 +0800) > > > > > > Aleksey Makarov (6): > > octeontx2-pf: Set irq affinity hints for CQ interrupts > > octeontx2-pf: Implement ndo_tx_timeout callback > > octeontx2-pf: Support queue interrupts > > octeontx2-pf: Add reset count to stats > > octeontx2-af: Add low level support for Marvell PTP coprocessor > > octeontx2-pf: Add support for PTP clock > > > > Angela Czubak (2): > > octeontx2-af: fix rvu_sso_ggrp_taq_flush > > octeontx2-af: fix cgx_lmac_rx_tx_enable > > > > Chandrakala Chavva (1): > > mmc: cavium_thunderx: Use proper register to clear interrupts > > > > Christina Jacob (21): > > octeontx2-pf: BQL support. > > octeontx2-pf: IRQ coalescing config and tuning via ethtool > > octeontx2-af: Dump current resource provisioning status > > octeontx2-pf: Adding ethtool support for link status information. > > octeontx2-af: Patch to prevent redundant message from pf to af. > > octeontx2-pf: Fix redundant message from AF to PF > > octeontx2-af: Support to get link info like current speed, fec etc > > octeontx2-pf: Ethtool support for fec configuration > > octeontx2-pf: Fix smmuv3 messages while deferring pf driver probe. > > octeontx2-af: Move to rvu_fwdata version 1. > > octeontx2-pf: Add ethtool -m option support. > > octeontx2-af: Extend fwdata structure with additional information. > > octeontx2-af: Update fwadata structure with few more reserved fields. > > octeontx2-af: Fetch FEC stats of the physical link > > octeontx2-pf: Support to display fec counters also in ethtool stats. > > octeontx2-af: sync ATF and Kernel firmware data structure. > > octeontx2-pf: Support to display current settings of a vf network > > interface via ethtool > > net:thunderx: fix memory leak in nicvf driver. > > soc: octeontx2: Add mdio command interface using debugfs > > octeontx2-af: Introduce SET_LINK_MODE command to change various > > configurations of a network interface. > > octeontx2-pf: support to change link speed and autoneg > > > > Felix Manlunas (2): > > octeontx2-af: Add new CGX_CMDs to set and get PHY modulation type > > octeontx2-pf: Add ethtool priv flag to control PAM4 on/off > > > > Geetha sowjanya (26): > > octeontx2-af: Sync hw mbox with bounce buffer. > > octeontx2-pf: Add mailbox bounce buffer > > octeontx2-pf: Add interface stats to ndo_get_stats64 > > octeontx2-af: Config receive and transmission of pause frames > > octeontx2-af: Add mbox message to enable/disable pause frames. > > octeontx2-af: Add mbox messages to configure backpressure for an > > interface. > > octeontx2-pf: Add ethtool support to enable/disable pause frames > > octeontx2-pf: Configure RED drop levels for packet reception. > > octeontx2-pf: Configure backpressure level for packet reception > > octeontx2-pf: Skip CQ_STATUS read if pending CQEs greater than budget > > octeontx2-pf: Set RVU PF/VF watchdog
Re: [linux-yocto] [kernel-meta v5.2 0/2] Fix the kernel_configcheck warnings for the v5.2 kernel
Thanks Kevin, I now have these merged and they'll be part of my next 5.2 recipe revision. Bruce On Thu, Aug 29, 2019 at 4:30 AM Kevin Hao wrote: > > These two patches fix the kernel_configcheck warnings when building the > v5.2 kernel. > > Kevin Hao (2): > fsl-mpc8315e-rdb/beaglebone: Replace CONFIG_MTD_NAND with > CONFIG_MTD_RAW_NAND > beaglebone: Drop the stale kernel options > > bsp/beaglebone/beaglebone.cfg | 4 +--- > bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg | 2 +- > 2 files changed, 2 insertions(+), 4 deletions(-) > > -- > 2.14.4 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache master] nxp-ls20xx: add kernel-cache configuration files for BSP nxp-ls20xx
merged Bruce On Thu, Aug 29, 2019 at 3:08 AM Xulin Sun wrote: > > This adds the cfg & scc files to support the LS2088A-RDB. > > Signed-off-by: Xulin Sun > --- > bsp/nxp-ls20xx/nxp-ls20xx-standard.scc | 8 ++ > bsp/nxp-ls20xx/nxp-ls20xx.cfg | 162 + > bsp/nxp-ls20xx/nxp-ls20xx.scc | 7 ++ > 3 files changed, 177 insertions(+) > create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.cfg > create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.scc > > diff --git a/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > new file mode 100755 > index ..e0d9b2b7 > --- /dev/null > +++ b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > @@ -0,0 +1,8 @@ > +define KMACHINE nxp-ls20xx > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard/standard.scc > +branch nxp-ls20xx > + > +include nxp-ls20xx.scc > diff --git a/bsp/nxp-ls20xx/nxp-ls20xx.cfg b/bsp/nxp-ls20xx/nxp-ls20xx.cfg > new file mode 100755 > index ..f554c916 > --- /dev/null > +++ b/bsp/nxp-ls20xx/nxp-ls20xx.cfg > @@ -0,0 +1,162 @@ > +.. > +.WARNING > +. > +. This file is a kernel configuration fragment, and not a full kernel > +. configuration file. The final kernel configuration is made up of > +. an assembly of processed fragments, each of which is designed to > +. capture a specific part of the final configuration (e.g. platform > +. configuration, feature configuration, and board specific hardware > +. configuration). For more information on kernel configuration, please > +. consult the product documentation. > +. > +.. > + > +CONFIG_ARM64=y > +CONFIG_ARM64_VA_BITS_48=y > +CONFIG_ARCH_LAYERSCAPE=y > +CONFIG_SCHED_MC=y > +CONFIG_ARM_SMMU=y > +CONFIG_ARM_SMMU_V3=y > + > +CONFIG_PCI=y > +CONFIG_PCI_LAYERSCAPE=y > +CONFIG_PCI_HOST_GENERIC=y > +CONFIG_PCI_XGENE=y > +CONFIG_PCI_MSI=y > + > +CONFIG_CPU_FREQ=y > +CONFIG_CPU_FREQ_STAT=y > +CONFIG_CPU_FREQ_GOV_POWERSAVE=y > +CONFIG_CPU_FREQ_GOV_USERSPACE=y > +CONFIG_CPU_FREQ_GOV_ONDEMAND=y > +CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y > +CONFIG_CPUFREQ_DT=y > +CONFIG_QORIQ_CPUFREQ=y > + > +CONFIG_MTD=y > +CONFIG_MTD_CMDLINE_PARTS=y > +CONFIG_MTD_BLOCK=y > +CONFIG_MTD_CFI=y > +CONFIG_MTD_CFI_ADV_OPTIONS=y > +CONFIG_MTD_CFI_INTELEXT=y > +CONFIG_MTD_CFI_AMDSTD=y > +CONFIG_MTD_CFI_STAA=y > +CONFIG_MTD_DATAFLASH=y > +CONFIG_MTD_M25P80=y > +CONFIG_MTD_SST25L=y > +CONFIG_MTD_SPI_NOR=y > +CONFIG_MTD_RAW_NAND=y > +CONFIG_MTD_NAND_FSL_IFC=y > +CONFIG_SPI_FSL_QUADSPI=y > +CONFIG_SCSI_SAS_ATA=y > +CONFIG_SCSI_HISI_SAS=y > +CONFIG_ATA=y > +CONFIG_SATA_AHCI=y > +CONFIG_SATA_AHCI_PLATFORM=y > +CONFIG_AHCI_CEVA=y > +CONFIG_AHCI_XGENE=y > +CONFIG_AHCI_QORIQ=y > +CONFIG_SATA_SIL24=y > + > +CONFIG_FSL_XGMAC_MDIO=y > +CONFIG_HNS_DSAF=y > +CONFIG_HNS_ENET=y > +CONFIG_E1000=y > +CONFIG_E1000E=y > + > +CONFIG_SERIAL_8250=y > +CONFIG_SERIAL_8250_CONSOLE=y > +CONFIG_SERIAL_8250_DW=y > +CONFIG_SERIAL_OF_PLATFORM=y > +CONFIG_SERIAL_FSL_LPUART=y > +CONFIG_SERIAL_FSL_LPUART_CONSOLE=y > + > +CONFIG_SPI=y > +CONFIG_SPI_FSL_DSPI=y > +CONFIG_SPI_PL022=y > +CONFIG_SPI_NXP_FLEXSPI=y > + > +CONFIG_POWER_RESET_XGENE=y > +CONFIG_POWER_RESET_SYSCON=y > +CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y > + > +CONFIG_THERMAL=y > +CONFIG_THERMAL_OF=y > +CONFIG_CPU_THERMAL=y > +CONFIG_THERMAL_EMULATION=y > +CONFIG_WATCHDOG=y > +CONFIG_ARM_SP805_WATCHDOG=y > + > +CONFIG_USB=y > +CONFIG_USB_OTG=y > +CONFIG_USB_XHCI_HCD=y > +CONFIG_USB_STORAGE=y > +CONFIG_USB_DWC3=y > +CONFIG_USB_DWC2=y > +CONFIG_USB_GADGET=y > + > +CONFIG_MMC=y > +CONFIG_MMC_ARMMMCI=y > +CONFIG_MMC_SDHCI=y > +CONFIG_MMC_SDHCI_PLTFM=y > +CONFIG_MMC_SDHCI_OF_ARASAN=y > +CONFIG_MMC_SDHCI_OF_ESDHC=y > +CONFIG_MMC_SDHCI_CADENCE=y > +CONFIG_MMC_SPI=y > +CONFIG_MMC_DW=y > + > +CONFIG_GPIOLIB=y > +CONFIG_OF_GPIO=y > + > +CONFIG_MDIO_DEVICE=y > +CONFIG_MDIO_BITBANG=y > +CONFIG_PHYLIB=y > +CONFIG_AQUANTIA_PHY=y > +CONFIG_CORTINA_PHY=y > + > +# > +# I2C support > +# > +CONFIG_I2C=y > +CONFIG_I2C_MUX=y > +CONFIG_I2C_IMX=y > +CONFIG_I2C_MUX_PCA954x=y > + > +CONFIG_RTC_CLASS=y > +CONFIG_RTC_DRV_DS3232=y > +CONFIG_RTC_DRV_PL031=y > +CONFIG_RTC_DRV_PCF2127=y > + > +CONFIG_DMADEVICES=y > +CONFIG_FSL_EDMA=y > +CONFIG_CMA=y > +CONFIG_DMA_CMA=y > + > +CONFIG_VFIO=y > +CONFIG_VFIO_PCI=y > + > +CONFIG_STAGING=y > +CONFIG_FSL_MC_BUS=y > +CONFIG_FSL_MC_DPIO=y > + > +CONFIG_CLK_QORIQ=y > + > +CONFIG_PHY_XGENE=y > + > +CONFIG_CRYPTO_DEV_FSL_CAAM=y > +CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=y > +CONFIG_ARM64_CRYPTO=y > +CONFIG_CRYPTO_SHA1_ARM64_CE=y > +CONFIG_CRYPTO_SHA2_ARM64_CE=y > +CONFIG_CRYPTO_GHASH_ARM64_CE=y > +CONFIG_CRYPTO_AES_ARM64_CE_CCM=y > +CONFIG_CRYPTO_AES_ARM64_CE_BLK=y > +# CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT is not set > + > +# EDAC > +CONFIG_EDAC_LAYERSCAPE=y > + > +CONFIG_SENSORS_LM90=y >
Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: add some patches to improve features on renesas-rcar platform
all three are now merged to linux-yocto-dev. Bruce On Thu, Aug 29, 2019 at 2:31 AM wrote: > > From: Limeng > > Hi Bruce, > > I am working on BSP renesas-rcar platform, and intend to merge this BSP > supporting into yocto community. > Below 3 patches are used to improve gpio, CAN BUS, audio and PCIe features > > 0001-arch-arm64-dts-Set-gpio5-pin9-as-input-by-default.patch > 0002-driver-net-can-disable-clock-when-it-is-in-enable-st.patch > 0003-pci-pcie-rcar-add-regulators-support.patch > > Could you please merge the 3 patches into linux-yocto-dev, branch is > standard/base? > > arch/arm64/boot/dts/renesas/ulcb-kf.dtsi | 56 +++ > drivers/net/can/rcar/rcar_can.c |5 +- > drivers/pci/controller/pcie-rcar.c | 64 > +++ > 3 files changed, 124 insertions(+), 1 deletion(-) > > > thanks, > Limeng -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] renesas-rcar: enable PCM3168A-I2C codec drvier
merged to master. Bruce On Tue, Aug 27, 2019 at 4:59 AM wrote: > > From: Limeng > > On KingFisher board, there is PCM3168A codec chip, so enable > PCM3168A-I2C codec driver by setting configure > CONFIG_SND_SOC_PCM3168A_I2C > > Signed-off-by: Meng Li > --- > bsp/renesas-rcar/renesas-rcar.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/renesas-rcar/renesas-rcar.cfg > b/bsp/renesas-rcar/renesas-rcar.cfg > index 102441ab..cc896276 100644 > --- a/bsp/renesas-rcar/renesas-rcar.cfg > +++ b/bsp/renesas-rcar/renesas-rcar.cfg > @@ -96,6 +96,7 @@ CONFIG_SND_SOC_AK4613=y > CONFIG_SND_SOC_HDMI_CODEC=y > CONFIG_SND_SIMPLE_CARD=y > CONFIG_SND_AUDIO_GRAPH_CARD=y > +CONFIG_SND_SOC_PCM3168A_I2C=y > > # Clock configuration > CONFIG_COMMON_CLK=y > -- > 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 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] aufs: for v5.3-rc3, update UAPI SPDX
merged
Bruce
On Thu, Aug 29, 2019 at 9:52 AM wrote:
>
> From: "J. R. Okajima"
>
> Simply follows the commit in mainline,
> 622445541b75 2019-07-29 kbuild: detect missing "WITH
> Linux-syscall-note" for uapi headers
>
> Signed-off-by: J. R. Okajima
>
> Backport from git://github.com/sfjro/aufs5-linux.git
> 90ff497cebbb ("aufs: for v5.3-rc3, update UAPI SPDX")
> to fix,
> error: kernel-source/include/uapi/linux/aufs_type.h: missing "WITH
> Linux-syscall-note" for SPDX-License-Identifier
>
> Signed-off-by: He Zhe
> ---
> This is for linux-yocto-dev all branches.
>
> include/uapi/linux/aufs_type.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/aufs_type.h b/include/uapi/linux/aufs_type.h
> index 0e3e2b1..59f050c 100644
> --- a/include/uapi/linux/aufs_type.h
> +++ b/include/uapi/linux/aufs_type.h
> @@ -1,4 +1,4 @@
> -/* SPDX-License-Identifier: GPL-2.0 */
> +/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
> /*
> * Copyright (C) 2005-2019 Junjiro R. Okajima
> *
> --
> 2.7.4
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] module: Fix build failure due to cracked commit
oops. Sorry about that, I forgot to push the resolution I did earlier
today for this. It should be in the tree now.
Bruce
On Mon, Aug 26, 2019 at 10:14 PM wrote:
>
> From: He Zhe
>
> This is the missing half of the following commit that is cracked during
> merging,
> which causes build failure.
> 3b5be16c7e90 ("modules: page-align module section allocations only for arches
> supporting strict module rwx")
>
> Signed-off-by: He Zhe
> ---
> This is for every branches of linux-yocto-dev.
>
> kernel/module.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/module.c b/kernel/module.c
> index 92e3c2e..9ee9342 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -69,6 +69,9 @@
> */
> #ifdef CONFIG_ARCH_HAS_STRICT_MODULE_RWX
> # define debug_align(X) ALIGN(X, PAGE_SIZE)
> +#else
> +# define debug_align(X) (X)
> +#endif
>
> /* If this is set, the section belongs in the init part of the module */
> #define INIT_OFFSET_MASK (1UL << (BITS_PER_LONG-1))
> --
> 2.7.4
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [linux-yocto-dev] Merge tag 'v5.3-rc6' into standard/base
On Mon, Aug 26, 2019 at 6:50 AM Jun Miao wrote: > > Hi Bruce, > >I am sorry to trouble you . > >When you merge tag 'v5.3-rc6' into standard/base, why you delete "define > debug_align(X) (X)" and lose the "#endif" (#ifend ... #endif) ? > Hmm. That wasn't on purpose. My builds ran overnight, so I'll have a look and fix it up. Bruce > > -- > > commit b73b90b1d2cc6b4ba740e66479ab054482174f94 > Merge: ce4ec6f a55aa89 > Author: Bruce Ashfield > Date: Sun Aug 25 22:28:04 2019 -0400 > > Merge tag 'v5.3-rc6' into standard/base > > Linux 5.3-rc6 > > Signed-off-by: Bruce Ashfield > > diff --cc kernel/module.c > index cd8df51,9ee9342..92e3c2e > --- a/kernel/module.c > +++ b/kernel/module.c > @@@ -64,9 -64,14 +64,11 @@@ > > /* >* Modules' sections will be aligned on page boundaries > - * to ensure complete separation of code and data > + * to ensure complete separation of code and data, but > + * only when CONFIG_ARCH_HAS_STRICT_MODULE_RWX=y >*/ > + #ifdef CONFIG_ARCH_HAS_STRICT_MODULE_RWX > # define debug_align(X) ALIGN(X, PAGE_SIZE) > -#else > -# define debug_align(X) (X) > -#endif > > > -- > Thanks > Jun -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] : [kernel-cache master]: renesas-rcar: add configure file for renesas BSP in kernel-cache
On Wed, Aug 21, 2019 at 6:15 AM wrote: > > From: Limeng > > Hi Bruce, > > I am working on BSP renesas-rcar platform, and intend to merge this BSP > supporting into yocto community. > Below patch includes scc and cfg files for renesas-rcar platform. > > Could you please merge this patch into yocto-kernel-cache, branch is master? > Merged! Bruce > > 0001-renesas-rcar-add-configure-file-for-renesas-BSP-in-k.patch > > renesas-rcar-h3-standard.scc |7 + > renesas-rcar-m3-standard.scc |7 + > renesas-rcar.cfg | 251 > +++ > renesas-rcar.scc |8 + > 4 files changed, 273 insertions(+) > > > thanks, > Limeng -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] v4.18.x - stable updates comprising v4.18.42
On Sun, Aug 18, 2019 at 10:14 AM Paul Gortmaker wrote: > > Bruce, Yocto kernel folks: > > Here is the next 4.18.x stable update "extension" primarily created > for the Yocto project, continuing from the previous v4.18.41 release. > > There are about 150 commits here, based on the remaining commits that > were used in the 4.19.46/47 stable releases -- but not put into the > previous 4.10.40 release in order to keep the commit count reasonable. > > These 4.18 stable backport releases will be ending in September, as I > will be moving to working on newer kernels. Hopefully with the same > messaging being in the last few releases, this is no surprise to anyone, > and people are in the final stages of getting their own maintenance or > migration plans in place and rolled out. > > I've put this 4.18.x 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 v4.18.42 tag using this key: > Hey Paul, I was merging this tonight and ran into a nasty -rt merge conflict in kernel/irq_work.c. Can you take a look and send a resolution ? When I compared the 4.19-rt and 5.x-rt branches, I didn't see an obvious way to resolve things. Bruce > 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-4.18.y.git/?h=linux-4.18.y > git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git > > for merge to standard/base in linux-yocto-4.18 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-4.18.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 4.18.x release. > > Paul. -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] modules: always page-align module section allocations
On Fri, Aug 16, 2019 at 12:01 PM wrote:
>
>
> 在 2019年8月16日 23:29，Paul Gortmaker 写下:
> >
> > [[linux-yocto] [PATCH] modules: always page-align module section
> > allocations] On 16/08/2019 (Fri 15:36) zhe...@windriver.com wrote:
> >
> > It helps maintainers if the version is embedded in the subject, like:
> >
> > [PATCH v4.18] modules: always page-align module section
> >
> > > From: Jessica Yu
> > >
> > > Some arches (e.g., arm64, x86) have moved towards non-executable
> > > module_alloc() allocations for security hardening reasons. That means
> > > that the module loader will need to set the text section of a module to
> > > executable, regardless of whether or not CONFIG_STRICT_MODULE_RWX is set.
> > >
> > > When CONFIG_STRICT_MODULE_RWX=y, module section allocations are always
> > > page-aligned to handle memory rwx permissions. On some arches with
> > > CONFIG_STRICT_MODULE_RWX=n however, when setting the module text to
> > > executable, the BUG_ON() in frob_text() gets triggered since module
> > > section allocations are not page-aligned when CONFIG_STRICT_MODULE_RWX=n.
> > > Since the set_memory_* API works with pages, and since we need to call
> > > set_memory_x() regardless of whether CONFIG_STRICT_MODULE_RWX is set, we
> > > might as well page-align all module section allocations for ease of
> > > managing rwx permissions of module sections (text, rodata, etc).
> > >
> > > Fixes: 2eef1399a866 ("modules: fix BUG when load module with rodata=n")
> > > Reported-by: Martin Kaiser
> > > Reported-by: Bartosz Golaszewski
> > > Tested-by: David Lechner
> > > Tested-by: Martin Kaiser
> > > Tested-by: Bartosz Golaszewski
> > > Signed-off-by: Jessica Yu
> > >
> > > commit 38f054d549a869f22a02224cd276a27bf14b6171 upstream
> >
> > Normally we put this right at the top of the long log. Also this commit
> > ID appears bogus - it does not exist in mainline.
>
> Yes, it's from modules-next,
> https://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git/commit/?h=modules-next
I went ahead and cleaned up the commit log, since we never say "commit
upstream", if "upstream" is not linus' main git repo. I've
pointed at modules-next, and hopefully it is well behaved and won't be
rebased.
I didn't see it in -rc5, so hopefully it makes it upstream soon.
>
> I can't wait as It blocks something.
>
> >
> > Also it seems very odd that the block of Signed-off lines are stuck in
> > the middle of the long log.
> >
> > >
> > > When loading modules with CONFIG_ARCH_HAS_STRICT_MODULE_RWX enabled and
> > > CONFIG_STRICT_MODULE_RWX disabled, the memory allocated for modules would
> > > not be page-aligned and cause the following BUG during frob_text.
> > >
> > > [ cut here ]
> > > kernel BUG at kernel/module.c:1907!
> > > Internal error: Oops - BUG: 0 [#1] ARM
> > > Modules linked in:
> > > CPU: 0 PID: 89 Comm: systemd-modules Not tainted 5.3.0-rc2 #1
> > > Hardware name: ARM-Versatile (Device Tree Support)
> > > PC is at frob_text.constprop.0+0x2c/0x40
> > > LR is at load_module+0x14b4/0x1d28
> > > pc : []lr : []psr: 2013
> > > sp : ce44fe58 ip : fp :
> > > r10: r9 : ce44feb8 r8 :
> > > r7 : 0001 r6 : bf00032c r5 : ce44ff40 r4 : bf000320
> > > r3 : bf000400 r2 : 0fff r1 : 0220 r0 : bf00
> > > Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none
> > > Control: 00093177 Table: 0e4c DAC: 0051
> > > Process systemd-modules (pid: 89, stack limit = 0x9fccc8dc)
> > > Stack: (0xce44fe58 to 0xce45)
> > > fe40:
> > > cf1b05b8
> > > fe60: 0001 ce47cf08 bf002754 c07ae5d8 d0a2a484 bf002060 bf0004f8
> > >
> > > fe80: b6d17910 c017cf1c ce47cf00 d0a29000 ce47cf00 ce44ff34 14fc
> > >
> > > fea0: bf00025c 0001 6e72656b
> > > 6c65
> > > fec0:
> > >
> > > fee0: c0ac9048 7fff
> > >
> > > ff00: b6d17910 0005 017b c0009208 ce44e000 b6ebfe54
> > > c008562c
> > > ff20: 7fff 0003 cefd28f8 0001 d0a29000 14fc
> > >
> > > ff40: d0a292cb d0a29380 d0a29000 14fc d0a29f0c d0a29d90 d0a29a60
> > > 0520
> > > ff60: 0710 0718 0826 0708
> > > 0023
> > > ff80: 0024 001c 0016 c0ac9048 0041c620
> > >
> > > ffa0: c0009000 0041c620 0005 b6d17910
> > >
> > > ffc0: 0041c620 017b 0041f078 004098b0
> > > b6ebfe54
> > > ffe0: bedb6bc8 bedb6bb8 b6d0f91c b6c945a0 6010 0005
> > >
> > > [] (frob_text.constprop.0) from []
> > > (load_module+0x14b4/0x1d28)
> > > [] (load_module) from [] (sys_finit_module+0xa0/0xc4)
> > > []
Re: [linux-yocto] [kernel-cache master][PATCH 1/1] ti-am335x: enable kernel options for PMIC support
merged Bruce On Thu, Aug 15, 2019 at 5:29 AM Jun Miao wrote: > > add Power Management IC support. > TPS65910: am335x EVM/SK > TPS65217: am335x BBB > > Signed-off-by: Jun Miao > --- > bsp/ti-am335x/ti-am335x.cfg | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg > index 77085326..bd2711c8 100644 > --- a/bsp/ti-am335x/ti-am335x.cfg > +++ b/bsp/ti-am335x/ti-am335x.cfg > @@ -32,6 +32,8 @@ CONFIG_NEON=y > CONFIG_PM=y > CONFIG_REGMAP_IRQ=y > > +CONFIG_REGULATOR_TPS65910=y > +CONFIG_REGULATOR_TPS65217=y > # > # RAM/ROM/Flash chip drivers > # > -- > 2.22.0 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/4] More security fragments
I've merged these to the 4.19/5.0/5.2 and master branches. SRCREV updates will follow this week, once I get some more test cycles completed. Bruce On Sun, Aug 11, 2019 at 12:29 PM Armin Kuster wrote: > It is time to move the kernel fragments out of meta-security to cache. > It should make maintenance easier. > > Armin Kuster (4): > kernel-cache: add apparmor fragments > kernel-cache: add smack > kernel-cache: add ima fragments > kernel-cache: add yama security fragments > > features/apparmor/apparmor.cfg | 7 +++ > features/apparmor/apparmor.scc | 5 + > features/apparmor/apparmor_on_boot.cfg | 1 + > features/ima/ima.cfg | 18 ++ > features/ima/ima.scc | 4 > features/ima/ima_evm_root_ca.cfg | 3 +++ > features/ima/modsign.cfg | 3 +++ > features/ima/modsign.scc | 6 ++ > features/smack/smack.cfg | 10 ++ > features/smack/smack.scc | 4 > features/yama/yama.cfg | 1 + > features/yama/yama.scc | 4 > 12 files changed, 66 insertions(+) > create mode 100644 features/apparmor/apparmor.cfg > create mode 100644 features/apparmor/apparmor.scc > create mode 100644 features/apparmor/apparmor_on_boot.cfg > create mode 100644 features/ima/ima.cfg > create mode 100644 features/ima/ima.scc > create mode 100644 features/ima/ima_evm_root_ca.cfg > create mode 100644 features/ima/modsign.cfg > create mode 100644 features/ima/modsign.scc > create mode 100644 features/smack/smack.cfg > create mode 100644 features/smack/smack.scc > create mode 100644 features/yama/yama.cfg > create mode 100644 features/yama/yama.scc > > -- > 2.17.1 > > -- > ___ > linux-yocto mailing list > linux-yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/linux-yocto > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache] Question about profiling.scc
On Wed, Aug 7, 2019 at 10:03 PM Hongzhi, Song wrote: > Hi Bruce, > > > profiling.cfg is just designed for powertop and oprofile. > that comment is a bit misleading. Things like perf events, rely on config_profiling .. so it is more of a base config than just for those two. bruce > >1 # for oprofile and powertop >2 CONFIG_PROFILING=y >3 CONFIG_OPROFILE=y >4 CONFIG_FRAME_POINTER=y >5 CONFIG_X86_LOCAL_APIC=y > > Maybe split profiling.cfg and move them to their recipe is a good way. > > > --Hongzhi > > > > On 8/7/19 10:43 AM, Bruce Ashfield wrote: > > > > > > On Mon, Aug 5, 2019 at 11:44 PM Hongzhi, Song > > mailto:hongzhi.s...@windriver.com>> wrote: > > > > Hi Bruce, > > > > I see profiling.scc is included by kernel-cache/bsp/*, such as > > bsp/intel-x86 bsp/common-pc/ ... . > > > > > > My question is that is it necessary to open profiling.cfg defaultly? > > > > > > We left profiling as a per-BSP decision, since production machine > > configurations don't want the overhead that it brings. > > > > Not all BSPs follow the split between developer and production, but > > see how it is used in: > > > > bsp/common-pc-64/common-pc-64-developer.scc:include > > features/profiling/profiling.scc > > bsp/common-pc-64/common-pc-64-preempt-rt.scc:include > > features/profiling/profiling.scc > > > > If it was enabled by default, it really should be in the developer > > ktype and then BSPs could have the split between production and > > developer/debug in their definitions .. with the developer ones > > getting profiling by default. > > > > Bruce > > > > > > > > --Hongzhi > > > > > > > > -- > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > thee at its end > > - "Use the force Harry" - Gandalf, Star Trek II > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] v4.18.x - stable updates comprising v4.18.41
On Fri, Aug 2, 2019 at 11:43 PM Paul Gortmaker wrote: > Bruce, Yocto kernel folks: > > Here is the next 4.18.x stable update "extension" primarily created > for the Yocto project, continuing from the previous v4.18.40 release. > > There are about 220 commits here, based on commits chosen from what were > used in the 4.19.46/47 stable releases -- plus some TCP related commits > that were of interest to reach ahead and source from newer 4.19 now. > Not all the 47 content was processed here, in order to keep the release > size sane. The remainder will be considered for the 4.18.42 release. > > And as we enter August, I need to again remind people that the creation > of these 4.18 stable backport releases will be ending relatively soon, > as I'll expect to be moving to newer kernels used in newer Yocto > releases. So people need to get their own maintenance or migration > plans in place as soon as possible, if they have not yet done so. > > I've put this 4.18.x 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 v4.18.41 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-4.18.y.git/?h=linux-4.18.y > git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git > > for merge to standard/base in linux-yocto-4.18 and then out from there > into the other base and BSP branches. > Thanks Paul, this is now merged! Bruce > > For those who are interested, the evolution of the commits is here: > > > https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-4.18.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 4.18.x release. > > Paul. > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache master][PATCH][V2] ti-am335x: add the basic scc/cfg enablement
I've merged v2, and created the standard/ti-am335x in linux-yocto-dev. Bruce On Wed, Aug 7, 2019 at 3:54 AM Jun Miao wrote: > Add scc/cfg kernel fragment to build and boot EVM/SK and BeagleBone Black > boards all with am335x soc > > Signed-off-by: Jun Miao > --- > bsp/ti-am335x/ti-am335x-standard.scc | 8 + > bsp/ti-am335x/ti-am335x.cfg | 236 +++ > bsp/ti-am335x/ti-am335x.scc | 8 + > cfg/remoteproc.cfg | 3 + > 4 files changed, 255 insertions(+) > create mode 100644 bsp/ti-am335x/ti-am335x-standard.scc > create mode 100644 bsp/ti-am335x/ti-am335x.cfg > create mode 100644 bsp/ti-am335x/ti-am335x.scc > create mode 100644 cfg/remoteproc.cfg > > diff --git a/bsp/ti-am335x/ti-am335x-standard.scc > b/bsp/ti-am335x/ti-am335x-standard.scc > new file mode 100644 > index ..d357a729 > --- /dev/null > +++ b/bsp/ti-am335x/ti-am335x-standard.scc > @@ -0,0 +1,8 @@ > +define KMACHINE ti-am335x > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard/standard.scc > +branch ti-am335x > + > +include ti-am335x.scc > diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg > new file mode 100644 > index ..77085326 > --- /dev/null > +++ b/bsp/ti-am335x/ti-am335x.cfg > @@ -0,0 +1,236 @@ > +#. > +#WARNING > +# > +# This file is a kernel configuration fragment, and not a full kernel > +# configuration file. The final kernel configuration is made up of > +# an assembly of processed fragments, each of which is designed to > +# capture a specific part of the final configuration (e.g. platform > +# configuration, feature configuration, and board specific hardware > +# configuration). For more information on kernel configuration, please > +# consult the product documentation. > +# > +#. > + > +CONFIG_ARM=y > +CONFIG_ARCH_OMAP=y > +CONFIG_OMAP_DM_TIMER=y > +CONFIG_SOC_AM33XX=y > +CONFIG_ARCH_OMAP2PLUS=y > + > + > +# > +# At least one emulation must be selected > +# > +CONFIG_VFP=y > +CONFIG_VFPv3=y > +CONFIG_NEON=y > + > +# > +# Power management options > +# > + > +CONFIG_PM=y > +CONFIG_REGMAP_IRQ=y > + > +# > +# RAM/ROM/Flash chip drivers > +# > +CONFIG_OMAP_OCP2SCP=y > +CONFIG_MTD=y > +CONFIG_MTD_CMDLINE_PARTS=y > +CONFIG_MTD_BLKDEVS=y > +CONFIG_MTD_BLOCK=y > +CONFIG_MTD_NAND_ECC=y > +CONFIG_MTD_RAW_NAND=y > +CONFIG_MTD_CFI=y > +CONFIG_MTD_CFI_INTELEXT=y > + > +CONFIG_MTD_NAND=y > +CONFIG_MTD_NAND_OMAP2=y > +CONFIG_MTD_NAND_OMAP_BCH=y > +CONFIG_MTD_NAND_OMAP_BCH_BUILD=y > + > +# Misc devices > +CONFIG_EEPROM_AT24=y > +CONFIG_SENSORS_LIS3_I2C=y > +CONFIG_BLK_DEV_SD=y > + > +CONFIG_ETHERNET=y > +CONFIG_NET_VENDOR_TI=y > +CONFIG_TI_DAVINCI_MDIO=y > +CONFIG_TI_DAVINCI_CPDMA=y > +CONFIG_TI_CPSW_PHY_SEL=y > +CONFIG_TI_CPSW_ALE=y > +CONFIG_TI_CPSW=y > +CONFIG_TI_CPTS=y > +CONFIG_PHYLIB=y > + > +CONFIG_SMSC_PHY=y > +CONFIG_FIXED_PHY=y > + > +# > +# Input Device Drivers > +# > + > +CONFIG_INPUT=y > +CONFIG_INPUT_MOUSEDEV=y > +CONFIG_INPUT_EVDEV=y > +CONFIG_INPUT_KEYBOARD=y > +CONFIG_KEYBOARD_GPIO=y > +CONFIG_KEYBOARD_MATRIX=y > +CONFIG_INPUT_TOUCHSCREEN=y > +CONFIG_TOUCHSCREEN_TI_AM335X_TSC=y > +CONFIG_INPUT_MISC=y > +CONFIG_INPUT_TPS65218_PWRBUTTON=m > +CONFIG_SERIAL_EARLYCON=y > + > +# > +# 8250 serial port support > +# > + > +CONFIG_SERIAL_8250=y > +CONFIG_SERIAL_8250_CONSOLE=y > +CONFIG_SERIAL_OF_PLATFORM=y > +CONFIG_SERIAL_8250_OMAP=y > +CONFIG_SERIAL_8250_OMAP_TTYO_FIXUP=y > + > +CONFIG_SERIAL_CORE=y > +CONFIG_SERIAL_CORE_CONSOLE=y > + > +CONFIG_HW_RANDOM=y > +CONFIG_HW_RANDOM_OMAP=y > + > +# I2C support > +CONFIG_I2C=y > +CONFIG_I2C_CHARDEV=y > +CONFIG_I2C_OMAP=y > +CONFIG_SENSORS_TSL2550=y > +CONFIG_GPIO_TWL4030=y > +CONFIG_PTP_1588_CLOCK=y > +CONFIG_GPIO_PCF857X=y > +CONFIG_PINCTRL=y > +CONFIG_PINCTRL_SINGLE=y > + > +CONFIG_GPIOLIB=y > +CONFIG_OF_GPIO=y > +CONFIG_GPIOLIB_IRQCHIP=y > +CONFIG_GPIO_SYSFS=y > + > +CONFIG_GPIO_OMAP=y > +CONFIG_GPIO_PCA953X=m > +CONFIG_GPIO_TPS65910=y > + > +CONFIG_WATCHDOG=y > +CONFIG_WATCHDOG_CORE=y > +CONFIG_OMAP_WATCHDOG=m > + > +CONFIG_MFD_SYSCON=y > +CONFIG_MFD_TI_AM335X_TSCADC=y > +CONFIG_MFD_OMAP_USB_HOST=y > +CONFIG_MFD_TPS65217=y > +CONFIG_MFD_TPS65218=y > +CONFIG_MFD_TPS65910=y > +CONFIG_TWL6040_CORE=y > + > +# > +# LCD > +# > +CONFIG_DRM=y > +CONFIG_DRM_OMAP=y > +CONFIG_OMAP2_DSS_DPI=y > +CONFIG_DRM_TILCDC=y > +CONFIG_DRM_OMAP_PANEL_DPI=y > +CONFIG_DRM_I2C_NXP_TDA998X=y > + > +CONFIG_BACKLIGHT_LCD_SUPPORT=y > +CONFIG_LCD_CLASS_DEVICE=y > +CONFIG_LCD_PLATFORM=y > +CONFIG_BACKLIGHT_CLASS_DEVICE=y > +CONFIG_BACKLIGHT_GENERIC=y > +CONFIG_PWM=y > +CONFIG_BACKLIGHT_PWM=y > +CONFIG_BACKLIGHT_GPIO=y > + > + > +CONFIG_SOUND=m > +CONFIG_SND=m > +CONFIG_SND_SOC=m > +CONFIG_SND_DAVINCI_SOC_MCASP=m > +CONFIG_SND_SIMPLE_CARD=m > + > + > +#CONFIG_USB_ANNOUNCE_NEW_DEVICES=y > +#CONFIG_USB_MON=m > + > +# > +#
