public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Aaradhana Sahu <quic_aarasahu@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>, Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] ath12k: Factory test mode support
Date: Mon, 17 Jun 2024 16:47:01 +0530	[thread overview]
Message-ID: <7e1ab778-83af-4e7e-bc5d-069bb6c83563@quicinc.com> (raw)
In-Reply-To: <875xudnf5x.fsf@kernel.org>



On 6/13/2024 7:00 PM, Kalle Valo wrote:
> Jeff Johnson <quic_jjohnson@quicinc.com> writes:
> 
>> On 6/11/2024 1:34 AM, Aaradhana Sahu wrote:
>>
>>> Device is booted in factory test mode for calibration.
>>> The commands are sent from userspace application, which
>>> is sent to firmware using wmi commands. Firmware sends
>>> the response to driver as wmi events and driver sends
>>> these events to the application via netlink message.
>>>
>>> Also added changes related to correct pdev id access for
>>> fw test cmd.
>>>
>>> Aaradhana Sahu (3):
>>>   wifi: ath: create common testmode_i.h file for ath drivers
>>>   wifi: ath12k: export ath12k_wmi_tlv_hdr for testmode
>>>   wifi: ath12k: add factory test mode support
>>>
>>> Rajat Soni (1):
>>>   wifi: ath12k: Fill pdev id for fw test cmd
>>>
>>> ---
>>> v3:
>>>   -Rebased on latest ToT
>>>   -Updated Tested-on Tag
>>>   -Removed second parameter of ath12k_core_start()
>>>   -Updated copyright
>>> v2:
>>>   -Rebased on latest ath ToT
>>> ---
>>>
>>>  drivers/net/wireless/ath/ath11k/testmode.c    |  78 ++--
>>>  drivers/net/wireless/ath/ath12k/Makefile      |   1 +
>>>  drivers/net/wireless/ath/ath12k/core.c        |  22 +-
>>>  drivers/net/wireless/ath/ath12k/core.h        |  13 +
>>>  drivers/net/wireless/ath/ath12k/debug.h       |   1 +
>>>  drivers/net/wireless/ath/ath12k/dp.c          |   3 +
>>>  drivers/net/wireless/ath/ath12k/mac.c         |  15 +-
>>>  drivers/net/wireless/ath/ath12k/pci.c         |   1 +
>>>  drivers/net/wireless/ath/ath12k/testmode.c    | 422 ++++++++++++++++++
>>>  drivers/net/wireless/ath/ath12k/testmode.h    |  40 ++
>>>  drivers/net/wireless/ath/ath12k/wmi.c         |  39 +-
>>>  drivers/net/wireless/ath/ath12k/wmi.h         |  21 +
>>>  .../wireless/ath/{ath11k => }/testmode_i.h    |  52 +--
>>>  13 files changed, 634 insertions(+), 74 deletions(-)
>>>  create mode 100644 drivers/net/wireless/ath/ath12k/testmode.c
>>>  create mode 100644 drivers/net/wireless/ath/ath12k/testmode.h
>>>  rename drivers/net/wireless/ath/{ath11k => }/testmode_i.h (53%)
>>>
>>>
>>> base-commit: a116bf2be795eb1db75fa6a48aa85c397be001a6
>>
>> FYI this series is not applying cleanly in my tree for validation:
>>
>> Base: using specified base-commit a116bf2be795eb1db75fa6a48aa85c397be001a6
>> Applying: wifi: ath: create common testmode_i.h file for ath drivers
>> Using index info to reconstruct a base tree...
>> Patch failed at 0001 wifi: ath: create common testmode_i.h file for ath drivers
>> When you have resolved this problem, run "git am --continue".
>> If you prefer to skip this patch, run "git am --skip" instead.
>> To restore the original branch and stop patching, run "git am --abort".
>> error: patch failed: drivers/net/wireless/ath/ath11k/testmode_i.h:4
>> error: drivers/net/wireless/ath/ath11k/testmode_i.h: patch does not apply
>> error: Did you hand edit your patch?
>> It does not apply to blobs recorded in its index.
>>
>> I initially used b4, but tried again directly with git, and it failed for me 
>> with both mechanisms.
>> Kalle, do you have any issues with this series?
> 
> Also fails for me on top of commit a116bf2be795:
> 
> Applying: wifi: ath: create common testmode_i.h file for ath drivers
> Using index info to reconstruct a base tree...
> error: patch failed: drivers/net/wireless/ath/ath11k/testmode_i.h:4
> error: drivers/net/wireless/ath/ath11k/testmode_i.h: patch does not apply
> error: Did you hand edit your patch?
> It does not apply to blobs recorded in its index.
> Patch failed at 0001 wifi: ath: create common testmode_i.h file for ath drivers
> 
> Setting the patchset to Changes Requested.
> 

I have rebased and sent the next version.


  reply	other threads:[~2024-06-17 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  8:34 [PATCH v3 0/4] ath12k: Factory test mode support Aaradhana Sahu
2024-06-11  8:34 ` [PATCH v3 1/4] wifi: ath: create common testmode_i.h file for ath drivers Aaradhana Sahu
2024-06-11  8:34 ` [PATCH v3 2/4] wifi: ath12k: export ath12k_wmi_tlv_hdr for testmode Aaradhana Sahu
2024-06-11  8:34 ` [PATCH v3 3/4] wifi: ath12k: add factory test mode support Aaradhana Sahu
2024-06-11  8:34 ` [PATCH v3 4/4] wifi: ath12k: Fill pdev id for fw test cmd Aaradhana Sahu
2024-06-12 16:51 ` [PATCH v3 0/4] ath12k: Factory test mode support Jeff Johnson
2024-06-13 13:30   ` Kalle Valo
2024-06-17 11:17     ` Aaradhana Sahu [this message]
2024-06-26 17:03 ` Kalle Valo

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=7e1ab778-83af-4e7e-bc5d-069bb6c83563@quicinc.com \
    --to=quic_aarasahu@quicinc.com \
    --cc=ath12k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_jjohnson@quicinc.com \
    /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