From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Johan Hovold <johan@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] gnss: ubx: add support for the reset gpio
Date: Mon, 6 Nov 2023 21:06:05 +0100 [thread overview]
Message-ID: <ZUlHLZ1mm9IpSPal@ninjato> (raw)
In-Reply-To: <ZUj3fzArgPU4kYYT@hovoldconsulting.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
> 1.5 I/O pins
> RESET_N: Reset input
> Driving RESET_N low activates a hardware reset of the system.
> Use this pin only to reset the module. Do not use RESET_N to
> turn the module on and off, since the reset state increases
> power consumption.
>
> (and AFAIU you should generally not try to use reset this way unless it
> is explicitly said to be supported).
Oh! That's the opposite of my intention :/ Okay, today I learnt
something. Thank you for pointing this out. I will remember this and
double check reset handling in the future.
That means I only need to de-assert reset in probe() for now, right?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-11-06 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 22:55 [PATCH v4 0/3] gnss: ubx: support the reset pin of the Neo-M8 variant Wolfram Sang
2023-11-03 22:55 ` [PATCH v4 1/3] gnss: ubx: use new helper to remove open coded regulator handling Wolfram Sang
2023-11-03 22:55 ` [PATCH v4 2/3] dt-bindings: gnss: u-blox: add "reset-gpios" binding Wolfram Sang
2023-11-03 22:56 ` [PATCH v4 3/3] gnss: ubx: add support for the reset gpio Wolfram Sang
2023-11-06 14:26 ` Johan Hovold
2023-11-06 20:06 ` Wolfram Sang [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=ZUlHLZ1mm9IpSPal@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=geert+renesas@glider.be \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.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