date:20201221

[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-12-21 Thread Robin Windey

@Piotr Tomaszewski (nfm886) can confirm my touchpad is the MSFT0001:00
06CB:7F28. I booted kernel 5.10.1 into recovery and then resumed regular
boot and my touchpad works.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-12-21 Thread wangjun

all the changes are extract from the master branch of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git .

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-12-21 Thread wangjun

on fedora 33,with kernel 5.10.2 , i use this patch ,then touchpad work!



diff -Narup a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
--- a/drivers/gpio/gpiolib-acpi.c   2020-12-14 06:41:30.0 +0800
+++ b/drivers/gpio/gpiolib-acpi.c   2020-12-22 14:31:53.078877803 +0800
@@ -205,6 +205,68 @@ static void acpi_gpiochip_request_irqs(s
acpi_gpiochip_request_irq(acpi_gpio, event);
 }
 
+static enum gpiod_flags
+acpi_gpio_to_gpiod_flags(const struct acpi_resource_gpio *agpio, int polarity)
+{
+   /* GpioInt() implies input configuration */
+   if (agpio->connection_type == ACPI_RESOURCE_GPIO_TYPE_INT)
+   return GPIOD_IN;
+
+   switch (agpio->io_restriction) {
+   case ACPI_IO_RESTRICT_INPUT:
+   return GPIOD_IN;
+   case ACPI_IO_RESTRICT_OUTPUT:
+   /*
+* ACPI GPIO resources don't contain an initial value for the
+* GPIO. Therefore we deduce that value from the pull field
+* and the polarity instead. If the pin is pulled up we assume
+* default to be high, if it is pulled down we assume default
+* to be low, otherwise we leave pin untouched. For active low
+* polarity values will be switched. See also
+* Documentation/firmware-guide/acpi/gpio-properties.rst.
+*/
+   switch (agpio->pin_config) {
+   case ACPI_PIN_CONFIG_PULLUP:
+   return polarity == GPIO_ACTIVE_LOW ? GPIOD_OUT_LOW : 
GPIOD_OUT_HIGH;
+   case ACPI_PIN_CONFIG_PULLDOWN:
+   return polarity == GPIO_ACTIVE_LOW ? GPIOD_OUT_HIGH : 
GPIOD_OUT_LOW;
+   default:
+   break;
+   }
+   break;
+   default:
+   break;
+   }
+
+   /*
+* Assume that the BIOS has configured the direction and pull
+* accordingly.
+*/
+   return GPIOD_ASIS;
+}
+
+static struct gpio_desc *acpi_request_own_gpiod(struct gpio_chip *chip,
+   struct acpi_resource_gpio 
*agpio,
+   unsigned int index,
+   const char *label)
+{
+   int polarity = GPIO_ACTIVE_HIGH;
+   enum gpiod_flags flags = acpi_gpio_to_gpiod_flags(agpio, polarity);
+   unsigned int pin = agpio->pin_table[index];
+   struct gpio_desc *desc;
+   int ret;
+
+   desc = gpiochip_request_own_desc(chip, pin, label, polarity, flags);
+   if (IS_ERR(desc))
+   return desc;
+
+   ret = gpio_set_debounce_timeout(desc, agpio->debounce_timeout);
+   if (ret)
+   gpiochip_free_own_desc(desc);
+
+   return ret ? ERR_PTR(ret) : desc;
+}
+
 static bool acpi_gpio_in_ignore_list(const char *controller_in, int pin_in)
 {
const char *controller, *pin_str;
@@ -290,8 +352,8 @@ static acpi_status acpi_gpiochip_alloc_e
if (!handler)
return AE_OK;
 
-   desc = gpiochip_request_own_desc(chip, pin, "ACPI:Event",
-GPIO_ACTIVE_HIGH, GPIOD_IN);
+   desc = acpi_request_own_gpiod(chip, agpio, 0, "ACPI:Event");
+
if (IS_ERR(desc)) {
dev_err(chip->parent,
"Failed to request GPIO for pin 0x%04X, err %ld\n",
@@ -526,39 +588,6 @@ static bool acpi_get_driver_gpio_data(st
return false;
 }
 
-static enum gpiod_flags
-acpi_gpio_to_gpiod_flags(const struct acpi_resource_gpio *agpio)
-{
-   switch (agpio->io_restriction) {
-   case ACPI_IO_RESTRICT_INPUT:
-   return GPIOD_IN;
-   case ACPI_IO_RESTRICT_OUTPUT:
-   /*
-* ACPI GPIO resources don't contain an initial value for the
-* GPIO. Therefore we deduce that value from the pull field
-* instead. If the pin is pulled up we assume default to be
-* high, if it is pulled down we assume default to be low,
-* otherwise we leave pin untouched.
-*/
-   switch (agpio->pin_config) {
-   case ACPI_PIN_CONFIG_PULLUP:
-   return GPIOD_OUT_HIGH;
-   case ACPI_PIN_CONFIG_PULLDOWN:
-   return GPIOD_OUT_LOW;
-   default:
-   break;
-   }
-   default:
-   break;
-   }
-
-   /*
-* Assume that the BIOS has configured the direction and pull
-* accordingly.
-*/
-   return GPIOD_ASIS;
-}
-
 static int
 __acpi_gpio_update_gpiod_flags(enum gpiod_flags *flags, enum gpiod_flags 
update)
 {
@@ -664,6 +693,7 @@ static int acpi_populate_gpio_lookup(str
lookup->desc = acpi_get_gpiod(agpio->resource_source.string_ptr,
  agpio->pin_table[pin_index]);

[Bug 1908978] Re: ALSA: hda/realtek - Supported Dell fixed type headset

2020-12-21 Thread koba

** Also affects: linux-oem-5.10 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.10 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux (Ubuntu Hirsute)
   Status: Incomplete => In Progress

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: New => In Progress

** Description changed:

  [Impact]
  Can't record sounds from external headset
  
  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
- The patch is provided by the realtek and is archived in the sound sub-system 
tree.
+ The patch is provided by the realtek and has been archived in the sound 
sub-system tree.
  Add "Dell Precision 3650 Tower" in the fix-up table.
  
  [Test Case]
  1. install manifest
  2. plug-in an external headset
  3. try to record sounds via external headset
  
  [Where problems could occur]
  Just add a supported device.

** Tags added: oem-priority originate-from-1904542 somerville

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908978

Title:
  ALSA: hda/realtek - Supported Dell fixed type headset

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908978] Re: ALSA: hda/realtek - Supported Dell fixed type headset

2020-12-21 Thread koba

** Summary changed:

- ALSA: usb-audio: Support ASUS PRIME TRX40 PRO-S
+ ALSA: hda/realtek - Supported Dell fixed type headset

** Description changed:

[Impact]
Can't record sounds from external headset

[Fix]
- Add ASUS PRIME TRX40 PRO-S in the support list.
+
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
+ The fix is provided by the realtek and is archived in the sound sub-system
tree.
+ Add "Dell Precision 3650 Tower" in the fix-up table.

[Test Case]
1. install manifest
2. plug-in an external headset
3. try to record sounds via external headset

[Where problems could occur]
Just add a supported device.

** Description changed:

[Impact]
Can't record sounds from external headset

[Fix]

https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=150927c3674d7db4dd51a7269e01423c8c78e53b
- The fix is provided by the realtek and is archived in the sound sub-system
tree.
+ The patch is provided by the realtek and is archived in the sound sub-system
tree.
Add "Dell Precision 3650 Tower" in the fix-up table.

1 2 3 >

1 - 100 of 225 matches

Mail list logo