mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: lee@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
	linux-kernel@vger.kernel.org, srini@kernel.org,
	krzk+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: mfd: qnap,ts433-mcu: allow nvmem-layout child node
Date: Wed, 30 Jul 2025 19:18:58 -0500	[thread overview]
Message-ID: <175392113764.1943443.12684318546344832887.robh@kernel.org> (raw)
In-Reply-To: <20250730172248.1875122-2-heiko@sntech.de>


On Wed, 30 Jul 2025 19:22:47 +0200, Heiko Stuebner wrote:
> The MCU has an eeprom memory connected internally, that for example
> contains some mac-addresses for the soc gmac controllers.
> 
> Therefore allow defining the nvmem-layout for the eeprom.
> 
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
>  Documentation/devicetree/bindings/mfd/qnap,ts433-mcu.yaml | 3 +++
>  1 file changed, 3 insertions(+)
> 

Acked-by: Rob Herring (Arm) <robh@kernel.org>


  reply	other threads:[~2025-07-31  0:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30 17:22 [PATCH 0/2] qnap-mcu: add nvmem subdevice to read the eeprom Heiko Stuebner
2025-07-30 17:22 ` [PATCH 1/2] dt-bindings: mfd: qnap,ts433-mcu: allow nvmem-layout child node Heiko Stuebner
2025-07-31  0:18   ` Rob Herring (Arm) [this message]
2025-07-31 13:47   ` (subset) " Lee Jones
2025-07-31 13:48     ` Lee Jones
2025-07-30 17:22 ` [PATCH 2/2] nvmem: add driver for the eeprom in qnap-mcu controllers Heiko Stuebner
2025-09-09  5:51   ` Srinivas Kandagatla
2025-09-11  8:41     ` Lee Jones
2025-09-11  8:48       ` Heiko Stübner
2025-09-11 14:44         ` Lee Jones
2025-08-18  6:41 ` (subset) [PATCH 0/2] qnap-mcu: add nvmem subdevice to read the eeprom Srinivas Kandagatla

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=175392113764.1943443.12684318546344832887.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srini@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®