From: Johan Hovold <johan@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 4/5] gnss: ubx: add support for the reset gpio
Date: Tue, 20 Jun 2023 09:17:34 +0200 [thread overview]
Message-ID: <ZJFSjrf41PHe400c@hovoldconsulting.com> (raw)
In-Reply-To: <20230523064310.3005-5-wsa+renesas@sang-engineering.com>
On Tue, May 23, 2023 at 08:43:09AM +0200, Wolfram Sang wrote:
> Tested with a Renesas KingFisher board. The chip correctly disappears
> from the I2C bus when the 'gnss0' device is not opened.
What do you mean by "disappears from the I2C bus"?
Does this device support both I2C and UART?
Johan
next prev parent reply other threads:[~2023-06-20 7:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 6:43 [RFC PATCH 0/5] gnss: updates to support the Renesas KingFisher board Wolfram Sang
2023-05-23 6:43 ` [RFC PATCH 1/5] WIP: gnss: merge MTK driver into UBX driver Wolfram Sang
2023-06-12 11:35 ` Wolfram Sang
2023-06-20 7:13 ` Johan Hovold
2023-06-20 9:00 ` Wolfram Sang
2023-06-20 10:21 ` Wolfram Sang
2023-06-20 14:50 ` Johan Hovold
2023-05-23 6:43 ` [RFC PATCH 2/5] gnss: ubx: use new helper to remove open coded regulator handling Wolfram Sang
2023-06-20 8:48 ` Johan Hovold
2023-06-20 9:04 ` Wolfram Sang
2023-06-20 9:08 ` Johan Hovold
2023-05-23 6:43 ` [RFC PATCH 3/5] gnss: ubx: 'vcc' can be optional Wolfram Sang
2023-06-20 7:15 ` Johan Hovold
2023-06-20 9:04 ` Wolfram Sang
2023-05-23 6:43 ` [RFC PATCH 4/5] gnss: ubx: add support for the reset gpio Wolfram Sang
2023-06-20 7:17 ` Johan Hovold [this message]
2023-06-20 9:06 ` Wolfram Sang
2023-06-20 9:12 ` Johan Hovold
2023-06-20 9:41 ` Wolfram Sang
2023-06-20 10:05 ` Johan Hovold
2023-06-20 10:14 ` Wolfram Sang
2023-05-23 6:43 ` [RFC PATCH 5/5] arm64: dts: renesas: ulcb-kf: add node for GPS Wolfram Sang
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=ZJFSjrf41PHe400c@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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