From: "manivannan.sadhasivam" <manivannan.sadhasivam@linaro.org>
To: Slark Xiao <slark_xiao@163.com>
Cc: Johannes Fischer <johannes.fischer@verificationpartners.com>,
Steven Edwards <steven.edwards@verificationpartners.com>,
mhi <mhi@lists.linux.dev>
Subject: Re: Re: Linux Kernel 6.6.36 and upstream mhi repo latest: Interface definition of sierra_em919x
Date: Sun, 21 Jul 2024 14:05:22 +0530 [thread overview]
Message-ID: <20240721083522.GK1908@thinkpad> (raw)
In-Reply-To: <1ba76a65.4185.190b47cf475.Coremail.slark_xiao@163.com>
On Mon, Jul 15, 2024 at 11:43:26AM +0800, Slark Xiao wrote:
>
> At 2024-07-13 17:41:27, "Johannes Fischer" <johannes.fischer@verificationpartners.com> 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.
> >
>
> Yeah, I just checked this issue again. We met this issue in our ARM platform.
> Device boot up shall through PBL->SBL->Kernel boot up. And there are 2 different PCIe settings between PBL and kernel side.
> When host mhi driver probed, your device may still in PBL stage or SBL stage(the PCIe EP in device side is not ready), then you will get a "foxconn-config" since your PBL ID match with that one.
> Solution shall have these:
> 1. Update firmware side to keep ID same between PBL and kernel config.
Having 2 PCIe IDs for a single device doesn't sound right. If it is fixed in
successive firmware releases then fine, otherwise please fix it for all.
- Mani
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-07-21 8:35 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 [this message]
2024-07-22 3:01 ` Re:Re: " Slark Xiao
[not found] ` <AS2PR03MB90048FCF02A8050A0375045EE5A72@AS2PR03MB9004.eurprd03.prod.outlook.com>
2024-07-21 8:32 ` manivannan.sadhasivam
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=20240721083522.GK1908@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox