Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933726Ab0BESo5 (ORCPT ); Fri, 5 Feb 2010 13:44:57 -0500 Received: from mga11.intel.com ([192.55.52.93]:42295 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933601Ab0BESo4 (ORCPT ); Fri, 5 Feb 2010 13:44:56 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.49,414,1262592000"; d="scan'208";a="538198407" From: Mark Allyn To: linux-kernel@vger.kernel.org, alan@linux.intel.com, charles.f.johnson@intel.com Cc: Mark Allyn Subject: Patch set for Restricted Access Region Register driver Date: Fri, 5 Feb 2010 10:49:09 -0800 Message-Id: <1265395749-15855-1-git-send-email-mark.a.allyn@intel.com> X-Mailer: git-send-email 1.6.0.6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1810 Lines: 50 The following six patches are for the Restricted Access Region Register (rar_register) driver. This driver is for the Intel MID platform. Restricted access regions are regions of memory that can be locked so that the x86 processor cannot access them. However, peripheral devices with DMA can access them. Restricted access regions are used to protect sensitive information from access by unauthorized software running on the x86 processor. The scenario is that encrypted information is presented to an encryption/decryption device. That device in turn does decryption of the information and places into one of the restricted access regions. Another device can then access and use the decrypted information. The x86 processor, however, cannot see that data. The rar_register driver provides address information for the individual restricted access regions to other device driver that need to use the regions. The rar_register also locks restricted access regions upon request by other device drivers. The rar_register device does not interact with user space processes at all. It only ineracts with other device driver. There are six patches: 1 renaming driver to rar_register 2 renaming directory to rar_register 3 provide better explanation in Kconfig 4 fix checkpatch errors and debug header file 5 fix checkpatch errors and debug program file 6 add suspend and resume functions Patches 1 and 2 are for renaming the driver from rar to rar_register. They do not fix checkpatch issues. A sucessful build was completed following all of these patches. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/