Linux IIO development
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Brajesh Patil <brajeshpatil11@gmail.com>, jic23@kernel.org
Cc: linux-iio@vger.kernel.org, marcelo.schmitt1@gmail.com
Subject: Re: Adding support for QMC5883L magnetometer to IIO subsystem
Date: Thu, 10 Apr 2025 10:10:10 -0500	[thread overview]
Message-ID: <22034f6d-f2ee-4792-a3c0-a5c0d69ef25f@baylibre.com> (raw)
In-Reply-To: <Z_UvBIsQ4rdIYTN8@brajesh-IdeaPad-3-15IAU7>

On 4/8/25 9:13 AM, Brajesh Patil wrote:
> I have a QMC5883L magnetometer module that I’ve been trying to integrate with my 
> Raspberry Pi using a kernel-space driver. While checking the mainline kernel, I 
> found that there is a driver for the HMC5883L (under the hmc5843 driver), but nothing 
> for QMC5883L.
> 
> I compared the datasheets for both devices and confirmed that they are not 
> register-compatible — the QMC5883L has a different I2C address and an entirely different 
> register map from the HMC5883L.
> 
> Given that this sensor is widely used (often as a drop-in replacement for the 
> now-discontinued HMC5883L), I was thinking of writing a new driver for it under the IIO 
> subsystem.
> 
> Would it make sense to move forward with this? If so, I’d appreciate any guidance or 
> suggestions from the community.
> 
> Thanks,  
> Brajesh 
> 
> 

Go for it. :-)

My advice for writing a new driver: Don't try to implement every feature in one
patch (or even one patch series). Just start with the most basic functionality.
Then add more features in separate patches as they are needed. (Devicetree
bindings are an exception and should be as complete as possible in the first
patch.)

  reply	other threads:[~2025-04-10 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 14:13 Adding support for QMC5883L magnetometer to IIO subsystem Brajesh Patil
2025-04-10 15:10 ` David Lechner [this message]
     [not found]   ` <CALJe6R3YfhdLKDVBZ=NgO+m64wHHqvFf5tt1T-2pWnr29wE94Q@mail.gmail.com>
2025-04-11 21:34     ` David Lechner

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=22034f6d-f2ee-4792-a3c0-a5c0d69ef25f@baylibre.com \
    --to=dlechner@baylibre.com \
    --cc=brajeshpatil11@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    /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