public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Brajesh Patil <brajeshpatil11@gmail.com>,
	jic23@kernel.org, lars@metafoo.de, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-iio@vger.kernel.org, marcelo.schmitt1@gmail.com
Subject: Re: [PATCH v2 0/5] iio: magnetometer: Add QMC5883L driver support
Date: Thu, 8 May 2025 10:26:13 -0500	[thread overview]
Message-ID: <a0b305dd-8eb5-412c-b9c8-d2b274707f66@baylibre.com> (raw)
In-Reply-To: <20250508120822.114060-1-brajeshpatil11@gmail.com>

On 5/8/25 7:08 AM, Brajesh Patil wrote:
> This series introduces support for the QST QMC5883L 3-axis magnetometer,
> a magnetic sensor with I2C interface.
> 
> The implementation follows standard IIO conventions and includes:
> 
> Patch 1/5: dt-bindings: vendor-prefixes
> - Adds 'qst' prefix for QST Corporation
> 
> Patch 2/5: dt-bindings: iio: magnetometer - Adds QMC5883L bindings
> - Adds compatible string and required properties
> - Includes example device tree node
> 
> Patch 3/5: iio: magnetometer - Base driver implementation
> - Basic register access via regmap
> - X/Y/Z axis and temperature readings
> - Triggered buffer support
> - Initialization and core functionality
> 
> Patch 4/5: Extended sysfs attributes and configuration
> - ODR (10-200Hz) and FSR (±2G/±8G) control
> - Mode selection (standby/continuous)
> - Oversampling ratio configuration (512-64)
> - Status monitoring (DRDY/OVL flags)
> - Available scale and sampling frequency attributes
> 
> Patch 5/5: Advanced features and power management
> - Mount matrix support for orientation compensation
> - Power management (suspend/resume)
> - Control register features (soft reset, pointer rollover)

This sort of information should be in the descriptions of the individual patches,
not in the cover letter.

> 
> The driver has been tested on a Raspberry Pi 5 and all features have been verified.

This info is good to have in the cover letter. Even better though would be to
explain a bit about the actual methodology of how you tested it.

Also, a v2 should have a link to v1 and describe the changes made since then.

It look like v2 was sent the same day as v1. Generally, you should wait a week
(or at least a few days) to give others time to review before sending a new
version. 

> 
> Signed-off-by: Brajesh Patil <brajeshpatil11@gmail.com>


  reply	other threads:[~2025-05-08 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 12:08 [PATCH v2 0/5] iio: magnetometer: Add QMC5883L driver support Brajesh Patil
2025-05-08 15:26 ` David Lechner [this message]
2025-05-11 15:16 ` Jonathan Cameron

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=a0b305dd-8eb5-412c-b9c8-d2b274707f66@baylibre.com \
    --to=dlechner@baylibre.com \
    --cc=brajeshpatil11@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --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