This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045386

Title:
  Add ODM driver gpio-m058ssan

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released

Bug description:
  From accccb1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti <filippo.cope...@eurotech.com>
  Date: Mon, 4 Dec 2023 14:45:07 +0100
  Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver

  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386

  [ Impact ]
  gpio-m058ssan driver needed for ODM partner

  [ Test Plan ]

  Connect the loopback GPIO connector to the ReliaCOR-40-13 system and
  connect the power supply of the GPIO connector.

  insert the "m058ssan" module:
  modprobe m058ssan

  create GPIOchip:
  echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device

  get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs ,
  the latter 8 are GPIs.

  Set and reset all of the GPOs one at a time and check that the
  corresponding GPI is set and reset accordingly.

  [ Where problems could occur ]

  Make sure that the power supply of the GPIO connector is correctly connected, 
otherwise the GPI will always report 0.
  Events could occur on the i2c bus communication that may cause miss-behavior 
of the driver.

  [ Other Info ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045386/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to