linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Liang He" <windhl@126.com>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>
Subject: Re:Re: [PATCH] mips/kernel: Add missing of_node_get()
Date: Wed, 22 Jun 2022 15:12:23 +0800 (CST)	[thread overview]
Message-ID: <1c4b317a.4aad.1818a41483c.Coremail.windhl@126.com> (raw)
In-Reply-To: <CAMuHMdUiZSqGY2xbosDBCxcvMej6ir8sDfuOk9qfXTzJPh6ZOw@mail.gmail.com>



At 2022-06-22 14:56:32, "Geert Uytterhoeven" <geert@linux-m68k.org> wrote:
>Hi Liang,
>
>CC devicetree
>
>On Wed, Jun 22, 2022 at 8:08 AM Liang He <windhl@126.com> wrote:
>> In mips_cpc_default_phys_base(), we need to add of_node_get() before
>> of_find_compatible_node() which will decrease the refcount of its
>> first arg.
>>
>> Signed-off-by: Liang He <windhl@126.com>
>
>Thanks for your patch!
>
>> --- a/arch/mips/kernel/mips-cpc.c
>> +++ b/arch/mips/kernel/mips-cpc.c
>> @@ -25,6 +25,7 @@ phys_addr_t __weak mips_cpc_default_phys_base(void)
>>         struct resource res;
>>         int err;
>>
>> +       of_node_get(of_root);
>
>Adding this looks strange to me...
>

Hi, this is also strange to me.

In fact, I also don't like add a special of_node_get() before I call of_find_xx() each time.

In fact, I have learned this error-pattern based on the following bug-fix:

https://lore.kernel.org/all/20200720152806.443262648@linuxfoundation.org/


>However, of_find_compatible_node() indeed calls of_node_put(from),
>so your patch is correct.
>

Thanks.

>However, when passed NULL as the from pointer, __of_find_all_nodes()
>(expanded from for_each_of_allnodes_from()) turns this into of_root.
>As of_find_compatible_node() still has the original (NULL) from
>pointer, of_node_put(from) becomes a no-op.
>
>>         cpc_node = of_find_compatible_node(of_root, NULL, "mti,mips-cpc");
>
>Hence I think it would be better to change the above to
>
>    cpc_node = of_find_compatible_node(NULL, NULL, "mti,mips-cpc");
>
>instead, i.e. get rid of the explicit of_root handling?
>
>>         if (cpc_node) {
>>                 err = of_address_to_resource(cpc_node, 0, &res);
>


Sorry, Geert.

As I don't know anyother details of the code except the error-pattern code,
I cannot do anyother (more efficient) changes.

If it is a bug, please fix it in your professional way if my patch is not so well.

Thanks.

Liang.

>Gr{oetje,eeting}s,
>
>                        Geert
>
>--
>Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
>In personal conversations with technical people, I call myself a hacker. But
>when I'm talking to journalists I just say "programmer" or something like that.
>                                -- Linus Torvalds

      reply	other threads:[~2022-06-22  7:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  6:08 [PATCH] mips/kernel: Add missing of_node_get() Liang He
2022-06-22  6:56 ` Geert Uytterhoeven
2022-06-22  7:12   ` Liang He [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=1c4b317a.4aad.1818a41483c.Coremail.windhl@126.com \
    --to=windhl@126.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.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;
as well as URLs for NNTP newsgroup(s).