From: Dan Williams <dcbw@redhat.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] In-kernel QMI handling
Date: Fri, 04 Aug 2017 10:36:07 -0500 [thread overview]
Message-ID: <1501860967.939.6.camel@redhat.com> (raw)
In-Reply-To: <20170804145938.25427-1-bjorn.andersson@linaro.org>
On Fri, 2017-08-04 at 07:59 -0700, Bjorn Andersson wrote:
> This series starts by moving the common definitions of the QMUX
> protocol to the
> uapi header, as they are shared with clients - both in kernel and
> userspace.
>
> This series then introduces in-kernel helper functions for aiding the
> handling
> of QMI encoded messages in the kernel. QMI encoding is a wire-format
> used in
> exchanging messages between the majority of QRTR clients and
> services.
This raises a few red-flags for me. So far, we've kept almost
everything QMI related in userspace and handled all QMI control-channel
messages from libraries like libqmi or uqmi via the cdc-wdm driver and
the "rmnet" interface via the qmi_wwan driver. The kernel drivers just
serve as the transport.
Can you describe what kinds of in-kernel drivers need to actually parse
QMI messages as part of their operation?
Dan
> It then adds an abstractions to reduce the duplication of common code
> in
> drivers that needs to query the name server and send and receive
> encoded
> messages to a remote service.
>
> Finally it introduces a sample implementation for showing QRTR and
> the QMI
> helpers in action. The sample device instantiates in response to
> finding the
> "test service" and implements the "test protocol".
>
> Bjorn Andersson (6):
> net: qrtr: Invoke sk_error_report() after setting sk_err
> net: qrtr: Move constants to header file
> net: qrtr: Add control packet definition to uapi
> soc: qcom: Introduce QMI encoder/decoder
> soc: qcom: Introduce QMI helpers
> samples: Introduce Qualcomm QRTR sample client
>
> drivers/soc/qcom/Kconfig | 8 +
> drivers/soc/qcom/Makefile | 3 +
> drivers/soc/qcom/qmi_encdec.c | 812
> ++++++++++++++++++++++++++++++++++++++
> drivers/soc/qcom/qmi_interface.c | 540 +++++++++++++++++++++++++
> include/linux/soc/qcom/qmi.h | 249 ++++++++++++
> include/uapi/linux/qrtr.h | 35 ++
> net/qrtr/qrtr.c | 16 +-
> samples/Kconfig | 8 +
> samples/Makefile | 2 +-
> samples/qrtr/Makefile | 1 +
> samples/qrtr/qrtr_sample_client.c | 603 ++++++++++++++++++++++++++++
> 11 files changed, 2261 insertions(+), 16 deletions(-)
> create mode 100644 drivers/soc/qcom/qmi_encdec.c
> create mode 100644 drivers/soc/qcom/qmi_interface.c
> create mode 100644 include/linux/soc/qcom/qmi.h
> create mode 100644 samples/qrtr/Makefile
> create mode 100644 samples/qrtr/qrtr_sample_client.c
>
next prev parent reply other threads:[~2017-08-04 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 14:59 [PATCH 0/6] In-kernel QMI handling Bjorn Andersson
2017-08-04 14:59 ` [PATCH 1/6] net: qrtr: Invoke sk_error_report() after setting sk_err Bjorn Andersson
2017-08-04 14:59 ` [PATCH 2/6] net: qrtr: Move constants to header file Bjorn Andersson
2017-08-04 14:59 ` [PATCH 3/6] net: qrtr: Add control packet definition to uapi Bjorn Andersson
2017-08-04 14:59 ` [PATCH 4/6] soc: qcom: Introduce QMI encoder/decoder Bjorn Andersson
2017-08-04 14:59 ` [PATCH 5/6] soc: qcom: Introduce QMI helpers Bjorn Andersson
2017-08-04 14:59 ` [PATCH 6/6] samples: Introduce Qualcomm QRTR sample client Bjorn Andersson
2017-08-04 15:36 ` Dan Williams [this message]
2017-08-07 17:38 ` [PATCH 0/6] In-kernel QMI handling Bjorn Andersson
2017-08-07 19:19 ` Marcel Holtmann
2017-08-08 4:45 ` Bjorn Andersson
2017-08-08 6:15 ` Marcel Holtmann
2017-08-08 11:02 ` Bjørn Mork
2017-08-08 11:13 ` Marcel Holtmann
2017-08-08 22:42 ` Bjorn Andersson
2017-08-09 0:48 ` Dan Williams
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=1501860967.939.6.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=david.brown@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.