From: Paul Bolle <pebolle@tiscali.nl>
To: Steven Miao <realmz6@gmail.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
Michael Hennerich <michael.hennerich@analog.com>,
adi-buildroot-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Blackfin: bf537: rename ad2s120x ->ad2s1200
Date: Thu, 13 Feb 2014 11:54:35 +0100 [thread overview]
Message-ID: <1392288875.30853.54.camel@x220> (raw)
In-Reply-To: <1365073330.1830.34.camel@x61.thuisdomein>
[Replaced previous maintainer and list with current maintainer and
list.]
On Thu, 2013-04-04 at 13:02 +0200, Paul Bolle wrote:
> In v3.2 the Analog Devices ad2s1200/ad2s1205 driver was renamed from
> ad2s120x to ad2s1200. But it apparently forgot to rename the references
> to this driver in the BF537-STAMP code. Rename these now, and use the
> IS_ENABLED() macro, while we're at it.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
This issue is also still present in v3.14-rc2. Can someone please have a
look at this patch?
> 0) Also untested. The ".modalias" change is educated guesswork.
>
> 1) See commit 10e4a52b6e471cea2e87e71f8708a8c8c6b75266
> ("staging:iio:resolver rename ad2s120x ->ad2s1200") for the commit that
> started all this.
>
> arch/blackfin/mach-bf537/boards/stamp.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/arch/blackfin/mach-bf537/boards/stamp.c b/arch/blackfin/mach-bf537/boards/stamp.c
> index 9735345..e6fdc2a 100644
> --- a/arch/blackfin/mach-bf537/boards/stamp.c
> +++ b/arch/blackfin/mach-bf537/boards/stamp.c
> @@ -654,13 +654,13 @@ static struct bfin5xx_spi_chip ad2s90_spi_chip_info = {
> };
> #endif
>
> -#if defined(CONFIG_AD2S120X) || defined(CONFIG_AD2S120X_MODULE)
> -static unsigned short ad2s120x_platform_data[] = {
> +#if IS_ENABLED(CONFIG_AD2S1200)
> +static unsigned short ad2s1200_platform_data[] = {
> /* used as SAMPLE and RDVEL */
> GPIO_PF5, GPIO_PF6, 0
> };
>
> -static struct bfin5xx_spi_chip ad2s120x_spi_chip_info = {
> +static struct bfin5xx_spi_chip ad2s1200_spi_chip_info = {
> .enable_dma = 0,
> };
> #endif
> @@ -1018,13 +1018,13 @@ static struct spi_board_info bfin_spi_board_info[] __initdata = {
> },
> #endif
>
> -#if defined(CONFIG_AD2S120X) || defined(CONFIG_AD2S120X_MODULE)
> +#if IS_ENABLED(CONFIG_AD2S1200)
> {
> - .modalias = "ad2s120x",
> + .modalias = "ad2s1200",
> .bus_num = 0,
> .chip_select = 4, /* CS, change it for your board */
> - .platform_data = ad2s120x_platform_data,
> - .controller_data = &ad2s120x_spi_chip_info,
> + .platform_data = ad2s1200_platform_data,
> + .controller_data = &ad2s1200_spi_chip_info,
> },
> #endif
>
This should be the last Kconfig related issue that I reported last year,
but was never fixed. I'm haven't checked what else lurks in blackfin.
Let's first see how these issues get resolved.
Thanks,
Paul Bolle
prev parent reply other threads:[~2014-02-13 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 11:02 Paul Bolle
2014-02-13 10:54 ` Paul Bolle [this message]
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=1392288875.30853.54.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=realmz6@gmail.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
all inboxes | Powered by JetHome®