linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Sinan Akman <sinan@writeme.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Scott Wood <oss@buserror.net>, Paul Mackerras <paulus@samba.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 5/7] powerpc/85xx: p2020: Define just one machine description
Date: Mon, 26 Sep 2022 12:08:56 +0200	[thread overview]
Message-ID: <20220926100856.klwmxgujr7nv4qik@pali> (raw)
In-Reply-To: <638a2f98-5c23-85ba-c835-bce276312182@csgroup.eu>

On Monday 26 September 2022 10:02:47 Christophe Leroy wrote:
> > +static int __init p2020_probe(void)
> >   {
> > -	if (of_machine_is_compatible("fsl,P2020RDB-PC"))
> > -		return 1;
> > -	return 0;
> > +	struct device_node *p2020_cpu;
> > +
> > +	/*
> > +	 * There is no common compatible string for all P2020 boards.
> > +	 * The only common thing is "PowerPC,P2020@0" cpu node.
> > +	 * So check for P2020 board via this cpu node.
> > +	 */
> > +	p2020_cpu = of_find_node_by_path("/cpus/PowerPC,P2020@0");
> > +	if (!p2020_cpu)
> > +		return 0;
> 
> This looks odd. I though all probe were using the compatible, and in 
> fact I have a series in preparation that drops all 
> of_machine_is_compatible() checks in probe functions and do it in the 
> caller instead, after adding a .compatible string in the machine 
> description.
> 
> Is there really no compatible that can be used for all p2020 ?

Really. There is none. I have looked into all available P2020 DTB files
(either externals passed by bootloader or kernel in-tree) and there is
no common compatible string. The only "common" thing is cpu node, how I
implemented it int this patch series.

And same issue is with boards with P101x and P102x DTB files.

  reply	other threads:[~2022-09-26 10:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 19:15 [PATCH 0/7] powerpc/85xx: p2020: Create one unified machine description Pali Rohár
2022-08-19 19:15 ` [PATCH 1/7] powerpc/85xx: Mark mpc85xx_rdb_pic_init() as static Pali Rohár
2022-08-19 19:15 ` [PATCH 2/7] powerpc/85xx: Mark mpc85xx_ds_pic_init() " Pali Rohár
2022-09-26  9:43   ` Christophe Leroy
2022-09-26  9:47     ` Pali Rohár
2022-10-16 11:05       ` Pali Rohár
2022-10-16 16:59         ` Christophe Leroy
2022-11-01 23:25           ` Pali Rohár
2022-11-26 16:25             ` Pali Rohár
2022-12-02 18:46               ` Christophe Leroy
2022-08-19 19:15 ` [PATCH 3/7] powerpc/85xx: p2020: Move all P2020 machine descriptions to p2020.c Pali Rohár
2022-09-26  9:48   ` Christophe Leroy
2022-09-26  9:53     ` Pali Rohár
2022-09-26 10:17       ` Christophe Leroy
2022-09-26 10:26         ` Pali Rohár
2022-12-07 14:02           ` Christophe Leroy
2022-08-19 19:15 ` [PATCH 4/7] powerpc/85xx: p2020: Unify .setup_arch and .init_IRQ callbacks Pali Rohár
2022-09-26  9:59   ` Christophe Leroy
2022-08-19 19:15 ` [PATCH 5/7] powerpc/85xx: p2020: Define just one machine description Pali Rohár
2022-09-26 10:02   ` Christophe Leroy
2022-09-26 10:08     ` Pali Rohár [this message]
2022-08-19 19:15 ` [PATCH 6/7] powerpc/85xx: p2020: Enable boards by new config option CONFIG_P2020 Pali Rohár
2022-09-26 10:08   ` Christophe Leroy
2022-09-26 10:19     ` Pali Rohár
2022-08-19 19:15 ` [PATCH 7/7] powerpc: dts: turris1x.dts: Remove "fsl,P2020RDB-PC" compatible string Pali Rohár
2022-09-26 10:10   ` Christophe Leroy
2022-09-26 10:21     ` Pali Rohár
2022-09-24 12:42 ` [PATCH 0/7] powerpc/85xx: p2020: Create one unified machine description Pali Rohár
2022-12-04 10:54 ` Pali Rohár
2022-12-07 14:07   ` Christophe Leroy

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=20220926100856.klwmxgujr7nv4qik@pali \
    --to=pali@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oss@buserror.net \
    --cc=paulus@samba.org \
    --cc=sinan@writeme.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).