linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aleksander Morgado <aleksander@aleksander.es>
To: Thomas Perrot <thomas.perrot@bootlin.com>
Cc: Loic Poulain <loic.poulain@linaro.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Hemant Kumar <hemantk@codeaurora.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: Sierra Wireless EM9191 integration issues in mhi+wwan
Date: Wed, 20 Oct 2021 10:43:09 +0200	[thread overview]
Message-ID: <CAAP7ucLCL37aYWMeqyj4eb-r6B-puZ+w9KeXMScpw3YhWgzXNA@mail.gmail.com> (raw)
In-Reply-To: <CAAP7ucJBed_5rCdyjWC9x8EkXn5+E7p4P46=ukAaC1vTFLdDAQ@mail.gmail.com>

Hey,

> This is the event ring configuration in the MBPL driver from Sierra,
> with NUM_MHI_EVT_RING_ELEMENTS=2048:
>
> static struct mhi_event_properties event_config[] = {
> /*    num                        intmod  msi chan    pri brs type
> hw_ev   c_m off  */
>     { NUM_MHI_EVT_RING_ELEMENTS,  1,      1,  0,      1,  2,  1,
> 0,      0,  0},
>     { NUM_MHI_EVT_RING_ELEMENTS,  1,      2,  100,    1,  3,  0,
> 1,      0,  0},
>     { NUM_MHI_EVT_RING_ELEMENTS,  1,      3,  101,    1,  3,  0,
> 1,      0,  0},
> //    { 240,  1,      3,  101,    1,  2,  0,      1,      0,  0},
> //    { 240,  1,      4,  0,      1,  2,  1,      0,      0,  0},
> };
>

Looking in detail at the table above, I can see at least 2 differences
between the Sierra MBPL driver and the upstream one:
 * In the upstream driver, MHI_EVENT_CONFIG_CTRL() sets
irq_moderation_ms to 0, while in the Sierra MBPL driver the table
above (intmod column) we can see it's set to 1 in channel 0.
 * In the upstream driver, MHI_EVENT_CONFIG_HW_DATA() sets mode to
MHI_DB_BRST_DISABLE(2), while in the Sierra MBPL driver the table
above (brs column) we can see it's set to MHI_DB_BRST_ENABLE (3) in
channels 100 and 101.

But changing those in my setup to be in line with the MBPL driver
didn't make any difference :/

-- 
Aleksander
https://aleksander.es

  reply	other threads:[~2021-10-20  8:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 13:04 Sierra Wireless EM9191 integration issues in mhi+wwan Aleksander Morgado
2021-10-09 10:51 ` Manivannan Sadhasivam
2021-10-12 19:38   ` Aleksander Morgado
2021-10-22  4:42     ` Manivannan Sadhasivam
2021-10-22  9:20       ` Aleksander Morgado
2021-10-22 14:40         ` Manivannan Sadhasivam
2021-10-25  8:10           ` Aleksander Morgado
2021-11-02 10:50             ` Manivannan Sadhasivam
2021-11-02 16:13               ` Aleksander Morgado
2021-11-02 16:22                 ` Manivannan Sadhasivam
2021-11-02 16:55                   ` Aleksander Morgado
2021-11-02 18:09                     ` Manivannan Sadhasivam
     [not found]                       ` <CAMZdPi9+zrsDy9WTipamRWBXMOxUX1tfsk2W52b9wG-4q21fWA@mail.gmail.com>
2021-11-04 22:50                         ` Bhaumik Bhatt
2021-11-08  7:40                       ` Manivannan Sadhasivam
2021-11-08 13:38                         ` Aleksander Morgado
2021-10-11 14:44 ` Thomas Perrot
2021-10-12 19:44   ` Aleksander Morgado
2021-10-14  9:51     ` Thomas Perrot
2021-10-14 10:04       ` Aleksander Morgado
2021-10-14 17:28         ` Loic Poulain
2021-10-14 20:25           ` Aleksander Morgado
2021-10-18  9:14             ` Aleksander Morgado
2021-10-18  9:59               ` Loic Poulain
2021-10-18 11:26                 ` Thomas Perrot
2021-10-18 12:46                   ` Loic Poulain
2021-10-18 14:07                     ` Thomas Perrot
2021-10-18 14:16                       ` Thomas Perrot
2021-10-19  8:38                       ` Aleksander Morgado
2021-10-20  8:43                         ` Aleksander Morgado [this message]
2021-10-22 14:33                     ` Aleksander Morgado
2021-11-08 15:11   ` Aleksander Morgado
2021-11-08 16:31     ` Thomas Perrot
2021-11-08 20:16       ` Aleksander Morgado

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=CAAP7ucLCL37aYWMeqyj4eb-r6B-puZ+w9KeXMScpw3YhWgzXNA@mail.gmail.com \
    --to=aleksander@aleksander.es \
    --cc=hemantk@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=thomas.perrot@bootlin.com \
    --cc=thomas.petazzoni@bootlin.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).