linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@codeaurora.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Nicolas Pitre <nico@fluxnic.net>,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Jeremy Kerr <jeremy.kerr@canonical.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Jason Wang <jason77.wang@gmail.com>,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] msm: fix debug-macro.S build failure
Date: Thu, 28 Oct 2010 11:00:24 -0700	[thread overview]
Message-ID: <1288288824.2683.24.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20101028174653.GH3122@n2100.arm.linux.org.uk>

On Thu, 2010-10-28 at 18:46 +0100, Russell King - ARM Linux wrote:

> There is no such option present - and there never has been.  This raises
> the question about what you did before with .phys_io and .io_pg_offst
> on these platforms which can't support it at all.

We had this in some of the boards (or something like it),

#ifdef CONFIG_MSM_DEBUG_UART
        .phys_io        = MSM_DEBUG_UART_PHYS,
        .io_pg_offst    = ((MSM_DEBUG_UART_BASE) >> 18) & 0xfffc,
#endif 

and the code in debug-macro.S had similar ifdefs.

I should change what I said in the last email. It's not that these
boards can't support this, it's that they can't support it _right now_.
It's something we can add, but haven't yet.

> Effectively, rp is what you would've returned as .phys_io, and rv is
> the virtual address corresponding to .io_pg_offst - so just replicate
> that behaviour.  But do not leave this function empty otherwise if you
> enable DEBUG_LL, you'll get unpredictable behaviour.

This is what the function currently has,

        .macro  addruart, rp, rv
        ldr     \rp, =MSM_DEBUG_UART_PHYS
        ldr     \rv, =MSM_DEBUG_UART_BASE
        .endm

So if we have a MSM_DEBUG_UART_PHYS and MSM_DEBUG_UART_BASE we're
returning it. We don't actually have those values for all the boards
tho. My understanding was that there are some generic arm changes
needed, but I need to confirm that.

Daniel


-- 

Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.


  reply	other threads:[~2010-10-28 18:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 21:58 [PATCH] msm: fix debug-macro.S build failure Daniel Walker
2010-10-27 22:14 ` Russell King - ARM Linux
2010-10-27 22:25   ` [PATCH -v2] " Daniel Walker
2010-10-28  2:30   ` [PATCH] " Nicolas Pitre
2010-10-28 16:30     ` Daniel Walker
2010-10-28 16:35       ` Russell King - ARM Linux
2010-10-28 16:41         ` Daniel Walker
2010-10-28 17:46           ` Russell King - ARM Linux
2010-10-28 18:00             ` Daniel Walker [this message]
2010-10-28 18:24               ` Nicolas Pitre
2010-10-28 18:27                 ` Daniel Walker
2010-10-28 18:29                   ` Russell King - ARM Linux
2010-10-28 18:46                     ` Nicolas Pitre
2010-10-28 18:40                   ` Nicolas Pitre
2010-10-28 18:28                 ` Russell King - ARM Linux
2010-10-28 18:43                   ` Nicolas Pitre
2010-10-28 18:46                     ` Russell King - ARM Linux
2010-10-29  3:03                       ` Nicolas Pitre
2010-10-29 21:17                         ` Daniel Walker
2010-10-29 22:14                           ` Russell King - ARM Linux
2010-10-29 22:21                             ` Daniel Walker
2010-10-29 22:28                               ` Russell King - ARM Linux
2010-10-29 23:06                             ` [PATCH -v3] " Daniel Walker
2010-10-29 22:17                           ` [PATCH] " Nicolas Pitre
2010-10-29 22:32                             ` Daniel Walker
2010-10-29 22:53                               ` Nicolas Pitre
2010-10-29 23:07                                 ` Daniel Walker
2010-11-05 21:31                                   ` David Brown
2010-10-28 22:36             ` Rohit Vaswani
2010-10-29  2:26               ` Nicolas Pitre

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=1288288824.2683.24.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --cc=jason77.wang@gmail.com \
    --cc=jeremy.kerr@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=nico@fluxnic.net \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).