[linux-yocto] [PATCH] dma-direct: Temporary DMA fix on arm64

2019-11-11 Thread Meng.Li
From: Phil Elwell 

commit 370e6f18b566f7880f538f5d9e9ca2953389b446 from
https://github.com/raspberrypi/linux.git

See: https://github.com/raspberrypi/linux/issues/3251

Signed-off-by: Phil Elwell 
Signed-off-by: Meng Li 
---
 kernel/dma/direct.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
index 9912be7..bf1846a 100644
--- a/kernel/dma/direct.c
+++ b/kernel/dma/direct.c
@@ -379,7 +379,7 @@ int dma_direct_supported(struct device *dev, u64 mask)
if (IS_ENABLED(CONFIG_ZONE_DMA))
min_mask = DMA_BIT_MASK(ARCH_ZONE_DMA_BITS);
else
-   min_mask = DMA_BIT_MASK(32);
+   min_mask = DMA_BIT_MASK(30);
 
min_mask = min_t(u64, min_mask, (max_pfn - 1) << PAGE_SHIFT);
 
-- 
2.7.4

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto


[linux-yocto] [linux-yocto-5.2]: [kernel v5.2/standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: dma-direct: Temporary DMA fix on arm64

2019-11-11 Thread Meng.Li
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.

diffstat info ad below:

 direct.c |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


thanks,
Limeng
-- 
___
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

2019-11-11 Thread Bruce Ashfield
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&search=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


[linux-yocto] [PATCH 1/1] sound: soc: xilinx: give a name to stream_name in xilinx_dp_dai_links

2019-11-11 Thread quanyang.wang
From: Quanyang Wang 

If .stream_name is NULL, when calling "aplay -l", it will show:

card 0: monitor [DisplayPort monitor], device 0: (null) 
xilinx-dp-snd-codec-dai-0 [(null) xilinx-dp-snd-codec-dai-0]

Adding .stream_name can eliminate the "(null)" in the output.

Signed-off-by: Quanyang Wang 
---
 sound/soc/xilinx/xilinx-dp-card.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/sound/soc/xilinx/xilinx-dp-card.c 
b/sound/soc/xilinx/xilinx-dp-card.c
index c99faccf666a..a149da095df8 100644
--- a/sound/soc/xilinx/xilinx-dp-card.c
+++ b/sound/soc/xilinx/xilinx-dp-card.c
@@ -37,11 +37,13 @@ static const struct snd_soc_ops xilinx_dp_ops = {
 static struct snd_soc_dai_link xilinx_dp_dai_links[] = {
{
.name   = "xilinx-dp0",
+   .stream_name= "xilinx-dp0",
.codec_dai_name = "xilinx-dp-snd-codec-dai",
.ops= &xilinx_dp_ops,
},
{
.name   = "xilinx-dp1",
+   .stream_name= "xilinx-dp1",
.codec_dai_name = "xilinx-dp-snd-codec-dai",
.ops= &xilinx_dp_ops,
},
-- 
2.17.1

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto


[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

2019-11-11 Thread quanyang.wang
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?

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

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto