[linux-yocto][linux-yocto cn96xx] marvell-cn96xx kernel update for linux-yocto v5.4

2020-12-21 Thread Ruiqiang Hao
Hi Bruce,

Please help to merge follow kernel code into our marvell-cn96xx repos.

repo: linux-yocto

branch:
v5.4/standard/cn96xx
v5.4/standard/preempt-rt/cn96xx

Thanks,
Ruiqiang

The following changes since commit 6e05fd5bacbaf8833b4a619f5041432e4737e93c:

  octeontx2-af: add SSO mbox message to release XAQ aura (2020-10-14 02:09:25 
+)

are available in the Git repository at:

  https://github.com/cythe/linux-yocto.git v5.4/standard/cn96xx

for you to fetch changes up to ffd5b3a957c20f78312d75d284db43607bb7112a:

  octeontx2-bphy-netdev: Add PTP hardware clock support to rfoe interfaces 
(2020-12-22 02:23:10 +)


Chandrakala Chavva (1):
  driver: serdes_debugfs: Add inject optional parameter to prbs command

Geetha sowjanya (1):
  octeontx2-pf: Fix interface down flag on error

George Cherian (1):
  octeontx2-af: Add support for RSS hashing based on Transport protocol 
field

Hariprasad Kelam (4):
  octeontx2-af: Assign valid mac address for LBKVFs
  octeontx2-af: Pass default values incase user did not specify
  octeontx2-pf: support to change link speed/duplex/autoneg
  octeontx2-pf: add Support QSGMII mode

Harman Kalra (2):
  octeontx2-af: load NPC profile via firmware database
  octeontx2-af: fix msix offset structure field data types

Kiran Kumar K (1):
  octeontx2-af: limit KPU parsing for GTPU only to GTPv1

Naveen Mamindlapalli (5):
  octeontx2-bphy-netdev: Fix kernel crash with ioctl trying to add timer
  octeontx2-bphy-netdev: Fix ptp pending skb list processing
  octeontx2-bphy-netdev: Added ioctl to set low level link state
  octeontx2-bphy-netdev: Fix list_entry usage in the code
  octeontx2-bphy-netdev: Add PTP hardware clock support to rfoe interfaces

Nithin Dabilpuram (1):
  octeontx2-af: fix order of queue work and interrupt disable

Rick Farrington (2):
  ghes_edac: remove erroneous error message regarding DIMM info
  drivers: marvell: otx2-sdei-ghes: fix BERT init error when RAS is disabled

Shijith Thotton (1):
  octeontx2-af: add NIX mbox message to get HW info

Smadar Fuks (2):
  octeontx2-af: Add register check to rvu_poll_reg()
  octeontx2-af: REE timeout error handling

Subbaraya Sundeep (10):
  octeontx2-af: Introduce tracepoints for mailbox
  octeontx2-pf: Add tracepoints for PF/VF mailbox
  octeontx2-af: Fix loading external MKEX profile
  octeontx2-af: Do not shift more than data type size
  octeontx2-af: Add IPv6 Src/Dst ip to MCAM rules
  octeontx2-af: Add SCTP Src/Dst ports to MCAM rules
  octeontx2-pf: Add raw IPv4 and SCTP4 filters
  octeontx2-pf: Add IPv6 and SCTP6 ntuple filters
  octeontx2-pf: Set NIX1_RX interface for backpressure
  octeontx2-af: Allocate low priority entries for PF

Suneel Garapati (2):
  drivers: i2c: octeon: Reduce latency for HS mode
  drivers: i2c: octeon: Revert early clear of IFLG

Yuri Tolstov (1):
  octeontx2-rm: Add char driver to RM

 drivers/edac/ghes_edac.c   |   3 +
 drivers/i2c/busses/i2c-octeon-core.c   |  18 +-
 drivers/net/ethernet/marvell/octeontx2/af/Makefile |   3 +-
 drivers/net/ethernet/marvell/octeontx2/af/cgx.c|   9 +-
 drivers/net/ethernet/marvell/octeontx2/af/mbox.c   |  11 +-
 drivers/net/ethernet/marvell/octeontx2/af/mbox.h   |  29 ++-
 .../ethernet/marvell/octeontx2/af/npc_profile.h|  10 +-
 drivers/net/ethernet/marvell/octeontx2/af/rvu.c|  33 ++-
 drivers/net/ethernet/marvell/octeontx2/af/rvu.h|  13 +
 .../net/ethernet/marvell/octeontx2/af/rvu_cgx.c|   2 +
 .../ethernet/marvell/octeontx2/af/rvu_debugfs.c|   2 +
 .../net/ethernet/marvell/octeontx2/af/rvu_nix.c|  25 ++
 .../net/ethernet/marvell/octeontx2/af/rvu_npc.c| 128 --
 .../net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c | 114 +++--
 .../net/ethernet/marvell/octeontx2/af/rvu_ree.c|  94 +++
 .../net/ethernet/marvell/octeontx2/af/rvu_reg.h|   1 +
 .../net/ethernet/marvell/octeontx2/af/rvu_trace.c  |  12 +
 .../net/ethernet/marvell/octeontx2/af/rvu_trace.h  | 103 
 .../net/ethernet/marvell/octeontx2/bphy/Makefile   |   2 +-
 .../ethernet/marvell/octeontx2/bphy/otx2_bphy.h|   9 +
 .../marvell/octeontx2/bphy/otx2_bphy_main.c| 108 +++-
 .../ethernet/marvell/octeontx2/bphy/otx2_cpri.c|   3 +
 .../ethernet/marvell/octeontx2/bphy/otx2_cpri.h|   7 +
 .../ethernet/marvell/octeontx2/bphy/otx2_rfoe.c|  38 ++-
 .../ethernet/marvell/octeontx2/bphy/otx2_rfoe.h|  17 ++
 .../marvell/octeontx2/bphy/otx2_rfoe_ethtool.c |   4 +-
 .../marvell/octeontx2/bphy/otx2_rfoe_ptp.c |  85 +++
 .../ethernet/marvell/octeontx2/nic/otx2_common.c   |  19 +-
 .../ethernet/marvell/octeontx2/nic/otx2_common.h   |   5 +-
 .../ethernet/marvell/octeontx2/nic/otx2_ethtool.c  | 197 +++
 

[linux-yocto] Question on i915: adust helper to 'm'

2020-12-21 Thread Zhang, Qiang
Hello Bruce

about commit 27ad9c754f20bdc59d281e6bc7c9b2a96bbed0ee
There is warning here:


[NOTE]: 'CONFIG_DRM_KMS_HELPER' last val (m) and .config val (y) do not match
[INFO]: CONFIG_DRM_KMS_HELPER : y ## .config: 4070 
:configs/standard/intel-x86/features/i915/i915.cfg (m) 
[INFO]: raw config text:

config DRM_KMS_HELPER
tristate
depends on DRM && HAS_IOMEM
help
  CRTC helpers for KMS drivers.

Config 'DRM_KMS_HELPER' has the following Direct dependencies 
(DRM_KMS_HELPER=y):
DRM(=y) && HAS_IOMEM(=y)
Parent dependencies are:
 HAS_IOMEM [y] DRM [y]
[INFO]: config 'CONFIG_DRM_KMS_HELPER' was set, but it wasn't assignable, 
check (parent) dependencies

[INFO]: selection details for 'CONFIG_DRM_KMS_HELPER':
Symbols currently y-selecting this symbol:
  - DRM_FBDEV_EMULATION
  - DRM_VIRTIO_GPU

Symbols currently m-selecting this symbol:
  - DRM_RADEON
  - DRM_NOUVEAU
  - DRM_I915
  - DRM_MGAG200


I find this will trigger Warning:

Symbol: DRM_FBDEV_EMULATION [=y]
  
Type  : bool   
Selects: DRM_KMS_HELPER [=y] && DRM_KMS_FB_HELPER [=y]

Thanks
Qiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9305): 
https://lists.yoctoproject.org/g/linux-yocto/message/9305
Mute This Topic: https://lists.yoctoproject.org/mt/79144148/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][linux-yocto-dev cn96xx] kernel update for linux-yocto-dev v5.9

2020-12-21 Thread Ruiqiang Hao
Hi Bruce,

Please help to merge this patch into our linux-yocto-dev repo.

repo:
linux-yocto-dev
branch:
v5.9/standard/base

Thanks,
Ruiqiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9303): 
https://lists.yoctoproject.org/g/linux-yocto/message/9303
Mute This Topic: https://lists.yoctoproject.org/mt/79143735/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [linux-yocto-dev standard/xlnx-soc][PATCH 1/1] dmaengine: xilinx: dpdma: add dma cyclic mode

2020-12-21 Thread quanyang.wang
From: Quanyang Wang 

The dma cyclic mode is required by DP audio, so add it to make DP audio
work.

Reference: b78c51347044 ("dma: xilinx: dpdma: Add the Xilinx DisplayPort DMA 
engine driver") from https://github.com/Xilinx/linux-xlnx.git
Signed-off-by: Quanyang Wang 
---
 drivers/dma/xilinx/xilinx_dpdma.c | 131 ++
 1 file changed, 131 insertions(+)

diff --git a/drivers/dma/xilinx/xilinx_dpdma.c 
b/drivers/dma/xilinx/xilinx_dpdma.c
index 55df63dead8d..580cd6b8cea3 100644
--- a/drivers/dma/xilinx/xilinx_dpdma.c
+++ b/drivers/dma/xilinx/xilinx_dpdma.c
@@ -499,6 +499,39 @@ static inline void dpdma_set(void __iomem *base, u32 
offset, u32 set)
  * Descriptor Operations
  */
 
+/**
+ * xilinx_dpdma_sw_desc_next_32 - Set 32 bit address of a next sw descriptor
+ * @sw_desc: current software descriptor
+ * @next: next descriptor
+ *
+ * Update the current sw descriptor @sw_desc with 32 bit address of the next
+ * descriptor @next.
+ */
+static inline void
+xilinx_dpdma_sw_desc_next_32(struct xilinx_dpdma_sw_desc *sw_desc,
+struct xilinx_dpdma_sw_desc *next)
+{
+   sw_desc->hw.next_desc = next->dma_addr;
+}
+
+/**
+ * xilinx_dpdma_sw_desc_next_64 - Set 64 bit address of a next sw descriptor
+ * @sw_desc: current software descriptor
+ * @next: next descriptor
+ *
+ * Update the current sw descriptor @sw_desc with 64 bit address of the next
+ * descriptor @next.
+ */
+static inline void
+xilinx_dpdma_sw_desc_next_64(struct xilinx_dpdma_sw_desc *sw_desc,
+struct xilinx_dpdma_sw_desc *next)
+{
+   sw_desc->hw.next_desc = lower_32_bits(next->dma_addr);
+   sw_desc->hw.addr_ext |= upper_32_bits(next->dma_addr) &
+   XILINX_DPDMA_DESC_ADDR_EXT_NEXT_ADDR_MASK;
+}
+
+
 /**
  * xilinx_dpdma_sw_desc_set_dma_addrs - Set DMA addresses in the descriptor
  * @xdev: DPDMA device
@@ -737,6 +770,77 @@ xilinx_dpdma_chan_prep_interleaved_dma(struct 
xilinx_dpdma_chan *chan,
return tx_desc;
 }
 
+/**
+ * xilinx_dpdma_chan_prep_cyclic_dma - Prepare a cyclic dma
+ * descriptor
+ * @chan: DPDMA channel
+ * @buf_addr: buffer address
+ * @buf_len: buffer length
+ * @period_len: number of periods
+ *
+ * Prepare a tx descriptor including internal software/hardware descriptors
+ * for the given cyclic transaction.
+ *
+ * Return: A DPDMA TX descriptor on success, or NULL.
+ */
+static struct xilinx_dpdma_tx_desc *
+xilinx_dpdma_chan_prep_cyclic_dma(struct xilinx_dpdma_chan *chan,
+ dma_addr_t buf_addr, size_t buf_len,
+ size_t period_len)
+{
+   struct xilinx_dpdma_tx_desc *tx_desc;
+   struct xilinx_dpdma_sw_desc *sw_desc, *last = NULL;
+   unsigned int periods = buf_len / period_len;
+   unsigned int i;
+
+   tx_desc = xilinx_dpdma_chan_alloc_tx_desc(chan);
+   if (!tx_desc)
+   return NULL;
+
+   for (i = 0; i < periods; i++) {
+   struct xilinx_dpdma_hw_desc *hw_desc;
+
+   if (!IS_ALIGNED(buf_addr, XILINX_DPDMA_ALIGN_BYTES)) {
+   dev_err(chan->xdev->dev, "buffer should be aligned at 
%d B\n",
+   XILINX_DPDMA_ALIGN_BYTES);
+   return NULL;
+   }
+
+   sw_desc = xilinx_dpdma_chan_alloc_sw_desc(chan);
+   if (!sw_desc) {
+   xilinx_dpdma_chan_free_tx_desc(_desc->vdesc);
+   return NULL;
+   }
+
+   xilinx_dpdma_sw_desc_set_dma_addrs(chan->xdev, sw_desc, last,
+   _addr, 1);
+   hw_desc = _desc->hw;
+   hw_desc->xfer_size = period_len;
+   hw_desc->hsize_stride =
+   FIELD_PREP(XILINX_DPDMA_DESC_HSIZE_STRIDE_HSIZE_MASK, 
period_len) |
+   FIELD_PREP(XILINX_DPDMA_DESC_HSIZE_STRIDE_STRIDE_MASK, 
period_len);
+
+   hw_desc->control |= XILINX_DPDMA_DESC_CONTROL_PREEMBLE;
+   hw_desc->control |= XILINX_DPDMA_DESC_CONTROL_COMPLETE_INTR;
+   hw_desc->control |= XILINX_DPDMA_DESC_CONTROL_IGNORE_DONE;
+
+   list_add_tail(_desc->node, _desc->descriptors);
+
+   buf_addr += period_len;
+   last = sw_desc;
+   }
+
+   sw_desc = list_first_entry(_desc->descriptors,
+  struct xilinx_dpdma_sw_desc, node);
+   if (chan->xdev->ext_addr)
+   xilinx_dpdma_sw_desc_next_64(last, sw_desc);
+   else
+   xilinx_dpdma_sw_desc_next_32(last, sw_desc);
+   last->hw.control |= XILINX_DPDMA_DESC_CONTROL_LAST_OF_FRAME;
+
+   return tx_desc;
+}
+
 /* 
-
  * DPDMA Channel Operations
  */
@@ -1206,6 +1311,31 @@ xilinx_dpdma_prep_interleaved_dma(struct dma_chan *dchan,
return 

Re: [linux-yocto] [kernel-cache master] xilinx-zynqmp: enable CONFIG_COMMON_CLK_SI5341 and CONFIG_XILINX_ZYNQMP_DPDMA

2020-12-21 Thread Bruce Ashfield
merged.

Bruce

On Wed, Dec 16, 2020 at 3:34 AM  wrote:
>
> From: Quanyang Wang 
>
> Since we use si5341 as clk source, then enable CONFIG_COMMON_CLK_SI5341
> to use its driver. And in order to use mainline dpdma driver, we need
> enable CONFIG_XILINX_ZYNQMP_DPDMA.
>
> Signed-off-by: Quanyang Wang 
> ---
>  bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg 
> b/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg
> index 747ca9d5c..e37c1f73b 100644
> --- a/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg
> +++ b/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg
> @@ -124,6 +124,7 @@ CONFIG_UIO_XILINX_APM=y
>  CONFIG_COMMON_CLK=y
>  CONFIG_COMMON_CLK_SI570=y
>  CONFIG_COMMON_CLK_SI5324=y
> +CONFIG_COMMON_CLK_SI5341=y
>  CONFIG_COMMON_CLK_ZYNQMP=y
>  CONFIG_COMMON_CLK_XLNX_CLKWZRD=y
>  CONFIG_IOMMU_API=y
> @@ -207,7 +208,7 @@ CONFIG_DRM_XLNX_SDI=y
>  CONFIG_DRM_XLNX_BRIDGE_CSC=y
>  CONFIG_DRM_XLNX_BRIDGE_SCALER=y
>  CONFIG_XILINX_FRMBUF=y
> -CONFIG_XILINX_DPDMA=y
> +CONFIG_XILINX_ZYNQMP_DPDMA=y
>  CONFIG_DRM_XILINX_SDI=y
>  CONFIG_SOUND=y
>  CONFIG_SND=y
> --
> 2.25.1
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9300): 
https://lists.yoctoproject.org/g/linux-yocto/message/9300
Mute This Topic: https://lists.yoctoproject.org/mt/78996619/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: update patches for raspberrypi 4b platform

2020-12-21 Thread Bruce Ashfield
On Mon, Dec 21, 2020 at 7:34 PM Li, Meng  wrote:
>
> Hi Bruce,
>
> Sorry! I forgot to push patches into my repo.
> I pushed them just now.

No worries! I do the same thing (more often than I'd like to admit!).

This is now merged.

Bruce

>
> Thanks,
> Limeng
>
> > -Original Message-
> > From: Bruce Ashfield 
> > Sent: Tuesday, December 22, 2020 6:07 AM
> > To: Li, Meng 
> > Cc: Linux Yocto 
> > Subject: Re: [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: 
> > bcm-2xxx-rpi:
> > update patches for raspberrypi 4b platform
> >
> > On Mon, Dec 21, 2020 at 5:20 AM  wrote:
> > >
> > > From: Limeng 
> > >
> > > Hi Bruce,
> > >
> > > I get some latest patches from raspberry pi git repo
> > > https://github.com/raspberrypi/linux.git rpi-5.10.y, and intend to merge
> > them into linux-yocto-dev.
> > >
> > > There are 39 patches in my public repo
> > > https://github.com/limeng-linux/linux-yocto-develop.git, branch
> > standard/bcm-2xxx-rpi Could you please help merge these patches into
> > linux-ycoto-dev kernel, v5.10, branch is standard/bcm-2xxx-rpi?
> > >
> >
> > Can you double check this ? When I fetched the branch and merged it, I'm
> > seeing no new changes.
> >
> > Bruce
> >
> > > diffstat info as below.
> > >
> > >  Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml
> > |1
> > >  arch/arm/boot/dts/bcm2711-rpi-cm4.dts
> > > |2
> > >  arch/arm/boot/dts/bcm2711.dtsi   
> > > |1
> > >  arch/arm/boot/dts/overlays/Makefile  
> > > |1
> > >  arch/arm/boot/dts/overlays/README
> > > |   19
> > >  arch/arm/boot/dts/overlays/ads1015-overlay.dts   
> > > |2
> > >  arch/arm/boot/dts/overlays/ads1115-overlay.dts   
> > > |2
> > >  arch/arm/boot/dts/overlays/allo-boss2-dac-audio-overlay.dts  
> > > |   57
> > >  arch/arm/boot/dts/overlays/allo-piano-dac-plus-pcm512x-audio-
> > overlay.dts |2
> > >  arch/arm/boot/dts/overlays/i2c-rtc-overlay.dts   
> > > |   98
> > >  arch/arm/boot/dts/overlays/mpu6050-overlay.dts   
> > > |1
> > >  arch/arm/configs/bcm2709_defconfig   
> > > |7
> > >  arch/arm/configs/bcm2711_defconfig   
> > > |7
> > >  arch/arm/configs/bcmrpi_defconfig
> > > |7
> > >  arch/arm64/configs/bcm2711_defconfig 
> > > |5
> > >  arch/arm64/configs/bcmrpi3_defconfig 
> > > |5
> > >  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > > |
> > 14
> > >  drivers/gpu/drm/arm/display/komeda/komeda_crtc.c 
> > > |   14
> > >  drivers/gpu/drm/arm/hdlcd_crtc.c 
> > > |2
> > >  drivers/gpu/drm/arm/malidp_crtc.c
> > > |   20
> > >  drivers/gpu/drm/armada/armada_crtc.c 
> > > |   14
> > >  drivers/gpu/drm/ast/ast_mode.c   
> > > |   12
> > >  drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c   
> > > |7
> > >  drivers/gpu/drm/drm_atomic_helper.c  
> > > |   10
> > >  drivers/gpu/drm/drm_simple_kms_helper.c  
> > > |   10
> > >  drivers/gpu/drm/exynos/exynos_drm_crtc.c 
> > > |   12
> > >  drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c   
> > > |2
> > >  drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c   
> > > |4
> > >  drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c  
> > > |4
> > >  drivers/gpu/drm/imx/dcss/dcss-crtc.c 
> > > |4
> > >  drivers/gpu/drm/imx/ipuv3-crtc.c 
> > > |   10
> > >  drivers/gpu/drm/ingenic/ingenic-drm-drv.c
> > > |   29
> > >  drivers/gpu/drm/mediatek/mtk_drm_crtc.c  
> > > |   16
> > >  drivers/gpu/drm/meson/meson_crtc.c   
> > > |4
> > >  drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c 
> > > |   27
> > >  drivers/gpu/drm/msm/disp/mdp4/mdp4_crtc.c
> > > |6
> > >  drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c
> > > |   17
> > >  drivers/gpu/drm/mxsfb/mxsfb_kms.c
> > > |   12
> > >  drivers/gpu/drm/nouveau/dispnv50/head.c  
> > > |7
> > >  drivers/gpu/drm/omapdrm/omap_crtc.c  
> > > |   17
> > >  

Re: [linux-yocto][linux-yocto-dev cn96xx] Bump marvell-cn96xx linux-yocto-dev to v5.10

2020-12-21 Thread Kevin Hao
On Mon, Dec 21, 2020 at 05:04:57PM -0500, Bruce Ashfield wrote:
> On Thu, Dec 17, 2020 at 9:12 PM Ruiqiang Hao  
> wrote:
> >
> > Hi Bruce,
> >
> > Please help to merge follow kernel code into our marvell-cn96xx repo.
> >
> > repo:
> > linux-yocto-dev
> > branch:
> > standard/cn96xx
> >
> 
> merged.

I can't find the standard/cn96xx in the linux-yocto-dev repo. Did I miss 
something?

Thanks,
Kevin


signature.asc
Description: PGP signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9295): 
https://lists.yoctoproject.org/g/linux-yocto/message/9295
Mute This Topic: https://lists.yoctoproject.org/mt/79053257/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] M+ & H bugs with Milestone Movements WW51

2020-12-21 Thread Stephen Jolley
All,

YP M+ or high bugs which moved to a new milestone in WW51 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  5322

Global DNS fallback mechanism not present in poky distro

kai.k...@windriver.com

kai.k...@windriver.com

3.3 M1

3.3 M2


 

  11385

poky-container: clarify that meta-data should be checked out using native tools 
that run the host and not with tools in container

timothy.t.orl...@intel.com

timothy.t.orl...@intel.com

3.3 M1

3.3 M2


 

  12060

It is possible to specify a PACKAGE and a PKG_ rename that conflict

kai.k...@windriver.com

kai.k...@windriver.com

3.3 M1

3.3 M2


 

  12342

lib32-core-image-sato -ctestimage failed due to wrong package names

kai.k...@windriver.com

kai.k...@windriver.com

3.3 M1

3.3 M2


 

  12917

Warnings from nightly-multilib builds (build-deps)

kai.k...@windriver.com

kai.k...@windriver.com

3.3 M1

3.3 M2


 

  13008

toaster testing

david.re...@windriver.com

david.re...@windriver.com

3.3 M1

3.3 M3


 

  13109

Implement CPE to package to Release mapping

david.re...@windriver.com

david.re...@windriver.com

3.3 M1

3.3 M3


 

  13103

[Bug][QA 2.7 M1 rc1][Toaster] "Recipes" table  and  "machines" table are not 
getting populated after clicking on imported layer as well as after clicking 
Machines Tab on project page

david.re...@windriver.com

david.re...@windriver.com

3.3 M1

3.3 M2


 

  13182

Inconsistency detected by ld.so: dl-open.c: 274: dl_open_worker: Assertion xxx 
failed

qi.c...@windriver.com

qi.c...@windriver.com

3.3 M1

3.3 M3


 

  13311

xargs: fdleak.c:396: complain_about_leaky_fds: Assertion `no_leaks' failed.

randy.macl...@windriver.com

mingli...@windriver.com

3.4

3.3 M3


 

  13411

ptest-perl.bbclass run-ptest is too greedy for SKIP

timothy.t.orl...@intel.com

timothy.t.orl...@intel.com

3.3 M1

3.3 M2


 

  13425

Add bblock and bbunlock helper tools

randy.macl...@windriver.com

newco...@yoctoproject.org

3.3 M1

3.3 M2


 

  13674

master dnf failures on qemumips

randy.macl...@windriver.com

mingli...@windriver.com

3.4

3.3 M3


 

  13690

runqemu with slirp, forwarded host ports are not available on host

timothy.t.orl...@intel.com

timothy.t.orl...@intel.com

3.3 M1

3.3 M2


 

  13722

Debugging With the GNU Project Debugger enhancements

randy.macl...@windriver.com

newco...@yoctoproject.org

3.3 M1

3.3 M2


 

  13768

base-files do_package fatal error in subprocess

randy.macl...@windriver.com

mingli...@windriver.com

3.4

3.3 M2


 

  13930

Port the CROPS toaster-container selenium tests to the Autobuilder

timothy.t.orl...@intel.com

timothy.t.orl...@intel.com

3.3 M1

3.3 M2


 

  13934

Apparent duplication of libtirpc package causes failure in "bitbake linux-yocto 
-c menuconfig"

hongxu@windriver.com

hongxu@windriver.com

3.1.5

3.3 M4


 

  13938

devtool modify virtual/kernel fails when EXTRAVERSION field is empty in Makefile

timothy.t.orl...@intel.com

timothy.t.orl...@intel.com

3.3 M1

3.3 M2


 

  14020

environment-setup script in multilib eSDK doesn't work for multilib variant

liezhi.y...@windriver.com

liezhi.y...@windriver.com

3.3 M1

3.3 M2


 

  14026

documentation how to use systemd is inconsistent

randy.macl...@windriver.com

mark.mor...@windriver.com

3.3 M1

3.3 M2


 

  14051

[QA 3.2 M3 RC1] failure in ptest : valgrind.drd and valgrind.helgrind

randy.macl...@windriver.com

anuj.mit...@intel.com

3.3 M1

3.3 M2


 

  14085

Toaster UI should know when bitbake crashed

david.re...@windriver.com

david.re...@windriver.com

3.3 M1

3.3 M2


 

  14098


[yocto] Enhancements/Bugs closed WW51!

2020-12-21 Thread Stephen Jolley
All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


mhalst...@linuxfoundation.org

3


richard.pur...@linuxfoundation.org

1


jay.shen.t...@intel.com

1


Grand Total

5

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51824): https://lists.yoctoproject.org/g/yocto/message/51824
Mute This Topic: https://lists.yoctoproject.org/mt/79139845/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Current high bug count owners for Yocto Project 3.3

2020-12-21 Thread Stephen Jolley
All,

Below is the list as of top 47 bug owners as of the end of WW51 of who have
open medium or higher bugs and enhancements against YP 3.3.   There are 98
possible work days left until the final release candidates for YP 3.3 needs
to be released.


Who

Count


richard.pur...@linuxfoundation.org

36


r...@burtonini.com

27


david.re...@windriver.com

21


bluelightn...@bluelightning.org

19


bruce.ashfi...@gmail.com

14


timothy.t.orl...@intel.com

12


mark.mor...@windriver.com

11


jpewhac...@gmail.com

11


kai.k...@windriver.com

10


sakib.sa...@windriver.com

10


akuster...@gmail.com

10


trevor.gamb...@windriver.com

9


qi.c...@windriver.com

6


hongxu@windriver.com

4


raj.k...@gmail.com

4


idad...@gmail.com

4


randy.macl...@windriver.com

4


yi.z...@windriver.com

4


mingli...@windriver.com

4


mostthings...@gmail.com

3


chee.yang@intel.com

3


alejan...@enedino.org

3


jon.ma...@arm.com

2


matthew...@posteo.net

2


jeanmarie.lemeta...@gmail.com

2


pokyli...@reliableembeddedsystems.com

2


saul.w...@windriver.com

2


anuj.mit...@intel.com

2


ydir...@free.fr

2


jae...@xilinx.com

2


matt.ranos...@konsulko.com

1


apoorvsan...@gmail.com

1


joe.sla...@windriver.com

1


akus...@mvista.com

1


mhalst...@linuxfoundation.org

1


kexin@windriver.com

1


aeh...@gmail.com

1


dl...@gmx.de

1


kerg...@gmail.com

1


liezhi.y...@windriver.com

1


mark.ha...@kernel.crashing.org

1


maxime.roussinbelan...@gmail.com

1


shac...@vdoo.com

1


martin.ja...@gmail.com

1


kamen...@cisco.com

1


Grand Total

260

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51823): https://lists.yoctoproject.org/g/yocto/message/51823
Mute This Topic: https://lists.yoctoproject.org/mt/79139613/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: update patches for raspberrypi 4b platform

2020-12-21 Thread Meng Li
Hi Bruce,

Sorry! I forgot to push patches into my repo.
I pushed them just now.

Thanks,
Limeng

> -Original Message-
> From: Bruce Ashfield 
> Sent: Tuesday, December 22, 2020 6:07 AM
> To: Li, Meng 
> Cc: Linux Yocto 
> Subject: Re: [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: bcm-2xxx-rpi:
> update patches for raspberrypi 4b platform
> 
> On Mon, Dec 21, 2020 at 5:20 AM  wrote:
> >
> > From: Limeng 
> >
> > Hi Bruce,
> >
> > I get some latest patches from raspberry pi git repo
> > https://github.com/raspberrypi/linux.git rpi-5.10.y, and intend to merge
> them into linux-yocto-dev.
> >
> > There are 39 patches in my public repo
> > https://github.com/limeng-linux/linux-yocto-develop.git, branch
> standard/bcm-2xxx-rpi Could you please help merge these patches into
> linux-ycoto-dev kernel, v5.10, branch is standard/bcm-2xxx-rpi?
> >
> 
> Can you double check this ? When I fetched the branch and merged it, I'm
> seeing no new changes.
> 
> Bruce
> 
> > diffstat info as below.
> >
> >  Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml
> |1
> >  arch/arm/boot/dts/bcm2711-rpi-cm4.dts| 
> >2
> >  arch/arm/boot/dts/bcm2711.dtsi   | 
> >1
> >  arch/arm/boot/dts/overlays/Makefile  | 
> >1
> >  arch/arm/boot/dts/overlays/README| 
> >   19
> >  arch/arm/boot/dts/overlays/ads1015-overlay.dts   | 
> >2
> >  arch/arm/boot/dts/overlays/ads1115-overlay.dts   | 
> >2
> >  arch/arm/boot/dts/overlays/allo-boss2-dac-audio-overlay.dts  | 
> >   57
> >  arch/arm/boot/dts/overlays/allo-piano-dac-plus-pcm512x-audio-
> overlay.dts |2
> >  arch/arm/boot/dts/overlays/i2c-rtc-overlay.dts   | 
> >   98
> >  arch/arm/boot/dts/overlays/mpu6050-overlay.dts   | 
> >1
> >  arch/arm/configs/bcm2709_defconfig   | 
> >7
> >  arch/arm/configs/bcm2711_defconfig   | 
> >7
> >  arch/arm/configs/bcmrpi_defconfig| 
> >7
> >  arch/arm64/configs/bcm2711_defconfig | 
> >5
> >  arch/arm64/configs/bcmrpi3_defconfig | 
> >5
> >  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c|
> 14
> >  drivers/gpu/drm/arm/display/komeda/komeda_crtc.c | 
> >   14
> >  drivers/gpu/drm/arm/hdlcd_crtc.c | 
> >2
> >  drivers/gpu/drm/arm/malidp_crtc.c| 
> >   20
> >  drivers/gpu/drm/armada/armada_crtc.c | 
> >   14
> >  drivers/gpu/drm/ast/ast_mode.c   | 
> >   12
> >  drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c   | 
> >7
> >  drivers/gpu/drm/drm_atomic_helper.c  | 
> >   10
> >  drivers/gpu/drm/drm_simple_kms_helper.c  | 
> >   10
> >  drivers/gpu/drm/exynos/exynos_drm_crtc.c | 
> >   12
> >  drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c   | 
> >2
> >  drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c   | 
> >4
> >  drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c  | 
> >4
> >  drivers/gpu/drm/imx/dcss/dcss-crtc.c | 
> >4
> >  drivers/gpu/drm/imx/ipuv3-crtc.c | 
> >   10
> >  drivers/gpu/drm/ingenic/ingenic-drm-drv.c| 
> >   29
> >  drivers/gpu/drm/mediatek/mtk_drm_crtc.c  | 
> >   16
> >  drivers/gpu/drm/meson/meson_crtc.c   | 
> >4
> >  drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 
> >   27
> >  drivers/gpu/drm/msm/disp/mdp4/mdp4_crtc.c| 
> >6
> >  drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c| 
> >   17
> >  drivers/gpu/drm/mxsfb/mxsfb_kms.c| 
> >   12
> >  drivers/gpu/drm/nouveau/dispnv50/head.c  | 
> >7
> >  drivers/gpu/drm/omapdrm/omap_crtc.c  | 
> >   17
> >  drivers/gpu/drm/qxl/qxl_display.c| 
> >2
> >  drivers/gpu/drm/rcar-du/rcar_du_crtc.c   | 
> >   15
> >  drivers/gpu/drm/rockchip/rockchip_drm_vop.c  | 
> >   12
> >  drivers/gpu/drm/sti/sti_crtc.c   | 
> >2
> >  drivers/gpu/drm/stm/ltdc.c   

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2020-12-21 Thread Stephen Jolley
All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 338
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.2", "3.3, "3.99" and "Future", the more pressing/urgent issues
being in "3.2" and then "3.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51822): https://lists.yoctoproject.org/g/yocto/message/51822
Mute This Topic: https://lists.yoctoproject.org/mt/79139599/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][linux-yocto v5.4/standard/nxp-imx8][PATCH] i2c: imx: fix a build error when compiling i2c-imx

2020-12-21 Thread Bruce Ashfield

merged.

Bruce

In message: [linux-yocto][linux-yocto v5.4/standard/nxp-imx8][PATCH] i2c: imx: 
fix a build error when compiling i2c-imx
on 18/12/2020 Xiaolei Wang wrote:

> i2c_imx_clear_ir did not join in the merge conflict, so use
> i2c_imx_clr_al_bit function instead
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  drivers/i2c/busses/i2c-imx.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
> index 16b741251055..8a215a5ccb38 100644
> --- a/drivers/i2c/busses/i2c-imx.c
> +++ b/drivers/i2c/busses/i2c-imx.c
> @@ -550,6 +550,7 @@ static int i2c_imx_bus_busy(struct imx_i2c_struct 
> *i2c_imx, int for_busy)
>  
>  static int i2c_imx_trx_complete(struct imx_i2c_struct *i2c_imx)
>  {
> + unsigned int temp;
>   wait_event_timeout(i2c_imx->queue, i2c_imx->i2csr & I2SR_IIF, HZ / 10);
>  
>   if (unlikely(!(i2c_imx->i2csr & I2SR_IIF))) {
> @@ -560,7 +561,8 @@ static int i2c_imx_trx_complete(struct imx_i2c_struct 
> *i2c_imx)
>   /* check for arbitration lost */
>   if (i2c_imx->i2csr & I2SR_IAL) {
>   dev_dbg(_imx->adapter.dev, "<%s> Arbitration lost\n", 
> __func__);
> - i2c_imx_clear_irq(i2c_imx, I2SR_IAL);
> + temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2SR);
> + i2c_imx_clr_al_bit(temp, i2c_imx);
>  
>   i2c_imx->i2csr = 0;
>   return -EAGAIN;
> -- 
> 2.25.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9292): 
https://lists.yoctoproject.org/g/linux-yocto/message/9292
Mute This Topic: https://lists.yoctoproject.org/mt/79053384/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][linux-yocto-dev cn96xx] Bump marvell-cn96xx linux-yocto-dev to v5.10

2020-12-21 Thread Bruce Ashfield
On Thu, Dec 17, 2020 at 9:12 PM Ruiqiang Hao  wrote:
>
> Hi Bruce,
>
> Please help to merge follow kernel code into our marvell-cn96xx repo.
>
> repo:
> linux-yocto-dev
> branch:
> standard/cn96xx
>

merged.

Bruce

> Thanks,
> Ruiqiang
>
> The following changes since commit 0477e92881850d44910a7e94fc2c46f96faa131f:
>
>   Linux 5.10-rc7 (2020-12-06 14:25:12 -0800)
>
> are available in the Git repository at:
>
>   https://github.com/cythe/linux.git marvell-cn96xx_v5.10-rc7
>
> for you to fetch changes up to b412d1001ca7bb306d226cfda0d3a2cf55f4dd85:
>
>   driver: net: marvell: Fixed warning caused by inconsistent const attribute 
> (2020-12-18 10:01:25 +0800)
>
> 
> Aaron Williams (3):
>   octeontx2: mmc: Add tuning support for HS400 mode
>   mmc: octeontx2: Use flags for hardware differences
>   mmc: octeontx2: fix handling calibration glitch
>
> Alex Belits (2):
>   arm64: Add support for ASID locking
>   kernel/exit.c: Add task cleanup callbacks
>
> Andrew Pinski (3):
>   arm64: Add MIDR encoding for some Marvell OcteonTX 2.
>   arm64: Add workaround for Cavium erratum 36890
>   arm64: Add workaround for Marvell erratum 37119
>
> Angela Czubak (2):
>   octeontx2-af: fix rvu_sso_ggrp_taq_flush
>   octeontx2-af: fix cgx_lmac_rx_tx_enable
>
> Bharat Bhushan (4):
>   dt-bindings: perf: arm-smmuv3-pmu: Add documentation for arm-smmuv3 pmu
>   perf/smmuv3: Add device tree support
>   perf/smmuv3: Fix programming event type with global filtering
>   coresight: Treat ETM4.2 as ETM4.3 on OcteonTx2
>
> Chandrakala Chavva (11):
>   mmc: cavium_thunderx: Use proper register to clear interrupts
>   driver: mmc: octeontx2: Fix tuning for T96 C0
>   driver: mmc: Configure flags for T96 pass B0
>   octeontx2-serdes: Update PRBS APIs to start/stop per QLM lane
>   octeontx2-serdes: Fix parameter passed to start_prbs().
>   octeontx2-serdes: Fix prbs error reporting
>   driver: serdes_debugfs: Allow user to clear prbs errors.
>   octeontx2-serdes: Fix prbs per lane configuration
>   driver: serdes_debugfs: Add new smc call to tune serdes
>   driver: serdes_debugfs: Add new smc call for serdes loopback
>   driver: serdes_debugfs: Add inject optional parameter to prbs command
>
> Christina Jacob (18):
>   octeontx2-pf: Adding ethtool support for link status information.
>   octeontx2-af: Support to get link info like current speed, fec etc
>   octeontx2-pf: Ethtool support for fec configuration
>   octeontx2-af: Move to rvu_fwdata version 1.
>   octeontx2-pf: Add ethtool -m option support.
>   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-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
>   octeontx2-pf: Disply the link detected status in ethtool command
>   net: thunderx: Do a PCS reset upon SGMII link toggle
>   octeontx2-pf: remove redundant changes from speed change suppcrt.
>   octeontx-af: Interface mode change feature via ethtool
>   octeontx2-pf: Interface Mode change using ethtool.
>
> Felix Manlunas (5):
>   octeontx2-af: Add new CGX_CMDs to set and get PHY modulation type
>   octeontx2-pf: Add ethtool priv flag to control PAM4 on/off
>   octeontx2-pf: Fix wrong info in ethtool's list of supported link modes
>   octeontx2-pf: Add LIO3 link modes to ethtool's list of supported modes
>   octeontx2-af: Add new CGX_CMD to get PHY FEC statistics
>
> Geetha sowjanya (11):
>   octeontx2-af: Check SQ counters to detect the deadlock
>   octeontx2-af: Update hardware workarounds for 95xx A1 silicon
>   PCI: quirks : Apply ACS quirk for all devices
>   octeontx2-pf: Ignore NPC parser layer errors
>   iommu/arm-smmu-v3: Force 32 byte command queue memory reads
>   octeontx2-af: Fix return value in npc_set_pkind
>   octeontx2-af: Update HW workarounds for 96xx C0, 98xx and F95xx B0 chips
>   octeontx2-pf: Set SMQ MAXLEN to max hardware supported value
>   octeontx2-af: Update NIX_TXSCHQ_CONFIG mbox to handle read request
>   octeontx2-af: Disable SMQ sticky mode to avoid NIX PSE deadlock
>   octeontx2-pf: Fix interface down flag on error
>
> George Cherian (2):
>   PCI: Add pci_iounmap
>   octeontx2-af: Add support for RSS hashing based on Transport protocol 
> field
>
> Hao Zheng (2):
>   octeontx2-af: Turn on L2 

Re: [linux-yocto] [kernel-cache master] xilinx-zynqmp: enable CONFIG_COMMON_CLK_SI5341 and CONFIG_XILINX_ZYNQMP_DPDMA

2020-12-21 Thread Bruce Ashfield
This looks ok to me, but I'll wait for the v3 of the BSP branch
changes before doing the merge.

Bruce

On Wed, Dec 16, 2020 at 3:34 AM  wrote:
>
> From: Quanyang Wang 
>
> Since we use si5341 as clk source, then enable CONFIG_COMMON_CLK_SI5341
> to use its driver. And in order to use mainline dpdma driver, we need
> enable CONFIG_XILINX_ZYNQMP_DPDMA.
>
> Signed-off-by: Quanyang Wang 
> ---
>  bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg 
> b/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg
> index 747ca9d5c..e37c1f73b 100644
> --- a/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg
> +++ b/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg
> @@ -124,6 +124,7 @@ CONFIG_UIO_XILINX_APM=y
>  CONFIG_COMMON_CLK=y
>  CONFIG_COMMON_CLK_SI570=y
>  CONFIG_COMMON_CLK_SI5324=y
> +CONFIG_COMMON_CLK_SI5341=y
>  CONFIG_COMMON_CLK_ZYNQMP=y
>  CONFIG_COMMON_CLK_XLNX_CLKWZRD=y
>  CONFIG_IOMMU_API=y
> @@ -207,7 +208,7 @@ CONFIG_DRM_XLNX_SDI=y
>  CONFIG_DRM_XLNX_BRIDGE_CSC=y
>  CONFIG_DRM_XLNX_BRIDGE_SCALER=y
>  CONFIG_XILINX_FRMBUF=y
> -CONFIG_XILINX_DPDMA=y
> +CONFIG_XILINX_ZYNQMP_DPDMA=y
>  CONFIG_DRM_XILINX_SDI=y
>  CONFIG_SOUND=y
>  CONFIG_SND=y
> --
> 2.25.1
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9289): 
https://lists.yoctoproject.org/g/linux-yocto/message/9289
Mute This Topic: https://lists.yoctoproject.org/mt/78996619/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto] [linux-yocto-dev standard/xlnx-soc][PATCH 1/1] dmaengine: xilinx: dpdma: add dma cyclic mode

2020-12-21 Thread Bruce Ashfield
Can you resubmit this along with the v3 core set of changes.

Or include it in that branch, either is fine with me, just mention it
in the summary if it is included.

Bruce

On Wed, Dec 16, 2020 at 3:55 AM  wrote:
>
> From: Quanyang Wang 
>
> The dma cyclic mode is required by DP audio, so add it to make DP audio
> work.
>
> Reference: b78c51347044 ("dma: xilinx: dpdma: Add the Xilinx DisplayPort DMA 
> engine driver") from https://github.com/Xilinx/linux-xlnx.git
> Signed-off-by: Quanyang Wang 
> ---
>  drivers/dma/xilinx/xilinx_dpdma.c | 131 ++
>  1 file changed, 131 insertions(+)
>
> diff --git a/drivers/dma/xilinx/xilinx_dpdma.c 
> b/drivers/dma/xilinx/xilinx_dpdma.c
> index 55df63dead8d..580cd6b8cea3 100644
> --- a/drivers/dma/xilinx/xilinx_dpdma.c
> +++ b/drivers/dma/xilinx/xilinx_dpdma.c
> @@ -499,6 +499,39 @@ static inline void dpdma_set(void __iomem *base, u32 
> offset, u32 set)
>   * Descriptor Operations
>   */
>
> +/**
> + * xilinx_dpdma_sw_desc_next_32 - Set 32 bit address of a next sw descriptor
> + * @sw_desc: current software descriptor
> + * @next: next descriptor
> + *
> + * Update the current sw descriptor @sw_desc with 32 bit address of the next
> + * descriptor @next.
> + */
> +static inline void
> +xilinx_dpdma_sw_desc_next_32(struct xilinx_dpdma_sw_desc *sw_desc,
> +struct xilinx_dpdma_sw_desc *next)
> +{
> +   sw_desc->hw.next_desc = next->dma_addr;
> +}
> +
> +/**
> + * xilinx_dpdma_sw_desc_next_64 - Set 64 bit address of a next sw descriptor
> + * @sw_desc: current software descriptor
> + * @next: next descriptor
> + *
> + * Update the current sw descriptor @sw_desc with 64 bit address of the next
> + * descriptor @next.
> + */
> +static inline void
> +xilinx_dpdma_sw_desc_next_64(struct xilinx_dpdma_sw_desc *sw_desc,
> +struct xilinx_dpdma_sw_desc *next)
> +{
> +   sw_desc->hw.next_desc = lower_32_bits(next->dma_addr);
> +   sw_desc->hw.addr_ext |= upper_32_bits(next->dma_addr) &
> +   XILINX_DPDMA_DESC_ADDR_EXT_NEXT_ADDR_MASK;
> +}
> +
> +
>  /**
>   * xilinx_dpdma_sw_desc_set_dma_addrs - Set DMA addresses in the descriptor
>   * @xdev: DPDMA device
> @@ -737,6 +770,77 @@ xilinx_dpdma_chan_prep_interleaved_dma(struct 
> xilinx_dpdma_chan *chan,
> return tx_desc;
>  }
>
> +/**
> + * xilinx_dpdma_chan_prep_cyclic_dma - Prepare a cyclic dma
> + * descriptor
> + * @chan: DPDMA channel
> + * @buf_addr: buffer address
> + * @buf_len: buffer length
> + * @period_len: number of periods
> + *
> + * Prepare a tx descriptor including internal software/hardware descriptors
> + * for the given cyclic transaction.
> + *
> + * Return: A DPDMA TX descriptor on success, or NULL.
> + */
> +static struct xilinx_dpdma_tx_desc *
> +xilinx_dpdma_chan_prep_cyclic_dma(struct xilinx_dpdma_chan *chan,
> + dma_addr_t buf_addr, size_t buf_len,
> + size_t period_len)
> +{
> +   struct xilinx_dpdma_tx_desc *tx_desc;
> +   struct xilinx_dpdma_sw_desc *sw_desc, *last = NULL;
> +   unsigned int periods = buf_len / period_len;
> +   unsigned int i;
> +
> +   tx_desc = xilinx_dpdma_chan_alloc_tx_desc(chan);
> +   if (!tx_desc)
> +   return NULL;
> +
> +   for (i = 0; i < periods; i++) {
> +   struct xilinx_dpdma_hw_desc *hw_desc;
> +
> +   if (!IS_ALIGNED(buf_addr, XILINX_DPDMA_ALIGN_BYTES)) {
> +   dev_err(chan->xdev->dev, "buffer should be aligned at 
> %d B\n",
> +   XILINX_DPDMA_ALIGN_BYTES);
> +   return NULL;
> +   }
> +
> +   sw_desc = xilinx_dpdma_chan_alloc_sw_desc(chan);
> +   if (!sw_desc) {
> +   xilinx_dpdma_chan_free_tx_desc(_desc->vdesc);
> +   return NULL;
> +   }
> +
> +   xilinx_dpdma_sw_desc_set_dma_addrs(chan->xdev, sw_desc, last,
> +   _addr, 1);
> +   hw_desc = _desc->hw;
> +   hw_desc->xfer_size = period_len;
> +   hw_desc->hsize_stride =
> +   FIELD_PREP(XILINX_DPDMA_DESC_HSIZE_STRIDE_HSIZE_MASK, 
> period_len) |
> +   FIELD_PREP(XILINX_DPDMA_DESC_HSIZE_STRIDE_STRIDE_MASK, 
> period_len);
> +
> +   hw_desc->control |= XILINX_DPDMA_DESC_CONTROL_PREEMBLE;
> +   hw_desc->control |= XILINX_DPDMA_DESC_CONTROL_COMPLETE_INTR;
> +   hw_desc->control |= XILINX_DPDMA_DESC_CONTROL_IGNORE_DONE;
> +
> +   list_add_tail(_desc->node, _desc->descriptors);
> +
> +   buf_addr += period_len;
> +   last = sw_desc;
> +   }
> +
> +   sw_desc = list_first_entry(_desc->descriptors,
> +  struct xilinx_dpdma_sw_desc, node);
> +   if 

[yocto] [auh][PATCH] upgrade-helper.py: handle unassigned recipes correctly

2020-12-21 Thread Alexander Kanavin
Attempting to send to unassig...@yoctoproject.org bounces immediately,
which means the CC recipients (such as oe-core list) won't get the email
either.

Instead, send to cc directly.

Signed-off-by: Alexander Kanavin 
---
 upgrade-helper.py | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/upgrade-helper.py b/upgrade-helper.py
index 7ed7af4..eb3935e 100755
--- a/upgrade-helper.py
+++ b/upgrade-helper.py
@@ -320,7 +320,10 @@ class Updater(object):
 
 cc_addr = None
 if "cc_recipients" in settings:
-cc_addr = settings["cc_recipients"].split()
+if 'unassigned' in to_addr:
+to_addr = settings["cc_recipients"].split()
+else:
+cc_addr = settings["cc_recipients"].split()
 
 newversion = pkg_ctx['NPV'] if not 
pkg_ctx['NPV'].endswith("new-commits-available") else pkg_ctx['NSRCREV']
 subject = "[AUH] " + pkg_ctx['PN'] + ": upgrading to " + newversion
-- 
2.29.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51821): https://lists.yoctoproject.org/g/yocto/message/51821
Mute This Topic: https://lists.yoctoproject.org/mt/79133842/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] hostapd_free_hapd_data: Interface wlan0 wasn't started #dunfell #linux #kernel

2020-12-21 Thread Shamil Khan
Hi VR,

Please make sure that the interface name in hostapd.conf matches with the 
wireless interface name of your target.
By default it is set to wlan0, but it could be different in your target (for 
ex, wlp2s0...).

Best regards,
Shamil

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51820): https://lists.yoctoproject.org/g/yocto/message/51820
Mute This Topic: https://lists.yoctoproject.org/mt/78628547/21656
Mute #linux:https://lists.yoctoproject.org/g/yocto/mutehashtag/linux
Mute #dunfell:https://lists.yoctoproject.org/g/yocto/mutehashtag/dunfell
Mute #kernel:https://lists.yoctoproject.org/g/yocto/mutehashtag/kernel
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Using U-boot in Yocto

2020-12-21 Thread Zoran
Hello Jonas,

Do not forget that you can also build and use U-Boot completely out of
a YOCTO tree.

I do things like that, not using the YOCTO U-Boot build.

(As a matter of fact, I do not use the kernel as well, only rootfs for
the testing purposes)

But it depends what and how your business/project management model
looks like, I should say.

Zoran
___

On Sun, Dec 20, 2020 at 3:10 PM Jonas Vautherin
 wrote:
>
> Oh, for some reason I had not found the docs. Thanks a lot, that looks really 
> good!
>
> On Sun, Dec 20, 2020 at 2:13 PM Paul Barker  wrote:
>>
>> On Sun, 20 Dec 2020 at 09:02, Jonas Vautherin  
>> wrote:
>> >
>> > Hello!
>> >
>> > I am new to Yocto, and hope that this is the right way to ask for help :-).
>> >
>> > I would like to have a way to flash my RPi over USB using `fastboot`, and 
>> > it seems to me that one way to do that is to enable a "fastboot mode" in 
>> > U-boot. Therefore, I am trying to use U-boot in my Yocto image.
>> >
>> > There seems to be a recipe for it, hence I just added the package to my 
>> > `-image.bb` file:
>> >
>> > ```
>> > IMAGE_INSTALL += "u-boot"
>> > ```
>> >
>> > However, I am not really used to bootloaders, and I am not sure it is 
>> > booting with it. How can I check if my system is booting with U-boot? It 
>> > does not seem like it's appearing in `dmesg` (which I presume is only 
>> > starting with the kernel). Do I need to observe that with a serial 
>> > connection to my RPi, or is there a log saved somewhere on the system?
>> >
>> > Note that my image uses `meta-raspberrypi` for MACHINE "raspberrypi4-64" 
>> > (Raspberry Pi 4 Model B).
>>
>> The IMAGE_INSTALL variable is used for packages to install into the
>> rootfs. Typically bootloaders need some special handling and simply
>> adding them to IMAGE_INSTALL either doesn't work or isn't sufficient
>> to enable booting via the chosen bootloader.
>>
>> For Raspberry Pi we made this simple by adding the RPI_USE_U_BOOT
>> variable which you can set in your distro config or in local.conf. See
>> https://meta-raspberrypi.readthedocs.io/en/latest/extra-build-config.html#boot-to-u-boot
>> for more details.
>>
>> The layer documentation for meta-raspberrypi is actually pretty good,
>> you can find it at
>> https://meta-raspberrypi.readthedocs.io/en/latest/index.html.
>>
>> Thanks,
>>
>> --
>> Paul Barker
>> Konsulko Group
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51819): https://lists.yoctoproject.org/g/yocto/message/51819
Mute This Topic: https://lists.yoctoproject.org/mt/79100324/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: update patches for raspberrypi 4b platform

2020-12-21 Thread Meng Li
From: Limeng 

Hi Bruce,

I get some latest patches from raspberry pi git repo 
https://github.com/raspberrypi/linux.git rpi-5.10.y,
and intend to merge them into linux-yocto-dev.

There are 39 patches in my public repo 
https://github.com/limeng-linux/linux-yocto-develop.git, branch 
standard/bcm-2xxx-rpi
Could you please help merge these patches into linux-ycoto-dev kernel, v5.10, 
branch is standard/bcm-2xxx-rpi?

diffstat info as below.

 Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml |
1 
 arch/arm/boot/dts/bcm2711-rpi-cm4.dts|
2 
 arch/arm/boot/dts/bcm2711.dtsi   |
1 
 arch/arm/boot/dts/overlays/Makefile  |
1 
 arch/arm/boot/dts/overlays/README|   
19 
 arch/arm/boot/dts/overlays/ads1015-overlay.dts   |
2 
 arch/arm/boot/dts/overlays/ads1115-overlay.dts   |
2 
 arch/arm/boot/dts/overlays/allo-boss2-dac-audio-overlay.dts  |   
57 
 arch/arm/boot/dts/overlays/allo-piano-dac-plus-pcm512x-audio-overlay.dts |
2 
 arch/arm/boot/dts/overlays/i2c-rtc-overlay.dts   |   
98 
 arch/arm/boot/dts/overlays/mpu6050-overlay.dts   |
1 
 arch/arm/configs/bcm2709_defconfig   |
7 
 arch/arm/configs/bcm2711_defconfig   |
7 
 arch/arm/configs/bcmrpi_defconfig|
7 
 arch/arm64/configs/bcm2711_defconfig |
5 
 arch/arm64/configs/bcmrpi3_defconfig |
5 
 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c|   
14 
 drivers/gpu/drm/arm/display/komeda/komeda_crtc.c |   
14 
 drivers/gpu/drm/arm/hdlcd_crtc.c |
2 
 drivers/gpu/drm/arm/malidp_crtc.c|   
20 
 drivers/gpu/drm/armada/armada_crtc.c |   
14 
 drivers/gpu/drm/ast/ast_mode.c   |   
12 
 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c   |
7 
 drivers/gpu/drm/drm_atomic_helper.c  |   
10 
 drivers/gpu/drm/drm_simple_kms_helper.c  |   
10 
 drivers/gpu/drm/exynos/exynos_drm_crtc.c |   
12 
 drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c   |
2 
 drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c   |
4 
 drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c  |
4 
 drivers/gpu/drm/imx/dcss/dcss-crtc.c |
4 
 drivers/gpu/drm/imx/ipuv3-crtc.c |   
10 
 drivers/gpu/drm/ingenic/ingenic-drm-drv.c|   
29 
 drivers/gpu/drm/mediatek/mtk_drm_crtc.c  |   
16 
 drivers/gpu/drm/meson/meson_crtc.c   |
4 
 drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c |   
27 
 drivers/gpu/drm/msm/disp/mdp4/mdp4_crtc.c|
6 
 drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c|   
17 
 drivers/gpu/drm/mxsfb/mxsfb_kms.c|   
12 
 drivers/gpu/drm/nouveau/dispnv50/head.c  |
7 
 drivers/gpu/drm/omapdrm/omap_crtc.c  |   
17 
 drivers/gpu/drm/qxl/qxl_display.c|
2 
 drivers/gpu/drm/rcar-du/rcar_du_crtc.c   |   
15 
 drivers/gpu/drm/rockchip/rockchip_drm_vop.c  |   
12 
 drivers/gpu/drm/sti/sti_crtc.c   |
2 
 drivers/gpu/drm/stm/ltdc.c   |
2 
 drivers/gpu/drm/sun4i/sun4i_crtc.c   |   
13 
 drivers/gpu/drm/tegra/dc.c   |   
10 
 drivers/gpu/drm/tidss/tidss_crtc.c   |   
14 
 drivers/gpu/drm/tilcdc/tilcdc_crtc.c |   
14 
 drivers/gpu/drm/vboxvideo/vbox_mode.c|
2 
 drivers/gpu/drm/vc4/vc4_crtc.c   |   
11 
 drivers/gpu/drm/vc4/vc4_drv.h|
4 
 drivers/gpu/drm/vc4/vc4_dsi.c|   
28 
 drivers/gpu/drm/vc4/vc4_firmware_kms.c   |   
13 
 drivers/gpu/drm/vc4/vc4_hdmi.c

[yocto] python scikit-learn ppackage

2020-12-21 Thread Marek Belisko
Hi,

I'm trying to add to my project python package for sciki-learn which
requires some cross compilation (using cython). I was trying to make
it but it's not straightforward as all python libs are searched in
native and not target sysroots. Is there some other way to force
python to look on target-sysroots instead of native one? I used
PYTHONPATH but it seems it's not taking effect. I was also pointed to
python tool crossenv but I'm not sure if it's the way to go. Ideas?

Thanks and regards,

marek

-- 
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51818): https://lists.yoctoproject.org/g/yocto/message/51818
Mute This Topic: https://lists.yoctoproject.org/mt/79121724/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-