From: James Feist <james.feist@linux.intel.com>
To: Vijay Khemka <vijaykhemka@fb.com>,
Andrew Jeffery <andrew@aj.id.au>,
Neeraj Ladkani <neladk@microsoft.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: nvme sensors
Date: Fri, 17 Apr 2020 11:47:15 -0700 [thread overview]
Message-ID: <954154ef-14f8-69fd-677b-e414cbdb0ae2@linux.intel.com> (raw)
In-Reply-To: <5CD00373-FD92-4E57-90C5-21FB8AD6DD25@fb.com>
On 4/16/2020 4:15 PM, Vijay Khemka wrote:
> Currently, dbus-sensors support reading NVME sensors via mctp only. It uses
> libmctp and some of smbus patch from Intel. It also uses slave mqueue mctp
> kernel driver which is not upstream.
>
> So currently it is not matured and fully upstreamed.
>
> James, how can we use this without mctp. I don't see any non mctp support like
> Sending direct smbus command, please advise if I missed it.
Currently it only supports MCTP. Should be easy to change it to support
both with some flag if you require it.
>
> Regards
> -Vijay
>
>
next prev parent reply other threads:[~2020-04-17 18:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 12:07 nvme sensors Vijay Khemka
2020-04-15 12:28 ` Vijay Khemka
2020-04-15 17:59 ` Neeraj Ladkani
2020-04-15 18:49 ` Vijay Khemka
2020-04-15 20:59 ` Neeraj Ladkani
2020-04-16 2:40 ` Andrew Jeffery
2020-04-16 3:08 ` Mark Carlson
2020-04-17 0:36 ` Andrew Jeffery
2020-04-16 7:52 ` [EXTERNAL] " Neeraj Ladkani
2020-04-17 0:57 ` Andrew Jeffery
2020-04-16 23:15 ` Vijay Khemka
2020-04-16 23:34 ` Benjamin Fair
2020-04-17 18:04 ` Vijay Khemka
2020-04-17 18:10 ` Benjamin Fair
2020-04-17 18:41 ` Vijay Khemka
2020-04-17 18:57 ` Benjamin Fair
2020-04-17 19:21 ` Vijay Khemka
2020-04-17 18:47 ` James Feist [this message]
2020-04-17 19:20 ` Vijay Khemka
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=954154ef-14f8-69fd-677b-e414cbdb0ae2@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=andrew@aj.id.au \
--cc=neladk@microsoft.com \
--cc=openbmc@lists.ozlabs.org \
--cc=vijaykhemka@fb.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.