From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754845AbcCKG0H (ORCPT ); Fri, 11 Mar 2016 01:26:07 -0500 Received: from mga09.intel.com ([134.134.136.24]:7843 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753075AbcCKGZ4 (ORCPT ); Fri, 11 Mar 2016 01:25:56 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,319,1455004800"; d="scan'208";a="64087990" Message-ID: <56E264EC.9070505@intel.com> Date: Fri, 11 Mar 2016 14:25:48 +0800 From: "Yong, Jonathan" User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:25.4) Gecko/20150524 FossaMail/25.1.5 MIME-Version: 1.0 To: linux-kernel@vger.kernel.org CC: "Yong, Jonathan" Subject: Re: [RFC] PCI: PTM Driver References: <1456730965-16684-1-git-send-email-jonathan.yong@intel.com> In-Reply-To: <1456730965-16684-1-git-send-email-jonathan.yong@intel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/29/2016 15:29, Yong, Jonathan wrote: > Hello LKML, > > This is a preliminary implementation of the PTM[1] support driver, the code > is obviously hacked together and in need of refactoring. This driver has > only been tested against a virtual PCI bus. > > The drivers job is to get to every PTM capable device, set some PCI config > space bits, then go back to sleep [2]. > > PTM capable PCIe devices will get a new sysfs entry to allow PTM to be > enabled if automatic PTM activation is disabled, or disabled if so desired. > > Comments? Should I explain the PTM registers in more details? > Please CC me, thanks. Ping?