public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <greg@kroah.com>
Cc: Andi Kleen <ak@muc.de>, <linux-kernel@vger.kernel.org>
Subject: [PATCH] Add sysfs support for the i8259 PIC on x86_64
Date: 20 Aug 2004 02:40:49 -0600	[thread overview]
Message-ID: <m13c2i8ani.fsf@ebiederm.dsl.xmission.com> (raw)


I got to looking at x86_64 and while it occasionally uses the i8259 legacy
pic it is not put in sysfs.

Here is the appropriate code ported code from i386.

diff -uNr linux-2.6.8.1-i8259-shutdown.i386/arch/x86_64/kernel/i8259.c linux-2.6.8.1-i8259-sysfs.x86_64/arch/x86_64/kernel/i8259.c
--- linux-2.6.8.1-i8259-shutdown.i386/arch/x86_64/kernel/i8259.c	Wed Aug 18 14:54:30 2004
+++ linux-2.6.8.1-i8259-sysfs.x86_64/arch/x86_64/kernel/i8259.c	Wed Aug 18 14:59:00 2004
@@ -342,6 +342,44 @@
 	}
 }
 
+static int i8259A_resume(struct sys_device *dev)
+{
+	init_8259A(0);
+	return 0;
+}
+
+static int i8259A_shutdown(struct sys_device *dev)
+{
+	/* Put the i8259A into a quiescent state that
+	 * the kernel initialization code can get it
+	 * out of.
+	 */
+	outb(0xff, 0x21);	/* mask all of 8259A-1 */
+	outb(0xff, 0xA1);	/* mask all of 8259A-1 */
+	return 0;
+}
+
+static struct sysdev_class i8259_sysdev_class = {
+	set_kset_name("i8259"),
+	.resume = i8259A_resume,
+	.shutdown = i8259A_shutdown,
+};
+
+static struct sys_device device_i8259A = {
+	.id	= 0,
+	.cls	= &i8259_sysdev_class,
+};
+
+static int __init i8259A_init_sysfs(void)
+{
+	int error = sysdev_class_register(&i8259_sysdev_class);
+	if (!error)
+		error = sysdev_register(&device_i8259A);
+	return error;
+}
+
+device_initcall(i8259A_init_sysfs);
+
 void __init init_8259A(int auto_eoi)
 {
 	unsigned long flags;

             reply	other threads:[~2004-08-20  8:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20  8:40 Eric W. Biederman [this message]
2004-08-24 23:16 ` [PATCH] Add sysfs support for the i8259 PIC on x86_64 Greg KH

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=m13c2i8ani.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=ak@muc.de \
    --cc=greg@kroah.com \
    --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