From: Lee Jones <lee@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: jdelvare@suse.com, linux@roeck-us.net, dmitry.torokhov@gmail.com,
pavel@ucw.cz, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, ukleinek@debian.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-hwmon@vger.kernel.org,
linux-input@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v4 2/7] mfd: add base driver for qnap-mcu devices
Date: Thu, 22 Aug 2024 11:10:20 +0100 [thread overview]
Message-ID: <20240822101020.GG6858@google.com> (raw)
In-Reply-To: <2875938.88bMQJbFj6@diego>
On Sun, 18 Aug 2024, Heiko Stübner wrote:
> Hi Lee,
>
> thanks a lot for your review,
>
> Am Freitag, 16. August 2024, 19:13:36 CEST schrieb Lee Jones:
> > On Sat, 10 Aug 2024, Heiko Stuebner wrote:
>
>
> > > +/*
> > > + * MFD core driver for the MCU in Qnap NAS devices that is connected
> >
> > No such thing as an "MFD". Please describe the device.
> >
> > Is it QNAP or Qnap? Please be consistent.
>
> Looks like QNAP spells itself in all upper case on their website, so I did
> go with that
Super, thanks.
> > > +
> > > +/*
> > > + * The MCU controls power to the peripherals but not the CPU.
> > > + *
> > > + * So using the pmic to power off the system keeps the MCU and hard-drives
> > > + * running. This also then prevents the system from turning back on until
> > > + * the MCU is turned off by unplugging the power-cable.
> > > + * Turning off the MCU alone on the other hand turns off the hard-drives,
> > > + * LEDs, etc while the main SoC stays running - including its network ports.
> > > + */
> > > +static int qnap_mcu_power_off(struct sys_off_data *data)
> > > +{
> > > + struct qnap_mcu *mcu = data->cb_data;
> > > + int ret;
> > > + u8 cmd[] = {
> > > + [0] = 0x40, /* @ */
> > > + [1] = 0x43, /* C */
> > > + [2] = 0x30 /* 0 */
> > > + };
> >
> > u8 cmd [] = { '@', 'C', '0' }; ?
>
> see above.
>
> I guess this is a style choice, we could of course go with
> u8 cmd[] = { 0x40, 0x43, 0x30 }
> if you prefer that.
Yes please.
--
Lee Jones [李琼斯]
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: jdelvare@suse.com, linux@roeck-us.net, dmitry.torokhov@gmail.com,
pavel@ucw.cz, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, ukleinek@debian.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-hwmon@vger.kernel.org,
linux-input@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v4 2/7] mfd: add base driver for qnap-mcu devices
Date: Thu, 22 Aug 2024 11:10:20 +0100 [thread overview]
Message-ID: <20240822101020.GG6858@google.com> (raw)
In-Reply-To: <2875938.88bMQJbFj6@diego>
On Sun, 18 Aug 2024, Heiko Stübner wrote:
> Hi Lee,
>
> thanks a lot for your review,
>
> Am Freitag, 16. August 2024, 19:13:36 CEST schrieb Lee Jones:
> > On Sat, 10 Aug 2024, Heiko Stuebner wrote:
>
>
> > > +/*
> > > + * MFD core driver for the MCU in Qnap NAS devices that is connected
> >
> > No such thing as an "MFD". Please describe the device.
> >
> > Is it QNAP or Qnap? Please be consistent.
>
> Looks like QNAP spells itself in all upper case on their website, so I did
> go with that
Super, thanks.
> > > +
> > > +/*
> > > + * The MCU controls power to the peripherals but not the CPU.
> > > + *
> > > + * So using the pmic to power off the system keeps the MCU and hard-drives
> > > + * running. This also then prevents the system from turning back on until
> > > + * the MCU is turned off by unplugging the power-cable.
> > > + * Turning off the MCU alone on the other hand turns off the hard-drives,
> > > + * LEDs, etc while the main SoC stays running - including its network ports.
> > > + */
> > > +static int qnap_mcu_power_off(struct sys_off_data *data)
> > > +{
> > > + struct qnap_mcu *mcu = data->cb_data;
> > > + int ret;
> > > + u8 cmd[] = {
> > > + [0] = 0x40, /* @ */
> > > + [1] = 0x43, /* C */
> > > + [2] = 0x30 /* 0 */
> > > + };
> >
> > u8 cmd [] = { '@', 'C', '0' }; ?
>
> see above.
>
> I guess this is a style choice, we could of course go with
> u8 cmd[] = { 0x40, 0x43, 0x30 }
> if you prefer that.
Yes please.
--
Lee Jones [李琼斯]
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-08-22 10:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 18:47 [PATCH v4 0/7] Drivers to support the MCU on QNAP NAS devices Heiko Stuebner
2024-08-10 18:47 ` Heiko Stuebner
2024-08-10 18:47 ` [PATCH v4 1/7] dt-bindings: mfd: add binding for qnap,ts433-mcu devices Heiko Stuebner
2024-08-10 18:47 ` Heiko Stuebner
2024-08-12 16:11 ` Conor Dooley
2024-08-12 16:11 ` Conor Dooley
2024-08-10 18:47 ` [PATCH v4 2/7] mfd: add base driver for qnap-mcu devices Heiko Stuebner
2024-08-10 18:47 ` Heiko Stuebner
2024-08-16 17:13 ` Lee Jones
2024-08-16 17:13 ` Lee Jones
2024-08-18 21:15 ` Heiko Stübner
2024-08-18 21:15 ` Heiko Stübner
2024-08-22 10:10 ` Lee Jones [this message]
2024-08-22 10:10 ` Lee Jones
2024-08-10 18:47 ` [PATCH v4 3/7] leds: add driver for LEDs from " Heiko Stuebner
2024-08-10 18:47 ` Heiko Stuebner
2024-08-10 18:47 ` [PATCH v4 4/7] Input: add driver for the input part of " Heiko Stuebner
2024-08-10 18:47 ` Heiko Stuebner
2024-08-10 18:47 ` [PATCH v4 5/7] hwmon: add driver for the hwmon parts " Heiko Stuebner
2024-08-10 18:47 ` Heiko Stuebner
2024-08-13 16:03 ` Guenter Roeck
2024-08-13 16:03 ` Guenter Roeck
2024-08-13 20:39 ` Heiko Stübner
2024-08-13 20:39 ` Heiko Stübner
2024-08-10 18:47 ` [PATCH v4 6/7] arm64: dts: rockchip: hook up the MCU on the QNAP TS433 Heiko Stuebner
2024-08-10 18:47 ` Heiko Stuebner
2024-08-10 18:47 ` [PATCH v4 7/7] arm64: dts: rockchip: set hdd led labels on qnap-ts433 Heiko Stuebner
2024-08-10 18:47 ` Heiko Stuebner
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=20240822101020.GG6858@google.com \
--to=lee@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=heiko@sntech.de \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=ukleinek@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.