linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Martin Kepplinger <martin.kepplinger@puri.sm>
To: Pavel Machek <pavel@ucw.cz>
Cc: robh@kernel.org, kernel@puri.sm, Anson.Huang@nxp.com,
	devicetree@vger.kernel.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, angus@akkea.ca,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com,
	kernel@pengutronix.de, mchehab@kernel.org, festevam@gmail.com,
	agx@sigxcpu.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] arm64: dts: Add a device tree for the Librem5 phone
Date: Fri, 29 May 2020 20:20:54 +0200	[thread overview]
Message-ID: <c8cebbbf-8348-6ecb-306c-be124db04876@puri.sm> (raw)
In-Reply-To: <20200529180743.GA1081@bug>

On 29.05.20 20:07, Pavel Machek wrote:
> Hi!
> 
> Plus, do we need calibration matrix for magnetometer?

I guess so. It's not a calibration matrix, it's the mount matrix that
tells you how the chip is placed on the PCB relative to a "natural"
orientation, see
https://github.com/torvalds/linux/blob/master/Documentation/ABI/testing/sysfs-bus-iio#L1638

> 
> Best regards,
> 								Pavel
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-05-29 18:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 15:57 [PATCH 1/2] arm64: dts: Add a device tree for the Librem5 phone Martin Kepplinger
2020-05-14 15:57 ` [PATCH 2/2] MAINTAINERS: Add Purism Librem 5 section to the list Martin Kepplinger
2020-05-27  9:40   ` Marco Felsch
2020-05-27 19:40     ` Martin Kepplinger
2020-05-25  8:47 ` [PATCH 1/2] arm64: dts: Add a device tree for the Librem5 phone Martin Kepplinger
2020-05-26 11:39 ` Daniel Baluta
2020-05-27  9:35 ` Marco Felsch
2020-06-02 15:44   ` Martin Kepplinger
2020-05-29 16:28 ` Pavel Machek
2020-05-29 18:07   ` Pavel Machek
2020-05-29 18:20     ` Martin Kepplinger [this message]
2020-05-31 15:36   ` Guido Günther

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=c8cebbbf-8348-6ecb-306c-be124db04876@puri.sm \
    --to=martin.kepplinger@puri.sm \
    --cc=Anson.Huang@nxp.com \
    --cc=agx@sigxcpu.org \
    --cc=angus@akkea.ca \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=kernel@puri.sm \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).