On 2023/5/17 12:28, Kevin Hao via lists.yoctoproject.org wrote:
On Wed, May 17, 2023 at 08:55:19AM +0800, Xulin Sun via lists.yoctoproject.org 
wrote:
Xulin Sun (11):
       media: platform: vxe-vxd: align with ti-linux-5.10.y branch
Aren't all the patches based on the ti-linux-5.10.y now?

Yes, all the patches are based on the ti-linux-5.10.y since TI's v6.1 kernel version is not released yet.


       Revert "net: ethernet: ti: am65-cpsw-switchdev: adjust to 5.10"
       net: update the AF_MAX value to the latest
We should fold this fix into the SDK patch which introduce this issue.

Ok, I will do this.


       PCI: j721e: disable retrain Link for Gen2 training
       net: ethernet: ti: j721e-cpsw-virt-mac: add the check whether it's own
device
       Revert "media: ti-vpe: cal: add multiplexed streams support"
       Revert "v4l: subdev: add routing & stream config to v4l2_subdev_state"
       Revert "v4l: subdev: Add [GS]_ROUTING subdev ioctls and operations"
       i2c: core: correct the wrong exit path in function
'i2c_new_client_device'
       arm64: dts: ti: k3-j784s4-evm: enable RNG feature
       drm/bridge: ti-sn65dsi86: correct wrong macro and undeclared variable
We should fold this fix into the SDK patch which introduce this issue.
Ok, I will do this.

For the revert patches, could we just delete them directly?

I will drop the "v4l: subdev: add routing & stream config to v4l2_subdev_state".  Left others two revert commits to avoid

subsequent series of patches will also have to be modified accordingly.


  net/Kconfig |     1 +
  net/Makefile |     1 +
  net/core/dev_ioctl.c |     7 +
  net/core/skbuff.c |     8 +
  net/core/sock.c |    16 +-
  net/ethtool/common.c |     1 +
  net/ethtool/ioctl.c |     3 +-
The changes for these net core files seem suspicious, some of the patches are 
even
marked as HACK. Do we really need them?
TI adds new rpmsg sockets and protocol family - remote-processor messaging sockets. This rpmsg protocol driver

provides the necessary support to expose a rpmsg communication channel through the socket API to userspace under

the AF_RPMSG address family.


  net/hsr/Makefile |     1 +
  net/hsr/hsr_debugfs.c |   107 +-
  net/hsr/hsr_device.c |   459 +-
  net/hsr/hsr_device.h |     5 +-
  net/hsr/hsr_forward.c |   331 +-
  net/hsr/hsr_framereg.h |     4 +
  net/hsr/hsr_main.h |   100 +-
  net/hsr/hsr_netlink.c |    39 +-
  net/hsr/hsr_proc.c |   673 ++
  net/hsr/hsr_slave.c |    23 +-
Which component will depend on these changes?
The component is "CONFIG_PROC_FS" for snmp agent interface.

  net/rpmsg/Kconfig |    19 +
  net/rpmsg/Makefile |     2 +
  net/rpmsg/rpmsg_proto.c |   745 ++
  net/socket.c |    28 +
Are there userspace applications to use this new protocol?
TI adds RPMSG_PROTO (RPMsg Sockets over virtio-rpmsg transport) to design to work

with the TI IPC stack on various available TI SoCs, currently the kernel option is enabled on the BSP for the demo "Vision Apps" to use.

Thanks

Xulin


Thanks,
Kevin



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

Reply via email to