From: Grant Likely <grant.likely@secretlab.ca>
To: christophe leroy <christophe.leroy@c-s.fr>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
linux-kernel@vger.kernel.org,
spi-devel-general@lists.sourceforge.net,
Anton Vorontsov <avorontsov@ru.mvista.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] spi_mpc8xxx: issue with using definition of pram in Device Tree
Date: Fri, 24 Sep 2010 01:10:06 -0600 [thread overview]
Message-ID: <20100924071006.GA21318@angua.secretlab.ca> (raw)
In-Reply-To: <20100916070503.10046C7391@messagerie.si.c-s.fr>
On Thu, Sep 16, 2010 at 09:05:03AM +0200, christophe leroy wrote:
> This patch applies to 2.6.34.7 and 2.6.35.4
> It fixes an issue during the probe for CPM1 with definition of parameter ram from DTS
>
> Signed-off-by: christophe leroy <christophe.leroy@c-s.fr>
I'm sorry, I don't understand the fix from the given description.
What is the problem, and why is cpm_muram_alloc_fixed() the wrong
thing to call on CPM1? Does CPM2 still need it?
g.
>
> diff -urN b/drivers/spi/spi_mpc8xxx.c c/drivers/spi/spi_mpc8xxx.c
> --- b/drivers/spi/spi_mpc8xxx.c 2010-09-08 16:43:50.000000000 +0200
> +++ c/drivers/spi/spi_mpc8xxx.c 2010-09-08 16:44:03.000000000 +0200
> @@ -822,7 +822,7 @@
> if (!iprop || size != sizeof(*iprop) * 4)
> return -ENOMEM;
>
> - spi_base_ofs = cpm_muram_alloc_fixed(iprop[2], 2);
> + spi_base_ofs = iprop[2];
> if (IS_ERR_VALUE(spi_base_ofs))
> return -ENOMEM;
>
> @@ -844,7 +844,6 @@
> return spi_base_ofs;
> }
>
> - cpm_muram_free(spi_base_ofs);
> return pram_ofs;
> }
next prev parent reply other threads:[~2010-09-24 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 7:05 [PATCH] spi_mpc8xxx: issue with using definition of pram in Device Tree christophe leroy
2010-09-24 7:10 ` Grant Likely [this message]
2010-09-24 7:20 ` LEROY Christophe
2010-09-24 7:57 ` Anton Vorontsov
2010-09-24 15:12 ` Scott Wood
2010-09-24 15:07 ` Scott Wood
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=20100924071006.GA21318@angua.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=avorontsov@ru.mvista.com \
--cc=christophe.leroy@c-s.fr \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=spi-devel-general@lists.sourceforge.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).