All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: "Miroslav Bendík" <miroslav.bendik@gmail.com>
Cc: linux-i2c@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: Wrong piix4_smbus address / slow trackpoint on Thinkpad P14s gen 2 (AMD)
Date: Thu, 6 Jan 2022 13:57:38 +0100	[thread overview]
Message-ID: <YdbnQjxBINyFIRsQ@ninjato> (raw)
In-Reply-To: <f8c13907-d296-baa6-7637-c5f8aa96b7ff@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

Hi again,

> Address detection does not work because cd6h/cd7h port io can be
> disabled, but it's accessible using mmio. This patch:
> https://lore.kernel.org/all/20210715221828.244536-1-Terry.Bowman@amd.com/
> with modified AMD_PCI_SMBUS_REVISION_MMIO fixed base address
> detection.

Okay, this patch is stalled because Terry is waiting for review
comments. I'll mention the high priority.

> Problem with RMI4 touchpad / trackpoint remains, because rmi4-smbus
> needs host notify feature. I have tried implement this feature,
> without success. Interrupts on IRQ 7 (SMBus) are generated only for
> block data transfers, but not for trackpoint / touchpad move actions.
> I have looked at pinctrl_amd and it looks, that activity is signaled
> using GPIO. This looks promising:

Isn't the interrupt described in the ACPI tables?

All the best,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-01-06 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11 12:14 Wrong piix4_smbus address / slow trackpoint on Thinkpad P14s gen 2 (AMD) Miroslav Bendik
2022-01-05 17:57 ` Miroslav Bendík
2022-01-06 12:57   ` Wolfram Sang [this message]
2022-01-06 17:54     ` Miroslav Bendík
2022-01-06 18:27   ` Andrea Ippolito
2022-01-07  5:41     ` Miroslav Bendík
2022-01-06 12:52 ` Wolfram Sang
2022-01-08 18:42 ` Miroslav Bendík
2022-01-11 12:35   ` Wolfram Sang
2022-02-12 17:42 ` Miroslav Bendík

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=YdbnQjxBINyFIRsQ@ninjato \
    --to=wsa@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=miroslav.bendik@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.