From: Dimitri Fedrau <dima.fedrau@gmail.com>
To: "Uwe Kleine-König" <ukleinek@kernel.org>
Cc: dimitri.fedrau@liebherr.com, Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v3] pwm: mc33xs2410: add support for temperature sensors
Date: Tue, 24 Jun 2025 10:19:20 +0200 [thread overview]
Message-ID: <20250624081920.GA10327@legfed1> (raw)
In-Reply-To: <u4aigv7nhsqygisyrhcohq25tvktsukjexng6zddib6kvj6hwl@vaa2pset4qbi>
Am Tue, Jun 24, 2025 at 09:29:25AM +0200 schrieb Uwe Kleine-König:
> On Tue, Jun 24, 2025 at 09:04:42AM +0200, Dimitri Fedrau wrote:
> > Hi Uwe,
> >
> > Am Mon, Jun 23, 2025 at 11:07:24AM +0200 schrieb Uwe Kleine-König:
> > > hello Dimitri,
> > >
> > > On Thu, Jun 19, 2025 at 07:32:42PM +0200, Dimitri Fedrau via B4 Relay wrote:
> > > > @@ -29,6 +30,8 @@
> > > >
> > > > #include <linux/spi/spi.h>
> > > >
> > > > +/* ctrl registers */
> > > > +
> > > > #define MC33XS2410_GLB_CTRL 0x00
> > > > #define MC33XS2410_GLB_CTRL_MODE GENMASK(7, 6)
> > > > #define MC33XS2410_GLB_CTRL_MODE_NORMAL FIELD_PREP(MC33XS2410_GLB_CTRL_MODE, 1)
> > > > @@ -51,6 +54,21 @@
> > > >
> > > > #define MC33XS2410_WDT 0x14
> > > >
> > > > +#define MC33XS2410_TEMP_WT 0x29
> > > > +#define MC33XS2410_TEMP_WT_MASK GENMASK(7, 0)
> > > > +
> > > > +/* diag registers */
> > > > +
> > > > +/* chan in { 1 ... 4 } */
> > > > +#define MC33XS2410_OUT_STA(chan) (0x02 + (chan) - 1)
> > > > +#define MC33XS2410_OUT_STA_OTW BIT(8)
> > > > +
> > > > +#define MC33XS2410_TS_TEMP_DIE 0x26
> > > > +#define MC33XS2410_TS_TEMP_MASK GENMASK(9, 0)
> > >
> > > Keep the registers in address order please
> >
> > Aren't they ? There are "ctrl" and "diag" registers and I didn't mix up
> > adresses. There is a comment for each of them when defines start.
>
> +#define MC33XS2410_TEMP_WT 0x29
> ...
> +#define MC33XS2410_TS_TEMP_DIE 0x26
>
MC33XS2410_TEMP_WT is a "ctrl" register and MC33XS2410_TS_TEMP_DIE is a
"diag" register. Both register sets start with adress 0. "ctrl" and
"diag" defines are separated because I didn't want to mix them up.
[...]
Best regards,
Dimitri Fedrau
prev parent reply other threads:[~2025-06-24 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 17:32 [PATCH v3] pwm: mc33xs2410: add support for temperature sensors Dimitri Fedrau
2025-06-19 17:32 ` Dimitri Fedrau via B4 Relay
2025-06-23 9:07 ` Uwe Kleine-König
2025-06-23 13:52 ` Guenter Roeck
2025-06-24 7:04 ` Dimitri Fedrau
2025-06-24 7:29 ` Uwe Kleine-König
2025-06-24 8:19 ` Dimitri Fedrau [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=20250624081920.GA10327@legfed1 \
--to=dima.fedrau@gmail.com \
--cc=dimitri.fedrau@liebherr.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ukleinek@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 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.