From: Chee, Tien Fong <tien.fong.chee@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 04/10] arm: socfpga: arria10: Added clock manager and pin mux compat macro
Date: Mon, 19 Dec 2016 04:10:17 +0000 [thread overview]
Message-ID: <1482120617.2382.10.camel@intel.com> (raw)
In-Reply-To: <e87c792f-8472-8c0e-bd35-c261fdbd838f@denx.de>
On Rab, 2016-12-07 at 14:54 +0100, Marek Vasut wrote:
> On 12/07/2016 11:48 AM, Chee, Tien Fong wrote:
> >
> > On Sel, 2016-12-06 at 13:49 +0100, Marek Vasut wrote:
> > >
> > > On 12/06/2016 08:52 AM, Chee Tien Fong wrote:
> > > >
> > > >
> > > > From: Tien Fong Chee <tien.fong.chee@intel.com>
> > > >
> > > > These compat macros would be used by clock manager and pin mux
> > > > drivers
> > > > to look the required HW info from DTS for hardware
> > > > initialization.
> > > >
> > > > Signed-off-by: Tien Fong Chee <tien.fong.chee@intel.com>
> > > > Cc: Marek Vasut <marex@denx.de>
> > > > Cc: Dinh Nguyen <dinguyen@kernel.org>
> > > > Cc: Chin Liang See <chin.liang.see@intel.com>
> > > > Cc: Tien Fong <skywindctf@gmail.com>
> > > > ---
> > > > ?include/fdtdec.h |????8 ++++++++
> > > > ?lib/fdtdec.c?????|????2 ++
> > > > ?2 files changed, 10 insertions(+), 0 deletions(-)
> > > >
> > > > diff --git a/include/fdtdec.h b/include/fdtdec.h
> > > > index 27887c8..68cb199 100644
> > > > --- a/include/fdtdec.h
> > > > +++ b/include/fdtdec.h
> > > > @@ -155,6 +155,14 @@ enum fdt_compat_id {
> > > > ? COMPAT_INTEL_BAYTRAIL_FSP_MDP, /* Intel FSP
> > > > memory-
> > > > down params */
> > > > ? COMPAT_INTEL_IVYBRIDGE_FSP, /* Intel Ivy Bridge
> > > > FSP
> > > > */
> > > > ? COMPAT_SUNXI_NAND, /* SUNXI NAND
> > > > controller
> > > > */
> > > > + COMPAT_ALTERA_SOCFPGA_CLK, /* SoCFPGA Clock
> > > > initialization */
> > > > + COMPAT_ALTERA_SOCFPGA_PINCTRL_SINGLE, /*
> > > > pinctrl-
> > > > single */
> > > > + COMPAT_ALTERA_SOCFPGA_H2F_BRG, /*
> > > > Arria10
> > > > hps2fpga bridge */
> > > > + COMPAT_ALTERA_SOCFPGA_LWH2F_BRG, /* Arria10
> > > > lwhps2fpga bridge */
> > > > + COMPAT_ALTERA_SOCFPGA_F2H_BRG, /*
> > > > Arria10
> > > > fpga2hps bridge */
> > > > + COMPAT_ALTERA_SOCFPGA_F2SDR0, /*
> > > > Arria10
> > > > fpga2SDRAM0 bridge */
> > > > + COMPAT_ALTERA_SOCFPGA_F2SDR1, /*
> > > > Arria10
> > > > fpga2SDRAM1 bridge */
> > > > + COMPAT_ALTERA_SOCFPGA_F2SDR2, /*
> > > > Arria10
> > > > fpga2SDRAM2 bridge */
> > > Is all of this needed ? You're only adding two entries in the
> > > FDTDEC
> > > below.
> > >
> > This is to avoid compilation error, we have some functions ported
> > from
> > our internal branch, which using above COMPAT macro. Soon, in
> > upcoming
> > patches, we will need those functions and more entries will be
> > added
> > into FDTDEC below.
> You can add the compat strings when you really need them. Still, with
> DM, you shouldn't even need them AFAIK.
>
We have some drivers in these series of patches contain some COMPAT
strings, without these compact strings, the compilation would fail due
to error compact string is not defined. I think having compact string
would giving us flexbility to put our nodes where we want without
worrying to break our existing codes?
> >
> > >
> > > >
> > > >
> > > > ?
> > > > ? COMPAT_COUNT,
> > > > ?};
> > > > diff --git a/lib/fdtdec.c b/lib/fdtdec.c
> > > > index 4defb90..09a1db4 100644
> > > > --- a/lib/fdtdec.c
> > > > +++ b/lib/fdtdec.c
> > > > @@ -66,6 +66,8 @@ static const char * const
> > > > compat_names[COMPAT_COUNT] = {
> > > > ? COMPAT(INTEL_BAYTRAIL_FSP_MDP, "intel,baytrail-fsp-
> > > > mdp"),
> > > > ? COMPAT(INTEL_IVYBRIDGE_FSP, "intel,ivybridge-fsp"),
> > > > ? COMPAT(COMPAT_SUNXI_NAND, "allwinner,sun4i-a10-nand"),
> > > > + COMPAT(ALTERA_SOCFPGA_CLK, "altr,clk-mgr"),
> > > > + COMPAT(ALTERA_SOCFPGA_PINCTRL_SINGLE, "pinctrl-
> > > > single"),
> > > > ?};
> > > > ?
> > > > ?const char *fdtdec_get_compatible(enum fdt_compat_id id)
> > > >
>
next prev parent reply other threads:[~2016-12-19 4:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 7:52 [U-Boot] [PATCH 02/10] arm: socfpga: arria10: Added config option build for SPL Chee Tien Fong
2016-12-06 7:52 ` [U-Boot] [PATCH 03/10] arm: socfpga: arria10: Enhanced socfpga_arria10_defconfig to support SPL Chee Tien Fong
2016-12-06 12:48 ` Marek Vasut
2016-12-07 10:36 ` Chee, Tien Fong
2016-12-06 7:52 ` [U-Boot] [PATCH 04/10] arm: socfpga: arria10: Added clock manager and pin mux compat macro Chee Tien Fong
2016-12-06 12:49 ` Marek Vasut
2016-12-07 10:48 ` Chee, Tien Fong
2016-12-07 13:54 ` Marek Vasut
2016-12-19 4:10 ` Chee, Tien Fong [this message]
2016-12-19 7:55 ` Marek Vasut
2016-12-19 8:40 ` Chee, Tien Fong
2016-12-19 8:43 ` Marek Vasut
2016-12-19 8:54 ` Chee, Tien Fong
2016-12-19 10:04 ` Marek Vasut
2016-12-19 10:31 ` Chee, Tien Fong
2016-12-19 12:40 ` Marek Vasut
2016-12-06 12:47 ` [U-Boot] [PATCH 02/10] arm: socfpga: arria10: Added config option build for SPL Marek Vasut
2016-12-07 10:57 ` Chee, Tien Fong
2016-12-07 13:54 ` Marek Vasut
2016-12-09 9:46 ` Chee, Tien Fong
2016-12-09 13:02 ` Marek Vasut
2016-12-19 4:04 ` Chee, Tien Fong
2016-12-19 7:56 ` Marek Vasut
2016-12-19 8:41 ` Chee, Tien Fong
2016-12-19 8:44 ` Marek Vasut
2016-12-19 10:34 ` Chee, Tien Fong
2016-12-19 12:36 ` Marek Vasut
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=1482120617.2382.10.camel@intel.com \
--to=tien.fong.chee@intel.com \
--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 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.