linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Duggan <aduggan@synaptics.com>,
	Christopher Heiny <cheiny@synaptics.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 1/2] i2c: i801: add support of Host Notify
Date: Mon, 1 Aug 2016 15:33:52 +0200	[thread overview]
Message-ID: <20160801153352.44943aae@endymion> (raw)
In-Reply-To: <20160728094457.GN19383@mail.corp.redhat.com>

On Thu, 28 Jul 2016 11:44:57 +0200, Benjamin Tissoires wrote:
> On Jul 18 2016 or thereabouts, Jean Delvare wrote:
> > On Fri, 24 Jun 2016 16:39:49 +0200, Benjamin Tissoires wrote:
> > > The i801 chip can handle the Host Notify feature since ICH 3 as mentioned
> > > in http://www.intel.com/content/dam/doc/datasheet/82801ca-io-controller-hub-3-datasheet.pdf
> > > 
> > > Enable the functionality unconditionally and propagate the alert
> > > on each notification.
> > > 
> > > With a T440s and a Synaptics touchpad that implements Host Notify, the
> > > payload data is always 0x0000, so I am not sure if the device actually
> > > sends the payload or if there is a problem regarding the implementation.
> > 
> > Out of curiosity, does it work on at least one machine?
> 
> I have tested the T440, t450 and t460 (3 different generation of Intel
> processor), and none seems to be working. The Synaptics touchpad used is
> mostly the same, so maybe that's a device issue.

May I ask why you are pushing the code upstream then, if it has no
known (working) user?

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2016-08-01 13:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 14:39 [PATCH v9 1/2] i2c: i801: add support of Host Notify Benjamin Tissoires
2016-06-24 14:41 ` [PATCH v9 2/2] Input: synaptics-rmi4 - add SMBus support Benjamin Tissoires
2016-06-24 21:47   ` kbuild test robot
2016-06-24 21:47   ` [PATCH] Input: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-07-05 15:40 ` [PATCH v9 1/2] i2c: i801: add support of Host Notify Wolfram Sang
2016-07-18 14:12 ` Jean Delvare
2016-07-28  9:44   ` Benjamin Tissoires
2016-08-01 13:33     ` Jean Delvare [this message]
2016-08-19 13:19       ` Benjamin Tissoires

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=20160801153352.44943aae@endymion \
    --to=jdelvare@suse.de \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=cheiny@synaptics.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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;
as well as URLs for NNTP newsgroup(s).