This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TAD5212: jack detection and switching between headset / speaker

Part Number: TAD5212
Other Parts Discussed in Thread: TS3A227E, , TLV320AIC3268

Targetting the following configuration:

  OUT1 Line-out

  OUT2 Use a MUX to switch between stereo headset jack and differential mono speaker amplifier.

Using something like the TS3A227E on the headset jack to detect the presense of a headset should allow for a straight forward solution.

However the TAD5212 has builtin support for jack detection so perhaps the TS3A227E isn't necessary.  Looking at the datasheet and the application note "Headset Detection for TAx52xx Family" leaves me with some questions:

  1. The application note shows MICDET and HPLOUT / HPROUT which I'm familar with from the TLV320AIC3268 ... it's not clear how they relate to the TAD5212 pinout.
  2. The TAD5212 datasheet shows both OUT1 and OUT2 can be configured to drive headsets (i.e. two separate headset jacks).  It looks like JACK_DET_CFG3 indicates if a headset has been inserted and if so, then the type.  What indicates which output / jack triggered the event?  Is the detection active for both OUT1 / OUT2 and the assumption is that a system will only have one jack, thus JACK_DET_CFG3 relates to whichever output is actually wired to a headset jack?
  3. Assuming that MICDET (mentioned in the application note) corresponds to the IN1 / IN2 pins, then is the following feasible:
  • Wire MICBIAS, and IN1 directly to headset jack.
  • Wire OUT1 to MUX.  Output of MUX is software switchable between headset jack and mono speaker amplifier.
  • Set MUX to speaker.
  • Set JACK_DET_EN to 1.
  • If interrupt event indicates headset insert event, then set MUX to headset jack and toggle JACK_DET_EN to restart detection routine so headset type can be determined.

This is for a small personal project so I can easily drop in the TS3A227E if the use case falls outside of what is directly supported by the TAD5212 jack detection hardware.

  • Hi John,

    The headset detection mechanism is meant for one jack, as both outputs are needed for common mode sensing done through OUT2M (HPSNS) in a pseudo-differential output mode:

    The "ground" of the jack is actually connected to the output common mode Vcm. I think the headset detection could work, but the headset type detection might be interfered by the MUX. This use case is not exactly typical, and since I cannot test the exact setup myself, I can only speculate as to its effectiveness.

    Best,

    Garret

  • The clarification of the headset detection mechanism used by the TAD5212 is very helpful ... I'll go the TS3A227E route for this project..

    Thanks.