linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: Matteo Facchinetti <matteo.facchinetti@sirius-es.it>
Cc: gregkh@linuxfoundation.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 3/3] powerpc/mpc512x: add platform code for MPC5125.
Date: Tue, 2 Apr 2013 12:38:39 +0200	[thread overview]
Message-ID: <20130402123839.612d18e6@crub> (raw)
In-Reply-To: <515AA9A2.1090100@sirius-es.it>

On Tue, 02 Apr 2013 11:49:22 +0200
Matteo Facchinetti <matteo.facchinetti@sirius-es.it> wrote:
...
> >          if (of_machine_is_compatible("fsl,mpc5121"))
> >                  return "fsl,mpc5121-psc";
> >
> >          if (of_machine_is_compatible("fsl,mpc5125"))
> >                  return "fsl,mpc5125-psc";
> >
> > but note that it will only work if we add these compatibles
> > to the compatible list of the root nodes in 5121 and 5125
> > device trees.
> 
> I agree with you.
> 
> But I don't like that:
> "fsl,mpc5121" is already present in <mpc5121.dtsi> and after its 
> inclusion in <mpc5121ads.dts> , compatible root node value is replaced 
> by "fsl,mpc5121ads".
> 
> Idea is automatically generate
>      compatible = "fsl,mpc5121", "fsl,mpc5121ads";
> using dtsi hierarchy.
> 
> Is there a way to extend compatible values instead of replace it?

Not that I am aware of. Note that the compatible list should
specify the compatibility from most specific to most general, so
the list in mpc5121ads.dts would look like

    compatible = "fsl,mpc5121ads", "fsl,mpc5121";

We can patch in-tree mpc512x dts files accordingly.

Thanks,

Anatolij

--
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0  Fax: +49-8142-66989-80 Email: office@denx.de

      reply	other threads:[~2013-04-02 10:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 17:41 [PATCH 0/3] Add MPC5125 platform support Matteo Facchinetti
2013-03-20 17:41 ` [PATCH 1/3] powerpc/512x: move mpc5121_generic platform to mpc512x_generic Matteo Facchinetti
2013-03-30 22:01   ` Anatolij Gustschin
2013-03-20 17:41 ` [PATCH 2/3] serial/mpc52xx_uart: add PSC UART support for MPC5125 platforms Matteo Facchinetti
2013-04-17 21:21   ` [PATCH v2 1/2] serial/mpc52xx_uart: prepare for adding MPC5125 PSC UART support Anatolij Gustschin
2013-04-17 21:21     ` [PATCH v2 2/2] serial/mpc52xx_uart: add MPC5125 PSC support Anatolij Gustschin
2013-05-24 17:49     ` [PATCH v2 1/2] serial/mpc52xx_uart: prepare for adding MPC5125 PSC UART support Anatolij Gustschin
2013-05-24 17:57       ` Greg Kroah-Hartman
2013-04-17 21:24   ` [PATCH 2/3] serial/mpc52xx_uart: add PSC UART support for MPC5125 platforms Anatolij Gustschin
2013-03-20 17:41 ` [PATCH 3/3] powerpc/mpc512x: add platform code for MPC5125 Matteo Facchinetti
2013-03-30 22:32   ` Anatolij Gustschin
2013-04-02  9:49     ` Matteo Facchinetti
2013-04-02 10:38       ` Anatolij Gustschin [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=20130402123839.612d18e6@crub \
    --to=agust@denx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=matteo.facchinetti@sirius-es.it \
    /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).