linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: linux-ide@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 2/12] ht6560b: add "vlb_clock=" parameter
Date: Thu, 13 Mar 2008 23:43:59 +0100	[thread overview]
Message-ID: <20080313224359.7051.8198.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20080313224352.7051.44005.sendpatchset@localhost.localdomain>

Add "vlb_clock=" parameter for specifying VLB clock frequency (in MHz).

Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
---
 drivers/ide/legacy/ht6560b.c |    9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

Index: b/drivers/ide/legacy/ht6560b.c
===================================================================
--- a/drivers/ide/legacy/ht6560b.c
+++ b/drivers/ide/legacy/ht6560b.c
@@ -116,6 +116,8 @@
 #define HT_TIMING(drivea) (u8)((drivea)->drive_data & 0x00ff)
 #define HT_TIMING_DEFAULT 0xff
 
+static int vlb_clock;
+
 /*
  * This routine handles interface switching for the peculiar hardware design
  * on the F.G.I./Holtek HT-6560B VLB IDE interface.
@@ -212,8 +214,8 @@ static u8 ht_pio2timings(ide_drive_t *dr
 {
 	int active_time, recovery_time;
 	int active_cycles, recovery_cycles;
-	int bus_speed = system_bus_clock();
-	
+	int bus_speed = vlb_clock ? vlb_clock : system_bus_clock();
+
         if (pio) {
 		unsigned int cycle_time;
 
@@ -328,6 +330,9 @@ static int probe_ht6560b;
 module_param_named(probe, probe_ht6560b, bool, 0);
 MODULE_PARM_DESC(probe, "probe for HT6560B chipset");
 
+module_param(vlb_clock, int, 0);
+MODULE_PARM_DESC(vlb_clock, "VLB clock frequency (in MHz)");
+
 static const struct ide_port_ops ht6560b_port_ops = {
 	.port_init_devs		= ht6560b_port_init_devs,
 	.set_pio_mode		= ht6560b_set_pio_mode,

  reply	other threads:[~2008-03-13 22:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 22:43 [PATCH 1/12] ali14xx: add "vlb_clock=" parameter Bartlomiej Zolnierkiewicz
2008-03-13 22:43 ` Bartlomiej Zolnierkiewicz [this message]
2008-03-13 22:44 ` [PATCH 3/12] qd65xx: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 4/12] aec62xx: add "pci_clock=" parameter Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 5/12] alim15x3: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 6/12] amd74xx: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 7/12] cmd64x: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 8/12] cy82c693: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 9/12] opti621: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 10/12] via82cxxx: " Bartlomiej Zolnierkiewicz
2008-03-13 22:45 ` [PATCH 11/12] cmd640: add "cmd_clock=" parameter Bartlomiej Zolnierkiewicz
2008-03-13 22:45 ` [PATCH 12/12] ide: mark "idebus=" kernel parameter as obsoleted Bartlomiej Zolnierkiewicz
2008-03-15 12:36 ` [PATCH 1/12] ali14xx: add "vlb_clock=" parameter Alan Cox
2008-03-15 21:44   ` Bartlomiej Zolnierkiewicz

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=20080313224359.7051.8198.sendpatchset@localhost.localdomain \
    --to=bzolnier@gmail.com \
    --cc=linux-ide@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).