From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 1/4] clk: imx: add Kconfig entry for i.MX8MM
Date: Tue, 13 Aug 2019 11:41:16 +0200 [thread overview]
Message-ID: <20190813114116.5e4e36f7@jawa> (raw)
In-Reply-To: <AM0PR04MB44817127A3604C5D1B73717188D20@AM0PR04MB4481.eurprd04.prod.outlook.com>
On Tue, 13 Aug 2019 09:07:03 +0000
Peng Fan <peng.fan@nxp.com> wrote:
> Hi Lukasz,
>
> > Subject: Re: [PATCH V3 1/4] clk: imx: add Kconfig entry for i.MX8MM
> >
> > Hi Peng,
> >
> > On Fri, Aug 9, 2019 at 5:02 AM Peng Fan <peng.fan@nxp.com> wrote:
> > >
> > > Add Kconfig entry for i.MX8MM
> > >
> > > Signed-off-by: Peng Fan <peng.fan@nxp.com>
> > > ---
> > > drivers/clk/Kconfig | 4 ++--
> > > drivers/clk/imx/Kconfig | 16 ++++++++++++++++
> > > 2 files changed, 18 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig index
> > > a3f0171b45..fce595b4b3 100644
> > > --- a/drivers/clk/Kconfig
> > > +++ b/drivers/clk/Kconfig
> > > @@ -48,7 +48,7 @@ config CLK_BOSTON
> > >
> > > config SPL_CLK_CCF
> > > bool "SPL Common Clock Framework [CCF] support "
> > > - depends on SPL_CLK_IMX6Q
> > > + depends on SPL_CLK_IMX6Q || ARCH_IMX8M
> >
> > I am wondering why this depends on i.MX. Shouldn't it be SoC
> > agnostic?
>
> Are you ok to expose the Kconfig for all with remove the depends on?
>
If it doesn't harm other SoCs I'm fine with it (but please check it
first).
I will review those patches tonight, or tomorrow morning.
> Thanks
> Peng
>
> >
> > > help
> > > Enable this option if you want to (re-)use the Linux
> > > kernel's
> > Common
> > > Clock Framework [CCF] code in U-Boot's SPL.
> > > @@ -62,7 +62,7 @@ config SPL_CLK_COMPOSITE_CCF
> > >
> > > config CLK_CCF
> > > bool "Common Clock Framework [CCF] support "
> > > - depends on CLK_IMX6Q || SANDBOX_CLK_CCF
> > > + depends on CLK_IMX6Q || ARCH_IMX8M || SANDBOX_CLK_CCF
> >
> > Same here.
> >
> > It doesn't look like a good idea to keep expanding this Kconfig
> > every time a new SoC wants to use the CCF.
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190813/18d9ae75/attachment.sig>
next prev parent reply other threads:[~2019-08-13 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 8:02 [U-Boot] [PATCH V3 0/4] Prepare i.MX8MM clk Peng Fan
2019-08-09 8:02 ` [U-Boot] [PATCH V3 1/4] clk: imx: add Kconfig entry for i.MX8MM Peng Fan
2019-08-09 8:56 ` Ye Li
2019-08-09 16:50 ` Fabio Estevam
2019-08-13 9:07 ` Peng Fan
2019-08-13 9:41 ` Lukasz Majewski [this message]
2019-08-09 8:02 ` [U-Boot] [PATCH V3 2/4] clk: imx: add pll14xx driver Peng Fan
2019-08-09 9:05 ` Ye Li
2019-08-09 16:51 ` Fabio Estevam
2019-08-09 8:02 ` [U-Boot] [PATCH V3 3/4] clk: imx: add i.MX8M composite clk support Peng Fan
2019-08-09 9:08 ` Ye Li
2019-08-09 16:59 ` Fabio Estevam
2019-08-13 9:37 ` Peng Fan
2019-08-09 8:02 ` [U-Boot] [PATCH V3 4/4] clk: imx: add i.MX8MM clk driver Peng Fan
2019-08-09 9:10 ` Ye Li
2019-08-09 21:02 ` Fabio Estevam
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=20190813114116.5e4e36f7@jawa \
--to=lukma@denx.de \
--cc=u-boot@lists.denx.de \
/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