public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Patro, Sumant" <Sumant.Patro@lsi.com>
Cc: James.Bottomley@SteelEye.com, akpm@osdl.org,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, "Kolli,
	Neela" <Neela.Kolli@lsi.com>, "Yang, Bo" <Bo.Yang@lsi.com>
Subject: Re: [PATCH] scsi: megaraid_{mm,mbox} init fix for kdump
Date: Fri, 05 Jan 2007 15:50:24 -0800	[thread overview]
Message-ID: <459EE440.6070908@oracle.com> (raw)
In-Reply-To: <0631C836DBF79F42B5A60C8C8D4E82298909B0@NAMAIL2.ad.lsil.com>

Patro, Sumant wrote:
> Hello Randy,
> 
> 	At this time I am not trying to modify the function comment
> style of existing megaraid_mbox code. For the new function the
> description style is in sync with the preexisting code.
> 	So, I request for the patch to be accepted in its current
> submitted form. 

I have no problem with that as long as you'll allow it to be
corrected to match kernel-doc syntax.  Or don't use kernel-doc
syntax there at all.

> Regards,
> 
> Sumant 
> 
> -----Original Message-----
> From: Randy Dunlap [mailto:randy.dunlap@oracle.com] 
> Sent: Friday, January 05, 2007 1:35 PM
> To: Patro, Sumant
> Cc: James.Bottomley@SteelEye.com; akpm@osdl.org;
> linux-scsi@vger.kernel.org; linux-kernel@vger.kernel.org; Kolli, Neela;
> Yang, Bo; Patro, Sumant
> Subject: Re: [PATCH] scsi: megaraid_{mm,mbox} init fix for kdump
> 
> On Fri, 05 Jan 2007 07:10:09 -0800 Sumant Patro wrote:
> 
> Hi,
> 
>> ---
>>
>>  Documentation/scsi/ChangeLog.megaraid |   16 ++
>>  drivers/scsi/megaraid/megaraid_mbox.c |  140 +++++++++++++++++++-----
>>  drivers/scsi/megaraid/megaraid_mbox.h |    4
>>  3 files changed, 130 insertions(+), 30 deletions(-)
>>
>> diff -uprN linux-2.6.orig/drivers/scsi/megaraid/megaraid_mbox.c
> linux-2.6.new/drivers/scsi/megaraid/megaraid_mbox.c
>> --- linux-2.6.orig/drivers/scsi/megaraid/megaraid_mbox.c
> 2006-12-28 09:56:04.000000000 -0800
>> +++ linux-2.6.new/drivers/scsi/megaraid/megaraid_mbox.c
> 2007-01-04 11:22:21.000000000 -0800
>> @@ -3380,6 +3386,84 @@ megaraid_mbox_flush_cache(adapter_t *ada
>>  
>>  
>>  /**
>> + * megaraid_mbox_fire_sync_cmd - fire the sync cmd
>> + * @param adapter	: soft state for the controller
> 
> That (above) should just be:
>  * @adapter:  (plus its description; the description there
>    doesn't seem to agree with its parameter name).
> 
> 
>> + *
>> + * Clears the pending cmds in FW and reinits its RAID structs  */ 
>> +static int megaraid_mbox_fire_sync_cmd(adapter_t *adapter) {
>> +	mbox_t	*mbox;
>> +	uint8_t	raw_mbox[sizeof(mbox_t)];
>> +	mraid_device_t	*raid_dev = ADAP2RAIDDEV(adapter);
>> +	mbox64_t *mbox64;
>> +	int	status = 0;
>> +	int i;
>> +	uint32_t dword;
>> +
>> +	mbox = (mbox_t *)raw_mbox;
>> +
>> +	memset((caddr_t)raw_mbox, 0, sizeof(mbox_t));
>> +
>> +	raw_mbox[0] = 0xFF;
>> +
>> +	mbox64	= raid_dev->mbox64;
>> +	mbox	= raid_dev->mbox;
>> +
>> +	/* Wait until mailbox is free */
>> +	if (megaraid_busywait_mbox(raid_dev) != 0) {
>> +		status = 1;
>> +		goto blocked_mailbox;
>> +	}
>> +
>> +	/* Copy mailbox data into host structure */
>> +	memcpy((caddr_t)mbox, (caddr_t)raw_mbox, 16);
>> +	mbox->cmdid		= 0xFE;
>> +	mbox->busy		= 1;
>> +	mbox->poll		= 0;
>> +	mbox->ack		= 0;
>> +	mbox->numstatus		= 0;
>> +	mbox->status		= 0;
>> +
>> +	wmb();
>> +	WRINDOOR(raid_dev, raid_dev->mbox_dma | 0x1);
>> +
>> +	/* Wait for maximum 1 min for status to post.
>> +	 * If the Firmware SUPPORTS the ABOVE COMMAND,
>> +	 * mbox->cmd will be set to 0
>> +	 * else
>> +	 * the firmware will reject the command with
>> +	 * mbox->numstatus set to 1
>> +	 */
>> +
>> +	i = 0;
>> +	status = 0;
>> +	while (!mbox->numstatus && mbox->cmd == 0xFF) {
>> +		rmb();
>> +		msleep(1);
>> +		i++;
>> +		if (i > 1000 * 60) {
>> +			status = 1;
>> +			break;
>> +		}
>> +	}
>> +	if (mbox->numstatus == 1)
>> +		status = 1; /*cmd not supported*/
>> +
>> +	/* Check for interrupt line */
>> +	dword = RDOUTDOOR(raid_dev);
>> +	WROUTDOOR(raid_dev, dword);
>> +	WRINDOOR(raid_dev,2);
>> +
>> +	return status;
>> +
>> +blocked_mailbox:
>> +	con_log(CL_ANN, (KERN_WARNING "megaraid: blocked mailbox\n"));
>> +	return status;
>> +}
>> +
>> +/**
>>   * megaraid_mbox_display_scb - display SCB information, mostly debug
> purposes
>>   * @param adapter	: controllers' soft state
>>   * @param scb  : SCB to be displayed
> 
> I haven't looked at the entire source file, but these extra "param"
> words should not be there.  kernel-doc syntax is just
>   @name: description
> 
> 
> ---
> ~Randy


-- 
~Randy

  reply	other threads:[~2007-01-05 23:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 23:47 [PATCH] scsi: megaraid_{mm,mbox} init fix for kdump Patro, Sumant
2007-01-05 23:50 ` Randy Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-05 15:10 Sumant Patro
2007-01-05 21:34 ` Randy Dunlap
2007-01-31 17:49 ` Matthias Urlichs
2007-01-03  2:37 [Patch] scsi: megaraid_{mm,mbox}: " Patro, Sumant
2006-12-29 16:02 Sumant Patro
2006-12-29 21:37 ` Randy Dunlap
2006-12-30 14:31   ` Douglas Gilbert
2006-12-30 15:38     ` Randy Dunlap

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=459EE440.6070908@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=Bo.Yang@lsi.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Neela.Kolli@lsi.com \
    --cc=Sumant.Patro@lsi.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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