devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
To: linux-sound@vger.kernel.org
Cc: devicetree@vger.kernel.org, broonie@kernel.org,
	robh+dt@kernel.org,  krzk+dt@kernel.org, conor+dt@kernel.org,
	shuah@kernel.org,  kuninori.morimoto.gx@renesas.com
Subject: [Guidance Request] LFX Mentee looking to contribute to ASoC / DT
Date: Fri, 25 Jul 2025 00:50:15 +0200	[thread overview]
Message-ID: <CANBuOYpLNAtLVWBvR9E74Ju4cM1K7H_bS2Z_UhthQFrJaZXmiQ@mail.gmail.com> (raw)

Hello,

My name is Jihed Chaibi. I am currently a mentee in the Linux
Foundation Mentorship Program, working with Shuah Khan.

With a professional background in embedded systems and a strong
personal interest in audio that extends to my own projects, the ASoC
subsystem seems like the perfect place to blend these two passions.
I'm eager to apply my experience with hardware bring-up and Device
Trees by becoming an active contributor.

To get familiar with the subsystem, I have:

    - Studied the ASoC framework (the Codec/Platform/Machine driver model).
    - Learned about the core audio interfaces (I2S, SAI, PCM, PDM, TDM etc.).
    - Analyzed existing DT sound card implementations to understand
simple-audio-card in practice.

As I look to deepen my involvement, I am writing to seek advice on
where I can best apply my efforts. I'm particularly interested in
finding a substantive task where my skills would be a good fit, such
as:

    - Enabling audio support for a new board using Device Trees.
    - Assisting with bug fixes or small feature additions in the ASoC C drivers.
    - Tackling items from the TODO list where my DT experience would
be applicable.
    - Helping with other driver enhancements or cleanups within the
ASoC framework.

Any guidance on finding a suitable project would be highly appreciated!

Thank you for your time and for your work on the kernel.

Best regards,
Jihed CHAIBI

             reply	other threads:[~2025-07-24 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 22:50 Jihed Chaibi [this message]
2025-07-25 13:33 ` [Guidance Request] LFX Mentee looking to contribute to ASoC / DT Mark Brown
2025-08-07 22:28   ` Jihed Chaibi
2025-08-08 13:01     ` Mark Brown

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=CANBuOYpLNAtLVWBvR9E74Ju4cM1K7H_bS2Z_UhthQFrJaZXmiQ@mail.gmail.com \
    --to=jihed.chaibi.dev@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shuah@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).