Reopen until the current comment is resolved.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Wed, Nov 26
Please approve this review again. Sorry for confusion.
This review has been split into the following 5 reviews. Please check the following reviews.
Sorry for the confusion.
Please accept again same commit: https://reviews.freebsd.org/D53919
- cam/scsi: Support well known logical unit
- ufshci: Enable WLUN scan
- cam/scsi: Add power condition support to START STOP UNIT
- ufshci: Add a check for WLUN during driver initialization
Thanks for the review~!
Oh, you left a review here. I'll reopen it.
We'll review each patch individually.
https://reviews.freebsd.org/D53376
Thu, Nov 6
This patch is ready for the review!
Sun, Nov 2
Oct 27 2025
I will request a review for each commit individually to make reviewing easier.
Oct 23 2025
Oct 22 2025
Sep 18 2025
Sep 16 2025
Sep 13 2025
Sep 12 2025
In D52440#1198791, @imp wrote:So this change is a bit larger than I like to review. But the moved code was simple (and I know I have comment about the moved code, and that maybe the NVMe driver isn't good about doing it true). In the future, though it would make it easiest if you had the 'move it' commits separate from the rest. The place I want a comment could get one later too, if that's easier to do.
Looking at the recovery algorithm, it does seem quite similar to the NVMe one. The only concern I have here is that we'll need to track it in two places. I've been tweaking it from time to time in the nvme driver, but I don't know how applicable future tweaks will be. I guess this is more of a "be aware" in the future comment.
Add a comment
Sep 11 2025
update commit log
Fix queue contruct sequence
Sep 9 2025
I expected the timeout handling to be in the CAM, but it seems the CAM only performs a retry and does not execute cmd abort and controller reset. Therefore, I implemented the cmd abort and controller reset within the ufshci driver. Is my understanding correct?
Added some comments for reviewers.
fix indent
Aug 29 2025
add a newline at end of file
In D51893#1193102, @imp wrote:One question, and one minor problem... Otherwise, I think this is fine. It's a feature that's enable on attach and then everything about it happens automatically, right?
rebase to the head
Aug 21 2025
Aug 14 2025
Add error return
Add error log
Aug 12 2025
Could you please submit this patch? Thanks!
Aug 2 2025
Could you please submit this patch? Thanks!
Jul 25 2025
Jul 18 2025
Jul 16 2025
In D50933#1172976, @imp wrote:In D50933#1172975, @j_yoon.choi_samsung.com wrote:In D50933#1172970, @imp wrote:committeed
I had hoped the test box I ordered to test the UFS stuff would have arrived by now since I wanted to test boot this first... but it's held up in customs, it seems, so after yet another delay I'll push this an the man page in.
Would you mind sharing which test box you ordered?
I think it would be easier to troubleshoot if we have the same device.Minisforum S100-US Intel® N100 / 8GB RAM+256GB SSD / US is what I ordered.
https://store.minisforum.com/products/minisforum-s100?_pos=1&_psq=Minisforum+S100-US&_ss=e&_v=1.0
though it's showing out of stock at the moment... I ordered mine about a month and a half ago now and had to wait until now to get it (now the tracking is telling me it will be here any day... Monday the tracking info made it sound like it was weeks away).
In D50933#1172970, @imp wrote:committeed
I had hoped the test box I ordered to test the UFS stuff would have arrived by now since I wanted to test boot this first... but it's held up in customs, it seems, so after yet another delay I'll push this an the man page in.
In D51029#1172968, @imp wrote:Committed...
Could you please commit this patch?
Could you please commit this patch?
Jul 10 2025
Jul 2 2025
Jun 25 2025
initialisation -> initialization
Add ufshci to Makefile
Jun 24 2025
Use full name of driver
Jun 19 2025
Jun 13 2025
In D50370#1160086, @imp wrote:In D50370#1160085, @j_yoon.choi_samsung.com wrote:In D50370#1159626, @j_yoon.choi_samsung.com wrote:In D50370#1159535, @imp wrote:I think this is ready to commit (or at least to start to try)... What do you think?
Yes, I think this is ready to commit!
I don't understand the commit process. Is there anything I need to do to commit?
Since you don't yet have commit permissions, I'll need to do that. I'll download it to my tree, make sure it compiles everywhere (or is disabled) and then push it into the repo. I just wanted to make sure that you didn't have anything else planned before I started that process...
In D50370#1159626, @j_yoon.choi_samsung.com wrote:In D50370#1159535, @imp wrote:I think this is ready to commit (or at least to start to try)... What do you think?
Yes, I think this is ready to commit!
Jun 12 2025
In D50370#1159535, @imp wrote:I think this is ready to commit (or at least to start to try)... What do you think?
Change UIC power mode ready time from 500ms to 2000ms
Apply review comments.
Apply review comments
Thank you for the kind review.
Your advice was a great help in preparing the patch. :)
Apply review comment, Remove unnecessary functions
Jun 11 2025
Rename functions
Fix a uic command bug
I measured the key performance metrics on the real device and confirmed that the results meet my goals.
For Write, if WriteBooster is applied, the bandwitch will increase.
Here are the results I measured on each device.