public inbox for platform-driver-x86@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 199715] hp_accel: probe of HPQ6007:00 failed with error -22 (HP Envy x360)
Date: Sat, 23 Jan 2021 22:08:40 +0000	[thread overview]
Message-ID: <bug-199715-215701-WPgQec0eoG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199715-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=199715

--- Comment #55 from Richard Neumann (mail@richard-neumann.de) ---
@Dimitris. The submitted v8 Version of AMD is already merged into the mainline
kernel for v5.11, afaik. So we will definitely get a driver with kernel 5.11.
The only problem is, that it does not include an option to override the sensor
mask if the manufacturer of the system did not write it into the P2C register
as is the case on our HP Envy 13-ag0xxx models.
So the upstream driver is pretty useless to us.

My refactored patch series is a side-project I developed after the initial
driver version of AMD was submitted upstream. I repeatedly asked for adding a
kernel parameter to be able to override the sensor mask, which was confirmed as
a good idea, but was never implemented. So I took a look at the code myself and
added it. While I was at it, I encountered some more problems regarding the
code structure and DMA handling, that I also reported upstream [1]. I also saw
some unused code. So, to challenge myself to improve the driver, I read into
the Linux kernel API documentation for the HID subsystem, PCI drivers and
platform drivers and re-wrote the patch to what eventually became the patch
series that I now submitted upstream.

I understand Hans' concern about the rewrite, but I think that it would benefit
the Kernel to share my work on the driver. If the maintainers are reluctant to
replace the driver with my changes, that's okay. They can still cherry pick
what they regard as improvements on the code.

[1] https://lkml.org/lkml/2020/3/30/157

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-01-23 22:09 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-199715-215701@https.bugzilla.kernel.org/>
2021-01-16 20:14 ` [Bug 199715] hp_accel: probe of HPQ6007:00 failed with error -22 (HP Envy x360) bugzilla-daemon
2021-01-17  9:02 ` bugzilla-daemon
2021-01-17 10:57 ` bugzilla-daemon
2021-01-17 10:57 ` bugzilla-daemon
2021-01-17 10:58 ` bugzilla-daemon
2021-01-17 11:09 ` bugzilla-daemon
2021-01-17 11:13 ` bugzilla-daemon
2021-01-17 11:34 ` bugzilla-daemon
2021-01-17 11:36 ` bugzilla-daemon
2021-01-17 12:15 ` bugzilla-daemon
2021-01-17 14:23 ` bugzilla-daemon
2021-01-17 14:46 ` bugzilla-daemon
2021-01-17 14:49 ` bugzilla-daemon
2021-01-17 14:51 ` bugzilla-daemon
2021-01-17 16:01 ` bugzilla-daemon
2021-01-19 13:38 ` bugzilla-daemon
2021-01-19 18:56 ` bugzilla-daemon
2021-01-19 20:20 ` bugzilla-daemon
2021-01-19 20:24 ` bugzilla-daemon
2021-01-19 20:36 ` bugzilla-daemon
2021-01-19 20:45 ` bugzilla-daemon
2021-01-19 22:25 ` bugzilla-daemon
2021-01-20  9:24 ` bugzilla-daemon
2021-01-20 11:09 ` bugzilla-daemon
2021-01-20 11:45 ` bugzilla-daemon
2021-01-21 16:58 ` bugzilla-daemon
2021-01-23 14:15 ` bugzilla-daemon
2021-01-23 20:58 ` bugzilla-daemon
2021-01-23 22:08 ` bugzilla-daemon [this message]
2021-01-24 12:04 ` bugzilla-daemon
2021-01-24 16:11 ` bugzilla-daemon
2021-01-27  1:57 ` bugzilla-daemon
2021-10-12 10:44 ` bugzilla-daemon
2021-12-04 11:00 ` bugzilla-daemon
2021-12-04 11:06 ` bugzilla-daemon
2021-12-04 14:48 ` bugzilla-daemon
2021-12-04 16:12 ` bugzilla-daemon
2022-02-02 19:04 ` bugzilla-daemon
2022-02-09 17:52 ` bugzilla-daemon
2022-02-23 20:30 ` bugzilla-daemon
2022-02-24  6:22 ` bugzilla-daemon
2025-04-30  6:37 ` bugzilla-daemon
2026-03-17 14:42 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-199715-215701-WPgQec0eoG@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox