From: "manivannan.sadhasivam" <manivannan.sadhasivam@linaro.org>
To: Johannes Fischer <johannes.fischer@verificationpartners.com>
Cc: Slark Xiao <slark_xiao@163.com>,
Steven Edwards <steven.edwards@verificationpartners.com>,
mhi <mhi@lists.linux.dev>
Subject: Re: Linux Kernel 6.6.36 and upstream mhi repo latest: Interface definition of sierra_em919x
Date: Sun, 21 Jul 2024 14:02:58 +0530 [thread overview]
Message-ID: <20240721083258.GJ1908@thinkpad> (raw)
In-Reply-To: <AS2PR03MB90048FCF02A8050A0375045EE5A72@AS2PR03MB9004.eurprd03.prod.outlook.com>
On Sat, Jul 13, 2024 at 09:33:17AM +0000, Johannes Fischer wrote:
> Hi all,
> @Stark,
> first, I accept that changes may have side impact on other modems.
> Please have in mind that I flashed SWIX55C_03.14.10.04 and the respective generic nvu a few days ago, so I assume to be quite close to default config.
>
> Using the sierra_em919x config with IP links changed to MBIM in kernel I can establish data traffic; I do not see a component converting the MBIM stream to RMnet in Linux kernel (?). I wonder whether there is positive confirmation about a EM919x working in PCIe mode with the current kernel config, in which mode? (We did not have trouble using the EM919x in USB mode.)
>
> About GPIO handling, as said there is none for for Full_Card_Power_off# (6, 10k pull-up to 3V3) and RESET# (67, just a C=100nF to GND) on the BPI-R4.
> We have not validated the timing in BPI-R4 with 6.6.36 or current kernel versus the timing diagram at "AirPrime EM919X/EM7690 Product Technical Specification". As you said there may be a corner case that we end up with the Foxconn config due to timing at BPI-R4 power up times.
>
> I get from your statement, that the valid config should be sierra_em919x, thanks for this clarification.
>
> @Mani,
> for my understanding: I would be only able to get a MBIM type channel if the channel is configured for IP_HW0_MBIM. If it is configured for IP_HW0 only than it would be plain IP traffic like RMnet. Is this understanding right? - Thanks
>
Correct.
- Mani
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2024-07-21 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AS2PR03MB90043BBFBCA2E14D2EB62E84E5A62@AS2PR03MB9004.eurprd03.prod.outlook.com>
2024-07-12 16:13 ` Linux Kernel 6.6.36 and upstream mhi repo latest: Interface definition of sierra_em919x manivannan.sadhasivam
[not found] ` <716a2414.bcfae.190a7cf2247.Coremail.slark_xiao@163.com>
2024-07-13 9:41 ` Johannes Fischer
2024-07-15 3:43 ` Slark Xiao
2024-07-21 8:35 ` manivannan.sadhasivam
2024-07-22 3:01 ` Slark Xiao
[not found] ` <AS2PR03MB90048FCF02A8050A0375045EE5A72@AS2PR03MB9004.eurprd03.prod.outlook.com>
2024-07-21 8:32 ` manivannan.sadhasivam [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=20240721083258.GJ1908@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=johannes.fischer@verificationpartners.com \
--cc=mhi@lists.linux.dev \
--cc=slark_xiao@163.com \
--cc=steven.edwards@verificationpartners.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 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.