From: Paul Bolle <pebolle@tiscali.nl>
To: Filip Brozovic <fbrozovic@gmail.com>
Cc: scottwood@freescale.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] powerpc/83xx: add support for mpc8306
Date: Fri, 03 Apr 2015 14:01:27 +0200 [thread overview]
Message-ID: <1428062487.7898.12.camel@x220> (raw)
In-Reply-To: <1428057856-26421-1-git-send-email-fbrozovic@gmail.com>
On Fri, 2015-04-03 at 12:44 +0200, Filip Brozovic wrote:
> --- a/arch/powerpc/platforms/83xx/Kconfig
> +++ b/arch/powerpc/platforms/83xx/Kconfig
> +# used for gpio
> +config PPC_MPC830x
> + bool
> + select ARCH_WANT_OPTIONAL_GPIOLIB
> +
> +config PPC_MPC8306
> + bool
To me these two new Kconfig symbols look pointless:
- they have no prompt, so one cannot set them manually;
- no other Kconfig symbol selects them;
- they do not default to 'y'.
I'm not aware of a way to set these symbols to 'y' outside of those
three. Is there perhaps a way for kconfig to set these symbols to 'y'
that I have missed?
Or do you expect to do one of these three things in a separate patch?
> --- a/arch/powerpc/platforms/83xx/usb.c
> +++ b/arch/powerpc/platforms/83xx/usb.c
> @@ -99,7 +99,7 @@ int mpc834x_usb_cfg(void)
> }
> #endif /* CONFIG_PPC_MPC834x */
>
> -#ifdef CONFIG_PPC_MPC831x
> +#if defined(CONFIG_PPC_MPC8306) || defined(CONFIG_PPC_MPC831x)
> int mpc831x_usb_cfg(void)
> {
> u32 temp;
So I think this hunk is pointless.
> @@ -210,7 +218,7 @@ out:
> of_node_put(np);
> return ret;
> }
> -#endif /* CONFIG_PPC_MPC831x */
> +#endif /* CONFIG_PPC_MPC8306 || CONFIG_PPC_MPC831x */
>
> #ifdef CONFIG_PPC_MPC837x
> int mpc837x_usb_cfg(void)
Ditto.
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index c1e2ca3..4c60e7f 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -217,11 +217,11 @@ config GPIO_MPC5200
>
> config GPIO_MPC8XXX
> bool "MPC512x/MPC8xxx GPIO support"
> - depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
> - FSL_SOC_BOOKE || PPC_86xx
> + depends on PPC_MPC512x || PPC_MPC830x || PPC_MPC831x || PPC_MPC834x || \
> + PPC_MPC837x || FSL_SOC_BOOKE || PPC_86xx
> help
> Say Y here if you're going to use hardware that connects to the
> - MPC512x/831x/834x/837x/8572/8610 GPIOs.
> + MPC512x/830x/831x/834x/837x/8572/8610 GPIOs.
>
> config GPIO_MSM_V1
> tristate "Qualcomm MSM GPIO v1"
Ditto (except for the help change, which still might make sense).
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-04-03 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 10:44 [PATCH v2] powerpc/83xx: add support for mpc8306 Filip Brozovic
2015-04-03 12:01 ` Paul Bolle [this message]
2015-04-03 12:45 ` Filip Brozović
2015-04-03 20:24 ` Scott Wood
2015-04-08 12:24 ` Filip Brozović
2015-04-03 21:31 ` Paul Bolle
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=1428062487.7898.12.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=fbrozovic@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).