Linux/DS90UB949-Q1: -Linux driver requirement

Hi,
The link between UB948 and UB948 can work automatically with hardware pin setting, you can refer to d/s on the mode_sel setting. also you can use TI's ALP tool with GUI to configure this link. in most cases, the link between UB949 and UB948 can run automatically without the register setting. in some cases, you can use registers, such as reset, I2C access, etc. So sorry we have no Linux driver for you.

best regards,
Steven

Hi TI Community:

First of all, very thanks for yor rapidly reply my question. Following are my understanding of the TI's SerDes, if I have any incorrect, please correct me:

1. Roughly, TI SerDes mainly have two I2C processing mechanism, one is the "paired device access, Fig-1" & the other is "external slave access Fig2."

2. In paired device access, the DES_ID will be loaded from de-serializer when RX_Locked. (Please see Fig-3)

3. Like as Fig3 illustration, if you just want to access De-serializer that's definitely don't need to config register between Serializer and De-Serializer and we can easily access serializer and de-serialize through master I2C interface by HOST.

4. But If I have slave device (touch panel) attached at the De-serializer, I have to config SlaveID and SlaveAlias of Serializer side.....Am I right? If this is right, the intialize driver still don't need?

Above that my understanding of TI's SerDes if I have any misconcepton please let me know.

Have a good day.

Fox.

Fig-1: SerDes I2C paired device

Fig-2 : External slave access

Fig-3 : Master I2C attached Serializer

Fox,
yes, you are right, please see below comments.
1. Roughly, TI SerDes mainly have two I2C processing mechanism, one is the "paired device access, Fig-1" & the other is "external slave access Fig2."
--> yes, can access remote paired part (ser or deser), and the attached slave I2C port (such as touch controller).

2. In paired device access, the DES_ID will be loaded from de-serializer when RX_Locked. (Please see Fig-3)
--> yes, automatically by FPD-Link after it is stable.

3. Like as Fig3 illustration, if you just want to access De-serializer that's definitely don't need to config register between Serializer and De-Serializer and we can easily access serializer and de-serialize through master I2C interface by HOST.
--> you need configure the deser's I2C alias address, or else you don't the two attached deser in figure3. also you need enable pass-through.

4. But If I have slave device (touch panel) attached at the De-serializer, I have to config SlaveID and SlaveAlias of Serializer side.....Am I right? If this is right, the intialize driver still don't need?
-> you need set: a. pass through; b. deser's alias address; c. slaveID and slaveAlias attached to the deser. if you need visit the touch controller, it is certain that the reg. should be configured, and TI has some reg. setting referencei in d/s or EVM board.

best regards,
Steven