From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Usyskin, Alexander" <alexander.usyskin@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [char-misc-next] mei: add device type
Date: Tue, 28 Jul 2020 18:09:12 +0000 [thread overview]
Message-ID: <99bf1aa994d64699ab9722ef5db875d9@intel.com> (raw)
In-Reply-To: <20200728155408.GB4178776@kroah.com>
> -----Original Message-----
> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Sent: Tuesday, July 28, 2020 18:54
> To: Winkler, Tomas <tomas.winkler@intel.com>
> Cc: Usyskin, Alexander <alexander.usyskin@intel.com>; linux-
> kernel@vger.kernel.org
> Subject: Re: [char-misc-next] mei: add device type
>
> On Tue, Jul 28, 2020 at 06:25:46PM +0300, Tomas Winkler wrote:
> > From: Alexander Usyskin <alexander.usyskin@intel.com>
> >
> > Some of the device heads are not generic and have specific purpose, we
> > need to announce it to the user space so it can detect and correct
> > device node via matching attributes.
> >
> > Generic devices are marked as 'mei' while special purpose their own
> > names. Currently we are adding 'itouch' string for Intel IPTS devices.
> >
> > Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> > ---
> > drivers/misc/mei/hw-me.c | 12 ++++++++++++
> > drivers/misc/mei/hw-me.h | 5 +++++
> > drivers/misc/mei/hw-txe.c | 1 +
> > drivers/misc/mei/main.c | 27 +++++++++++++++++++++++++++
> > drivers/misc/mei/mei_dev.h | 4 ++++
> > drivers/misc/mei/pci-me.c | 8 ++++----
> > 6 files changed, 53 insertions(+), 4 deletions(-)
>
> No Documentation/ABI/ update for this new sysfs file?
Hmm, looks like I've forgot to 'git add'
Thanks
Tomas
prev parent reply other threads:[~2020-07-28 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 15:25 Tomas Winkler
2020-07-28 15:54 ` Greg Kroah-Hartman
2020-07-28 18:09 ` Winkler, Tomas [this message]
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=99bf1aa994d64699ab9722ef5db875d9@intel.com \
--to=tomas.winkler@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
Powered by JetHome