All of lore.kernel.org
 help / color / mirror / Atom feed
From: Varka Bhadram <varkabhadram@gmail.com>
To: Dong Aisheng <b29396@freescale.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
	linux-can@vger.kernel.org, wg@grandegger.com,
	socketcan@hartkopp.net, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, mark.rutland@arm.com
Subject: Re: [PATCH v3 2/2] can: m_can: add Bosch M_CAN controller support
Date: Mon, 14 Jul 2014 13:05:55 +0530	[thread overview]
Message-ID: <53C3885B.5020008@gmail.com> (raw)
In-Reply-To: <20140714072146.GD1668@shlinux1.ap.freescale.net>

On 07/14/2014 12:51 PM, Dong Aisheng wrote:
>
> +    dev_dbg(&pdev->dev, "mram_base %p sidf 0x%x %d xidf 0x%x %d rxf0
> 0x%x %d rxf1 0x%x %d rxb 0x%x %d txe 0x%x %d txb 0x%x %d\n",
> +        priv->mram_base,
> +        priv->mcfg[MRAM_SIDF].off, priv->mcfg[MRAM_SIDF].num,
> +        priv->mcfg[MRAM_XIDF].off, priv->mcfg[MRAM_XIDF].num,
> +        priv->mcfg[MRAM_RXF0].off, priv->mcfg[MRAM_RXF0].num,
> +        priv->mcfg[MRAM_RXF1].off, priv->mcfg[MRAM_RXF1].num,
> +        priv->mcfg[MRAM_RXB].off, priv->mcfg[MRAM_RXB].num,
> +        priv->mcfg[MRAM_TXE].off, priv->mcfg[MRAM_TXE].num,
> +        priv->mcfg[MRAM_TXB].off, priv->mcfg[MRAM_TXB].num);
> +
>>>> dev_dbg() will insert the new lines in b/w. It wont print the values as
>>>> you expected.
>>>> Check this by enabling debug ...
>>> What do you mean by b/w?
>> You are expecting the data to be print in format like:
>> pdev->dev/name: mram_base %p sidf 0x%x %d xidf 0x%x %d rxf0 0x%x %d rxf1 0x%x %d rxb 0x%x %d txe 0x%x %d txb 0x%x %d
>>
>> But when we use the dev_dbg()/pr_debug()... It will put data like:
>> pdev->dev/name: mram_base %p sidf 0x%x
>> 0x%x %d rxf0 0x%x
>> rxf1 0x%x %d rxb
>> ....
>>
>> check this by enable DEBUG...
>>
> My test showed the format is:
> root@imx6qdlsolo:~# uname -a
> Linux imx6qdlsolo 3.16.0-rc2-next-20140627-00006-gd55dd62-dirty #373 SMP Fri Jul 11 18:12:31 CST 2014 armv7l GNU/Linux
> root@imx6qdlsolo:~# dmesg | grep m_can
> m_can 20e8000.can: mram_base c0990000 sidf 0x0 0 xidf 0x0 0 rxf0 0x0 32 rxf1 0x200 0 rxb 0x200 0 txe 0x200 0 txb 0x200 1
> m_can 20e8000.can: m_can device registered (regs=c0988000, irq=146)
> m_can 20f0000.can: mram_base c09a0000 sidf 0x400 0 xidf 0x400 0 rxf0 0x400 32 rxf1 0x600 0 rxb 0x600 0 txe 0x600 0 txb 0x600 1
> m_can 20f0000.can: m_can device registered (regs=c0998000, irq=147)
>
I think you got the expected result.

I faced the above problem when i use pr_debug(). Can you check with this....?

This is good. Thanks for clarification.

>
> Regards
> Dong Aisheng
>
-- 
Regards,
Varka Bhadram.


WARNING: multiple messages have this Message-ID (diff)
From: varkabhadram@gmail.com (Varka Bhadram)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] can: m_can: add Bosch M_CAN controller support
Date: Mon, 14 Jul 2014 13:05:55 +0530	[thread overview]
Message-ID: <53C3885B.5020008@gmail.com> (raw)
In-Reply-To: <20140714072146.GD1668@shlinux1.ap.freescale.net>

On 07/14/2014 12:51 PM, Dong Aisheng wrote:
>
> +    dev_dbg(&pdev->dev, "mram_base %p sidf 0x%x %d xidf 0x%x %d rxf0
> 0x%x %d rxf1 0x%x %d rxb 0x%x %d txe 0x%x %d txb 0x%x %d\n",
> +        priv->mram_base,
> +        priv->mcfg[MRAM_SIDF].off, priv->mcfg[MRAM_SIDF].num,
> +        priv->mcfg[MRAM_XIDF].off, priv->mcfg[MRAM_XIDF].num,
> +        priv->mcfg[MRAM_RXF0].off, priv->mcfg[MRAM_RXF0].num,
> +        priv->mcfg[MRAM_RXF1].off, priv->mcfg[MRAM_RXF1].num,
> +        priv->mcfg[MRAM_RXB].off, priv->mcfg[MRAM_RXB].num,
> +        priv->mcfg[MRAM_TXE].off, priv->mcfg[MRAM_TXE].num,
> +        priv->mcfg[MRAM_TXB].off, priv->mcfg[MRAM_TXB].num);
> +
>>>> dev_dbg() will insert the new lines in b/w. It wont print the values as
>>>> you expected.
>>>> Check this by enabling debug ...
>>> What do you mean by b/w?
>> You are expecting the data to be print in format like:
>> pdev->dev/name: mram_base %p sidf 0x%x %d xidf 0x%x %d rxf0 0x%x %d rxf1 0x%x %d rxb 0x%x %d txe 0x%x %d txb 0x%x %d
>>
>> But when we use the dev_dbg()/pr_debug()... It will put data like:
>> pdev->dev/name: mram_base %p sidf 0x%x
>> 0x%x %d rxf0 0x%x
>> rxf1 0x%x %d rxb
>> ....
>>
>> check this by enable DEBUG...
>>
> My test showed the format is:
> root at imx6qdlsolo:~# uname -a
> Linux imx6qdlsolo 3.16.0-rc2-next-20140627-00006-gd55dd62-dirty #373 SMP Fri Jul 11 18:12:31 CST 2014 armv7l GNU/Linux
> root at imx6qdlsolo:~# dmesg | grep m_can
> m_can 20e8000.can: mram_base c0990000 sidf 0x0 0 xidf 0x0 0 rxf0 0x0 32 rxf1 0x200 0 rxb 0x200 0 txe 0x200 0 txb 0x200 1
> m_can 20e8000.can: m_can device registered (regs=c0988000, irq=146)
> m_can 20f0000.can: mram_base c09a0000 sidf 0x400 0 xidf 0x400 0 rxf0 0x400 32 rxf1 0x600 0 rxb 0x600 0 txe 0x600 0 txb 0x600 1
> m_can 20f0000.can: m_can device registered (regs=c0998000, irq=147)
>
I think you got the expected result.

I faced the above problem when i use pr_debug(). Can you check with this....?

This is good. Thanks for clarification.

>
> Regards
> Dong Aisheng
>
-- 
Regards,
Varka Bhadram.

  reply	other threads:[~2014-07-14  7:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 10:29 [PATCH v3 1/2] can: m_can: add device tree binding documentation Dong Aisheng
2014-07-11 10:29 ` Dong Aisheng
2014-07-11 10:29 ` [PATCH v3 2/2] can: m_can: add Bosch M_CAN controller support Dong Aisheng
2014-07-11 10:29   ` Dong Aisheng
2014-07-11 11:13   ` Varka Bhadram
2014-07-11 11:13     ` Varka Bhadram
     [not found]     ` <53BFC6CE.9090408-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-11 12:03       ` Marc Kleine-Budde
2014-07-11 12:03         ` Marc Kleine-Budde
2014-07-11 12:13         ` Varka Bhadram
2014-07-11 12:13           ` Varka Bhadram
2014-07-11 12:22           ` Marc Kleine-Budde
2014-07-11 12:22             ` Marc Kleine-Budde
2014-07-14  7:21           ` Dong Aisheng
2014-07-14  7:21             ` Dong Aisheng
2014-07-14  7:35             ` Varka Bhadram [this message]
2014-07-14  7:35               ` Varka Bhadram
2014-07-14  8:24               ` Dong Aisheng
2014-07-14  8:24                 ` Dong Aisheng
2014-07-14  8:46                 ` Varka Bhadram
2014-07-14  8:46                   ` Varka Bhadram
2014-07-11 10:41 ` [PATCH v3 1/2] can: m_can: add device tree binding documentation Varka Bhadram
2014-07-11 10:41   ` Varka Bhadram
2014-07-14  3:24   ` Dong Aisheng
2014-07-14  3:24     ` Dong Aisheng
2014-07-14  4:37     ` Varka Bhadram
2014-07-14  4:37       ` Varka Bhadram
2014-07-14  5:04       ` Dong Aisheng
2014-07-14  5:04         ` Dong Aisheng
2014-07-14  5:18         ` Varka Bhadram
2014-07-14  5:18           ` Varka Bhadram
2014-07-11 12:54 ` Marc Kleine-Budde
2014-07-11 12:54   ` Marc Kleine-Budde
2014-07-14  7:06   ` Dong Aisheng
2014-07-14  7:06     ` Dong Aisheng

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=53C3885B.5020008@gmail.com \
    --to=varkabhadram@gmail.com \
    --cc=b29396@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mkl@pengutronix.de \
    --cc=socketcan@hartkopp.net \
    --cc=wg@grandegger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.