Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Aiden Isik" <aidenisik@member.fsf.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwinfo: samsung,exynos-chipid: Add exynos5515 compatible
Date: Mon, 17 Aug 2026 10:16:57 +0000	[thread overview]
Message-ID: <20260817101658.75BE71F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260817-for-next-lucky7-chipid-v1-1-eb2908705c0d@member.fsf.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete support for Exynos 5515 causes driver probe failure
--

--- Patch [1]: [PATCH 1/2] dt-bindings: hwinfo: samsung,exynos-chipid: Add exynos5515 compatible ---
commit 5ce6d6fa94d63e1a87277e33f24686ff951995c4
Author: Aiden Isik <aidenisik@member.fsf.org>

dt-bindings: hwinfo: samsung,exynos-chipid: Add exynos5515 compatible

This commit adds the samsung,exynos5515-chipid compatible string to the
exynos-chipid device tree binding. It specifies that it should use the
samsung,exynos850-chipid compatible string as a fallback.

> diff --git a/Documentation/devicetree/bindings/hwinfo/samsung,exynos-chipid.yaml b/Documentation/devicetree/bindings/hwinfo/samsung,exynos-chipid.yaml
> index b9cdfe52b62ff..619faf33214bd 100644
> --- a/Documentation/devicetree/bindings/hwinfo/samsung,exynos-chipid.yaml
> +++ b/Documentation/devicetree/bindings/hwinfo/samsung,exynos-chipid.yaml
> @@ -25,6 +25,7 @@ properties:
>        - items:
>            - enum:
>                - samsung,exynos2200-chipid
> +              - samsung,exynos5515-chipid

[Severity: Medium]
Will this compatible string cause a probe failure on Exynos 5515 hardware?

Because this binding uses the samsung,exynos850-chipid fallback, the
exynos-chipid driver will attempt to probe on Exynos 5515 hardware.
However, if the Exynos 5515 product ID is not added to the soc_ids array
in drivers/soc/samsung/exynos-chipid.c, exynos_product_id_to_name() will
return NULL:

drivers/soc/samsung/exynos-chipid.c:exynos_chipid_probe() {
    ...
    soc_dev_attr->soc_id = exynos_product_id_to_name(soc_info.product_id);
    if (!soc_dev_attr->soc_id)
        return dev_err_probe(dev, -ENODEV, "Unknown SoC\n");
    ...
}

Does the driver need a companion patch to add the Exynos 5515 product ID
so that it can successfully probe rather than returning -ENODEV?

>                - samsung,exynos7885-chipid
>                - samsung,exynos8895-chipid
>                - samsung,exynos9610-chipid

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260817-for-next-lucky7-chipid-v1-0-eb2908705c0d@member.fsf.org?part=1

  reply	other threads:[~2026-08-17 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 10:11 [PATCH 0/2] Hi there, Aiden Isik via B4 Relay
2026-08-17 10:11 ` [PATCH 1/2] dt-bindings: hwinfo: samsung,exynos-chipid: Add exynos5515 compatible Aiden Isik via B4 Relay
2026-08-17 10:16   ` sashiko-bot [this message]
2026-08-17 11:05     ` Aiden Isik
2026-08-17 11:10   ` Krzysztof Kozlowski
2026-08-17 10:11 ` [PATCH 2/2] soc: samsung: exynos-chipid: Add exynos5515 SoC support Aiden Isik via B4 Relay

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=20260817101658.75BE71F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=aidenisik@member.fsf.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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