From: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Platform Driver <platform-driver-x86@vger.kernel.org>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>,
Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>
Subject: Re: [PATCH 1/4] platform/x86: intel_pmc_core: Show Latency Tolerance info
Date: Wed, 26 Sep 2018 19:41:49 +0530 [thread overview]
Message-ID: <04398317-a3b8-9387-e532-fcf26da9220e@linux.intel.com> (raw)
In-Reply-To: <CAHp75Vesn4TrdF8tWLkU7nCRGp_o8fEK6gxpTkwM7E7zQo0qKg@mail.gmail.com>
On 26-Sep-18 7:18 PM, Andy Shevchenko wrote:
> On Mon, Sep 3, 2018 at 9:06 PM Rajneesh Bhardwaj
> <rajneesh.bhardwaj@linux.intel.com> wrote:
>> This adds support to show the Latency Tolerance Reporting for the IPs on
>> the PCH as reported by the PMC. The format shown here is raw LTR data
>> payload that can further be decoded as per the PCI specification.
>>
>> This also fixes some minor alignment issues in the header file by
>> removing spaces and converting to tabs at some places.
> Thanks for the patch, my comments below.
Hi Andy,
Thanks for the review, my answers below.
>
>> +static const struct pmc_bit_map spt_ltr_show_map[] = {
>> + {"IP 0 : LTR_SOUTHPORT_A", SPT_PMC_LTR_SPA},
>> + {"IP 1 : LTR_SOUTHPORT_B", SPT_PMC_LTR_SPB},
>> + {"IP 2 : LTR_SATA", SPT_PMC_LTR_SATA},
>> + {"IP 3 : LTR_GIGABIT_ETHERNET", SPT_PMC_LTR_GBE},
>> + {"IP 4 : LTR_XHCI", SPT_PMC_LTR_XHCI},
>> + /* IP 5 is reserved */
>> + {"IP 6 : LTR_ME", SPT_PMC_LTR_ME},
>> + /* EVA is Enterprise Value Add, doesn't really exist on PCH */
>> + {"IP 7 : LTR_EVA", SPT_PMC_LTR_EVA},
>> + {"IP 8 : LTR_SOUTHPORT_C", SPT_PMC_LTR_SPC},
>> + {"IP 9 : LTR_HD_AUDIO", SPT_PMC_LTR_AZ},
>> + /* IP 10 is reserved */
>> + {"IP 11 : LTR_LPSS", SPT_PMC_LTR_LPSS},
>> + {"IP 12 : LTR_SOUTHPORT_D", SPT_PMC_LTR_SPD},
>> + {"IP 13 : LTR_SOUTHPORT_E", SPT_PMC_LTR_SPE},
>> + {"IP 14 : LTR_CAMERA", SPT_PMC_LTR_CAM},
>> + {"IP 15 : LTR_ESPI", SPT_PMC_LTR_ESPI},
>> + {"IP 16 : LTR_SCC", SPT_PMC_LTR_SCC},
>> + {"IP 17 : LTR_ISH", SPT_PMC_LTR_ISH},
>> + /* Below two cannot be for LTR_IGNORE */
>> + {"LTR_CURRENT_PLATFORM", SPT_PMC_LTR_CUR_PLT},
>> + {"LTR_AGGREGATED_SYSTEM", SPT_PMC_LTR_CUR_ASLT},
> Before no map has this fancy "IP xx :" prefixes. Please, remove.
The users of the driver often ask for IP Numbers while performing
LTR_IGNORE operation so this is deliberately added. Please consider it.
>
>> + {},
> No need for comma
Ok.
>> +
> Redundant.
OK
>
>> +};
>> +static const struct pmc_bit_map cnp_ltr_show_map[] = {
> Same comments as above.
>
>> +};
>> + debugfs_create_file("ltr_show", 0644, dir, pmcdev,
>> + &pmc_core_ltr_fops);
> One line?
IIRC, it was crossing the limit. I will check again and if possible
would change it.
>
>> #define NUM_RETRIES 100
>> #define NUM_IP_IGN_ALLOWED 17
> + blank line here.
Sure.
>
>> +#define SPT_PMC_LTR_CUR_PLT 0x350
next prev parent reply other threads:[~2018-09-26 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 18:04 [PATCH 1/4] platform/x86: intel_pmc_core: Show Latency Tolerance info Rajneesh Bhardwaj
2018-09-03 18:04 ` [PATCH 2/4] platform/x86: intel_pmc_core: Fix LTR IGNORE Max offset Rajneesh Bhardwaj
2018-09-26 13:57 ` Andy Shevchenko
2018-09-26 14:24 ` Bhardwaj, Rajneesh
2018-09-03 18:04 ` [PATCH 3/4] platform/x86: intel_pmc_core: Decode Snoop / Non Snoop LTR Rajneesh Bhardwaj
2018-09-26 13:53 ` Andy Shevchenko
2018-09-26 14:19 ` Bhardwaj, Rajneesh
2018-09-26 17:42 ` Andy Shevchenko
2018-09-03 18:04 ` [PATCH 4/4] platform/x86: intel_telemetry: report debugfs failure Rajneesh Bhardwaj
2018-09-26 13:56 ` Andy Shevchenko
2018-09-26 14:24 ` Bhardwaj, Rajneesh
2018-09-26 17:18 ` Andy Shevchenko
[not found] ` <bb2d01ce-e2c9-18a8-7409-8c014989f732@linux.intel.com>
2018-09-28 9:10 ` Rajneesh Bhardwaj
2018-09-26 13:48 ` [PATCH 1/4] platform/x86: intel_pmc_core: Show Latency Tolerance info Andy Shevchenko
2018-09-26 14:11 ` Bhardwaj, Rajneesh [this message]
2018-09-26 17:14 ` Andy Shevchenko
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=04398317-a3b8-9387-e532-fcf26da9220e@linux.intel.com \
--to=rajneesh.bhardwaj@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajneesh.bhardwaj@intel.com \
--cc=souvik.k.chakravarty@intel.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 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).