From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Anshul Dalal <anshulusr@gmail.com>
Cc: michael.opdenacker@rootcommit.com, linux-input@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: I2C: can't detect Adafruit Mini I2C Gamepad on Linux - other devices detected
Date: Fri, 11 Apr 2025 05:21:40 +0000 (UTC) [thread overview]
Message-ID: <24f08a7b-4a3c-4cd6-82b7-0f2c9ab4bbef@rootcommit.com> (raw)
Hi Anshul
I contact you as the maintainer for the Adafruit Mini I2C Gamepad driver.
I'm trying to use the Adafruit Seesaw I2C gamepad in my embedded Linux
training courses, to demonstrate driving I2C hardware, and the gamepad
would be perfect to play an ASCII Pac-Man clone
(https://github.com/michaelopdenacker/myman
<https://github.com/michaelopdenacker/myman>).
Even before your driver is loaded, the device has to be detected. My
problem is the gamepad is never detected on Linux (running "i2cdetect -r
<num>"), while other I2C devices connected to the same bus are, proving
that the bus is correctly enabled. This happens on all these boards
running recent kernels:
- BeaglePlay (Linux 6.14.2!)
- BeagleBone Black
- Raspberry Pi5
I double checked my gamepads (I have 4 of them) and wires: they work
fine on Arduino Uno.
Any clue why none of my 4 gamepads are never detected while two other
types of I2C devices are detected on the same bus, and the same gamepads
work on Arduino Uno?
Maybe something stupid but I'm running out of clues...
You can also have a look at the questions I asked on the Adafruit forums
and the pictures I shared:
https://forums.adafruit.com/viewtopic.php?p=1052577#p1052577
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
next reply other threads:[~2025-04-11 5:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 5:21 Michael Opdenacker [this message]
2025-04-11 15:44 ` I2C: can't detect Adafruit Mini I2C Gamepad on Linux - other devices detected Michael Opdenacker
2025-04-11 15:57 ` Wolfram Sang
2025-04-11 17:34 ` Michael Opdenacker
2025-04-11 19:21 ` Wolfram Sang
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=24f08a7b-4a3c-4cd6-82b7-0f2c9ab4bbef@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=anshulusr@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.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).