From: Roger Gammans <rgammans@gammascience.co.uk>
To: Sandeep Singh <Sandeep.Singh@amd.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH v4 4/4] SFH: Create HID report to Enable support of AMD sensor fusion Hub (SFH)
Date: Sun, 29 Mar 2020 18:40:06 +0000 [thread overview]
Message-ID: <20200329184006.GA8199@kilburn.gammascience.co.uk> (raw)
On Thu, Feb 27, 2020 at 05:10:57AM +0000, Sandeep Singh wrote:
> From: Sandeep Singh <sandeep.singh@amd.com>
>
> +#include "amd_sfh_hid_report_descriptor.h"
> +#include "amd_mp2_pcie.h"
I had to change the last line to
#include "../amd_mp2_pcie.h"
to make it compile out of tree. After that I got a clean compile.
Also I don't seem to be getting any data through
to monitor-sensor in user space when I do install it, but I am
gettting logs of log messages similar to this:
pcie_mp2_amd 0000:04:00.7: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0x5267f000 flags=0x0020]
pcie_mp2_amd 0000:04:00.7: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0x5267f000 flags=0x0020]
This is compiled against the debian 5.4.0 kernel, on a
HP ENVY x360 Convertible 15-ds0xxx, SKU 6TD07EA#ABU
I can run other tests or try other kernels if you think it might help,
let me know what you need.
--
Roger Gammans
next reply other threads:[~2020-03-29 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 18:40 Roger Gammans [this message]
2020-03-30 4:23 ` [PATCH v4 4/4] SFH: Create HID report to Enable support of AMD sensor fusion Hub (SFH) Singh, Sandeep
2020-03-30 19:07 ` Roger Gammans
-- strict thread matches above, loose matches on Subject: below --
2020-02-27 4:58 [PATCH v4 0/4] SFH: Add Support for AMD Sensor Fusion Hub Sandeep Singh
2020-02-27 4:58 ` [PATCH v4 4/4] SFH: Create HID report to Enable support of AMD sensor fusion Hub (SFH) Sandeep Singh
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=20200329184006.GA8199@kilburn.gammascience.co.uk \
--to=rgammans@gammascience.co.uk \
--cc=Sandeep.Singh@amd.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).