Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
From:   Bassem Fahmy <bassem@morsemicro.com>
Date:   Wed, 30 Oct 2019 06:48:39 +1100
Message-ID: <CAEirPfz4FEtuRH8VST0ehtQtttPpFJFrZLDb9v7heUAb8EA2tw@mail.gmail.com>
Subject: Chip debug tool
To:     linux-wireless@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

Hi
Our systems team is asking to develop a chip debug tool to be able to
test, calibrate and tweak every bit of the chip from user space
(something similar to Broadcom's WL tool). The tool would later be
stripped out and passed to customers to help them tweak specific
features.

The tool needs to be easy for the firmware and RF team to add extra
command, by adding some definitions in the user space tool and a
matching response in the firmware (no driver recompilation).

Based on this, I can think of few of options
- nl80211: to overload NL80211_CMD_TESTMODE or NL80211_CMD_VENDOR or
- nl80211: to create a new set of commands. These options don't seem
to have a chance to go back upstream though.

Another option is to use debugfs. In this case however, all the
commands would go to a single node, and the driver which would blindly
pass data to/from the chip. This is to avoid recompiling the driver
every time a new command is added.

Just wondering what is the proper (recommended way) for this. Any
ideas, directions?

Thanks, Bassem