SIMCOM 7230E vs 7600E

[Bjørn Mork]

Sebastian Sjoholm <sebastian.sjoholm at gmail.com> writes:

> Hi,
>
> An interesting QMI issue on SimCom 7230E vs SimCom 7600E.
>
> The 7230E is quite old model, don't remember the chipset (but qualcomm
> based), and 7600E is the new with MDM9207 (Same as Quectel EC25). Now the
> 7230E is already included in the qmi_wwan.c as normal "QMI_FIXED_INTF", and
> then the 7600E will need the "QMI_QUIRK_SET_DTR" to work (same as EC25).
> But both of these modems uses same USB ID.
>
> Would it be any sense to test if the QUIRK setup works with 7230E?

Sure. But my experience is that older devices fail with "set DTR", so
I'm not too optimistic.

> *** 7600E
>
> ati
> Manufacturer: SIMCOM INCORPORATED
> Model: SIMCOM_SIM7600E-H
> Revision: SIM7600M22_V1.1
> IMEI: 867584030000603
> +GCAP: +CGSM,+DS,+ES
> OK
>
> root at SIMCOM7600E:~# lsusb
> Bus 002 Device 003: ID 1e0e:9001 Qualcomm / Option
> Bus 002 Device 002: ID 04b4:6570 Cypress Semiconductor Corp.
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> root at SIMCOM7600E:~# lsusb -t
> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
>     |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
>         |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 1, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 2, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 3, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 4, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 5, Class=Vendor Specific Class,
> Driver=qmi_wwan, 480M
> /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
> root at SIMCOM7600E:~#
>
> *** 7230E
>
> ati
> Manufacturer: SIMCOM INCORPORATED
> Model: SIMCOM_SIM7230E
> Revision: SIM7230E_V2.0
> IMEI: 864402020047422
> +GCAP: +CGSM,+DS,+ES
> OK
>
> root at SIMCOM7230E:~# lsusb
> Bus 002 Device 003: ID 1e0e:9001 Qualcomm / Option
> Bus 002 Device 002: ID 04b4:6570 Cypress Semiconductor Corp.
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> root at SIMCOM7230E:~# lsusb -t
> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
>     |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
>         |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 1, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 2, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 3, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 4, Class=Vendor Specific Class,
> Driver=option, 480M
>         |__ Port 2: Dev 3, If 5, Class=Vendor Specific Class,
> Driver=qmi_wwan, 480M
>         |__ Port 2: Dev 3, If 6, Class=Vendor Specific Class, Driver=, 480M
>         |__ Port 2: Dev 3, If 7, Class=Mass Storage, Driver=usb-storage,
> 480M
> /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
> root at SIMCOM7230E:~#

OK, so if these compositions are static then we can always use a hack to
recognise the two devices.  Maybe simply look at the number of
interfaces?



Bjørn