All of lore.kernel.org
 help / color / mirror / Atom feed
From: viresh.kumar@st.com (viresh kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] using amba_pl08x driver for s3c64xx SoCs
Date: Mon, 8 Aug 2011 09:55:52 +0530	[thread overview]
Message-ID: <4E3F6550.6010204@st.com> (raw)
In-Reply-To: <CACRpkdaYxbgqYZZSgRJmfBDWPyp-SQrviK50UvHrkTCO=B=6NQ@mail.gmail.com>

On 08/05/2011 06:49 PM, Linus Walleij wrote:
> Alter pl08x_phy_channel_busy() to return false immediately if
> ch->serving == NULL?
> 
> Please make a separate patch for this, since it's an obvious bug that
> should be fixed ASAP.

On 08/08/2011 09:39 AM, viresh kumar wrote:
> Sorry, but i couldn't get why will we get a crash here.
> 
> pl08x_phy_channel_busy() looks like this:
> 
> static int pl08x_phy_channel_busy(struct pl08x_phy_chan *ch)
> {
> 	unsigned int val;
> 
> 	val = readl(ch->base + PL080_CH_CONFIG);
> 	return val & PL080_CONFIG_ACTIVE;
> }
> 
> ch->base is already initialized and clock is enabled by amba layer.
> 
> Sorry if I am missing something Obvious.

Sorry, i saw your patch now only. So you have updated this routine and now
occurs a new issue.

@Linus: The bug isn't present currently, but is introduced with Alim's patch only.
So probably he isn't required to send this change separately, but can include this
in his patch only. What do you say?

-- 
viresh

  reply	other threads:[~2011-08-08  4:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGOxZ50Rz3ynmkuoJb9Pgc0b1pG++-CB9kUtU92zKYtfP3jtRg@mail.gmail.com>
2011-08-05  8:48 ` [RFC] using amba_pl08x driver for s3c64xx SoCs Linus Walleij
2011-08-05 11:10   ` Alim Akhtar
2011-08-05 13:19     ` Linus Walleij
2011-08-08  4:25       ` viresh kumar [this message]
2011-08-08  4:51         ` Alim Akhtar
2011-08-11 15:04           ` Linus Walleij
2011-08-08  4:09     ` viresh kumar

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=4E3F6550.6010204@st.com \
    --to=viresh.kumar@st.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.