From: Jakub Kicinski <kuba@kernel.org>
To: "Kolacinski, Karol" <karol.kolacinski@intel.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"G, GurucharanX" <gurucharanx.g@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH net-next 3/3] ice: add write functionality for GNSS TTY
Date: Thu, 23 Jun 2022 09:07:39 -0700 [thread overview]
Message-ID: <20220623090739.2ae8c14b@kernel.org> (raw)
In-Reply-To: <MW4PR11MB58003D5B00016D1F30E0DC0686B59@MW4PR11MB5800.namprd11.prod.outlook.com>
On Thu, 23 Jun 2022 13:39:35 +0000 Kolacinski, Karol wrote:
> On Mon, 23 May 2022 19:58 +0000 Jakub Kicinski wrote:
> > I meant discovered at the uAPI level. Imagine I plug in a shiny E810T
> > with a GNSS receiver into a box, the PRSNT_N bit is set and the driver
> > registered the ttys. How do I find the GNSS under /dev ?
>
> If the module is physically present, driver creates 2 TTYs for each supported
> device in /dev, ttyGNSS_<device>:<function>_0 and _1. First one (_0) is RW and
> the second one is RO.
> The protocol of write commands is dependent on the GNSS module as the driver
> writes raw bytes from the TTY to the GNSS i2c.
>
> I added this to Documentation/.
Sounds good, thanks!
next prev parent reply other threads:[~2022-06-23 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 21:19 [PATCH net-next 0/3][pull request] 100GbE Intel Wired LAN Driver Updates 2022-05-17 Tony Nguyen
2022-05-17 21:19 ` [PATCH net-next 1/3] ice: remove u16 arithmetic in ice_gnss Tony Nguyen
2022-05-17 21:19 ` [PATCH net-next 2/3] ice: add i2c write command Tony Nguyen
2022-05-19 13:40 ` Paolo Abeni
2022-05-23 17:02 ` Kolacinski, Karol
2022-05-17 21:19 ` [PATCH net-next 3/3] ice: add write functionality for GNSS TTY Tony Nguyen
2022-05-19 4:57 ` Jakub Kicinski
2022-05-23 16:56 ` Kolacinski, Karol
2022-05-23 17:58 ` Jakub Kicinski
2022-06-23 13:39 ` Kolacinski, Karol
2022-06-23 16:07 ` Jakub Kicinski [this message]
2022-05-19 13:45 ` Paolo Abeni
2022-05-23 16:58 ` Kolacinski, Karol
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=20220623090739.2ae8c14b@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gurucharanx.g@intel.com \
--cc=karol.kolacinski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@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;
as well as URLs for NNTP newsgroup(s).