Linux bluetooth development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	Xinming Hu <huxm@marvell.com>, Cathy Luo <cluo@marvell.com>,
	Avinash Patil <patila@marvell.com>
Subject: Re: [PATCH] Bluetooth: btmrvl add firmware dump support
Date: Wed, 19 Nov 2014 14:43:15 +0100	[thread overview]
Message-ID: <1416404595.9374.4.camel@sipsolutions.net> (raw)
In-Reply-To: <1416403887-9271-1-git-send-email-akarwar@marvell.com>

On Wed, 2014-11-19 at 05:31 -0800, Amitkumar Karwar wrote:

> +static ssize_t btmrvl_fwdump_read(struct file *file, char __user *userbuf,
> +				  size_t count, loff_t *ppos)
> +{
> +	struct btmrvl_private *priv = file->private_data;
> +	ssize_t ret = 0;
> +
> +	btmrvl_firmware_dump(priv);

Might be better to do that on write.


> +		fw_dump_len += (strlen("========Start dump ") +
> +				strlen(entry->mem_name) +
> +				strlen("========\n") +
> +				(memory_size + 1) +
> +				strlen("\n========End dump========\n"));

I'd consider a binary file format.

You also need the select in the Kconfig as I pointed out before.

The more intended use case for this was to trigger it when the driver
detected a crash, but I guess a debugfs file works as well, just not
sure when you'd want it.

johannes

  reply	other threads:[~2014-11-19 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 13:31 [PATCH] Bluetooth: btmrvl add firmware dump support Amitkumar Karwar
2014-11-19 13:43 ` Johannes Berg [this message]
2014-11-19 13:58   ` Amitkumar Karwar
2014-11-19 14:02     ` Johannes Berg
2014-11-19 14:17       ` Amitkumar Karwar
  -- strict thread matches above, loose matches on Subject: below --
2014-11-20 15:44 Amitkumar Karwar

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=1416404595.9374.4.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=huxm@marvell.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=patila@marvell.com \
    /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