From: <Hari.PrasathGE@microchip.com>
To: <robh@kernel.org>, <claudiu.beznea@tuxon.dev>, <arnd@arndb.de>,
<gregkh@linuxfoundation.org>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] misc: atmel-ssc: Use of_property_present() for non-boolean properties
Date: Tue, 5 Nov 2024 12:53:18 +0000 [thread overview]
Message-ID: <4b297a3e-d59e-4768-b482-8ed15d79c220@microchip.com> (raw)
In-Reply-To: <20241104190700.275573-1-robh@kernel.org>
On 11/5/24 12:36 AM, Rob Herring (Arm) wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> The use of of_property_read_bool() for non-boolean properties is
> deprecated in favor of of_property_present() when testing for property
> presence.
>
Thank you for the patch.
Reviewed-by: Hari Prasath Gujulan Elango <hari.prasathge@microchip.com>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> drivers/misc/atmel-ssc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/misc/atmel-ssc.c b/drivers/misc/atmel-ssc.c
> index 6eac0f335915..1d0322dfaf79 100644
> --- a/drivers/misc/atmel-ssc.c
> +++ b/drivers/misc/atmel-ssc.c
> @@ -153,7 +153,7 @@ static int ssc_sound_dai_probe(struct ssc_device *ssc)
>
> ssc->sound_dai = false;
>
> - if (!of_property_read_bool(np, "#sound-dai-cells"))
> + if (!of_property_present(np, "#sound-dai-cells"))
> return 0;
>
> id = of_alias_get_id(np, "ssc");
> @@ -176,7 +176,7 @@ static void ssc_sound_dai_remove(struct ssc_device *ssc)
> #else
> static inline int ssc_sound_dai_probe(struct ssc_device *ssc)
> {
> - if (of_property_read_bool(ssc->pdev->dev.of_node, "#sound-dai-cells"))
> + if (of_property_present(ssc->pdev->dev.of_node, "#sound-dai-cells"))
> return -ENOTSUPP;
>
> return 0;
> --
> 2.45.2
>
>
prev parent reply other threads:[~2024-11-05 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 19:06 Rob Herring (Arm)
2024-11-05 12:53 ` Hari.PrasathGE [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=4b297a3e-d59e-4768-b482-8ed15d79c220@microchip.com \
--to=hari.prasathge@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@tuxon.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®