linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "Oliver Hartkopp" <socketcan@hartkopp.net>,
	"Thomas Körper" <Thomas.Koerper@esd.eu>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: AW: [PATCH v3 1/1] can: Add support for esd CAN PCIe/402 card
Date: Wed, 05 Nov 2014 11:11:01 +0100	[thread overview]
Message-ID: <5459F7B5.7080002@pengutronix.de> (raw)
In-Reply-To: <5459EA11.4060600@hartkopp.net>

[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]

On 11/05/2014 10:12 AM, Oliver Hartkopp wrote:
> On 05.11.2014 05:21, Thomas Körper wrote:
> 
>> already was afraid the module param should be removed :)
>> May I print all these infos unconditionally?  ...If someone has
>> trouble with the card we really like to see that stuff first.
> 
> Oh. It's no problem to print hardware specific information at startup.
> But this is IMO only too much because of it's formatting
> 
> +	if (dump_infos) {
> +		dev_info(dev, "  Probe register: 0x%.8x\n",
> +			 acc_ov_read32(ov, ACC_OV_OF_PROBE));
> +		dev_info(dev, "  Features: 0x%.4x\n", ov->features);
> +		dev_info(dev, "  FPGA Version: 0x%.4x\n",
> +			 ov->version);
> +		dev_info(dev, "  Strappings: 0x%.4x\n",
> +			 acc_ov_read32(ov, ACC_OV_OF_INFO) >> 16);
> +		dev_info(dev, "  Active cores: %u\n",
> +			 ov->active_cores);
> +		dev_info(dev, "  Total cores: %u\n",
> +			 ov->total_cores);
> +		dev_info(dev, "  Core frequency: %u\n",
> +			 ov->core_frequency);
> +		dev_info(dev, "  Timestamp frequency: %u\n",
> +			 ov->timestamp_frequency);
> +	}
> 
> What about putting these information in just one or two lines, e.g.
> 
> esdacc: FPGA rev x.xx @ 3000Hz (TS @ 400Hz), probe reg x.xx, feat. x.xx, X of Y cores active 

One line would be fine.

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-11-05 10:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  5:47 [PATCH v3 1/1] can: Add support for esd CAN PCIe/402 card Thomas Körper
2014-11-04 13:24 ` Oliver Hartkopp
2014-11-04 13:26   ` Marc Kleine-Budde
2014-11-05  4:21     ` AW: " Thomas Körper
2014-11-05  9:12       ` Oliver Hartkopp
2014-11-05 10:11         ` Marc Kleine-Budde [this message]
2015-03-16 11:45       ` Thomas Körper
2015-03-16 11:53         ` Marc Kleine-Budde
2015-03-16 12:00           ` Oliver Hartkopp

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=5459F7B5.7080002@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=Thomas.Koerper@esd.eu \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    /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).