Thanks everyone. Pushed upstream today. Sorry about the delay in pushing it.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 13 2021
Jul 8 2021
Mar 3 2021
Feb 24 2021
Feb 22 2021
Thanks everyone for accepting the changes.
Feb 19 2021
@vmaffione, @gallatin and @yuripv,
Addressed comments on V2 patch
Feb 18 2021
Addressed review comments on v1 patch
@vmaffione, I have used igor and mandoc to ensure no warnings before submitting the patch. I have informed the same in Test plan section
Feb 17 2021
Feb 16 2021
@vmaffione and @gallatin
Added PGP public key along with other previous changes
Feb 12 2021
@vmaffione, Do you have any comments?
Feb 11 2021
Feb 10 2021
Jul 9 2019
Ok. I will create another review. Thanks for your time and immediate response.
Thanks @mav for reviewing and pushing the patch upstream. I verified it to work properly. I have some more minor changes to this Driver (basically to add support for another PCI Device ID). Shall I submit the additional patch here itself? or should I open another review for the same?
Apr 15 2019
Is there anything else needed here? or can this be taken upstream?
Mar 11 2019
@mav, Did you get a chance to look at this?
Feb 25 2019
@mav: Sorry to disturb you on this again. But, please have a look at this when you get a chance and let me know if there any comments to address here.
Feb 18 2019
@mav, Any more comments on this patch?
Feb 11 2019
Made necessary changes as per the previous discussion. Attached V6 patch.
Feb 8 2019
@mav: I checked about that alignment requirements. Seems, the alignment should be on-par to the bar size (and not a fixed value) and the granularity range what I mentioned earlier for LUT based addressing (which is not implemented here). So, I need to change the alignment equal to the bar size. Do you have any comments on the previous discussed changes?
Feb 5 2019
Feb 4 2019
No new patch attached, but looking for few clarification on your previous comments.
Feb 1 2019
Addressed comment from @mav regarding the alignment and explained the reason for those checks for xlat and limit registers.
Jan 29 2019
Any more comments on this patch?
Jan 23 2019
Jan 21 2019
Submitting V4 patch, addressing comment from @imp
In D18774#403351, @imp wrote:I just made a pass through for anything that caught my eye, and found a couple. I have not reviewed it to see if it matches the hardware spec for what it's trying to control.
Jan 18 2019
Jan 9 2019
V2 patch addressing the previous comments from cem.
Hi cem,
Jan 7 2019
Nov 5 2018
Thanks Macy.
Oct 30 2018
Hi Macy,
Oct 22 2018
Hi Macy/Warner,
Oct 16 2018
make tinderbox reported some failure with arm architecture. Fixed that.
Oct 13 2018
Hi Oleksandr,
Oct 8 2018
In D16865#371516, @gonzo wrote:Sorry for delays with answers
To be honest, the current code freeze seems quite... flexible. As in, there's certainly some new stuff coming in, and from my understanding adding a new driver (as opposed to modifying something that's already there) is rather unlikely to break something. Maybe just send an email to re@ and see what they say?
Yes, and IMHO this flexibility is not a very good thing (speaking from personal experience as a part-time RE at $WORK). I don't want to submit more new feature changes to re@ that is strictly necessary and so far I can't find pro arguments for this driver. As far as I understand this driver is going to be used as a building block for other components that are going to use it either as a control method for peripherals or as an interrupt source. If I am wrong and there are readily available immediate use cases, for instance, AMD-based embedded platforms where GPIO can be used from the userland or AMD-based laptops where gpioctl can be used directly to enable certain functionality that is otherwise unavailable I'll bring the patch up to re@ for the consideration. Otherwise, I'd rather wait for the code thaw and submit it to -HEAD with further MFCs to -12 and -11, it will be available in 12.1 in a year or so.
Rajesh, if you're familiar with the solutions available on the market could you share such use cases so I could argue for the inclusion of the driver?
Thanks
Hi Oleksandr,
Oct 2 2018
Oct 1 2018
Hi Oleksandr,
Sep 21 2018
Hi Olexsandr,
- Added the static keywords to those mentioned structures in H file, as the intent is code readability
- Cleared the unwanted whitespaces/tabs and followed style(9) format for indentation in both C and H file.
Hi Oleksandr,
Sep 18 2018
Thanks for taking time to review the first patch and clarifying on the release process.
Hi Gonzo,
- Removed static keywords from pin grouping definitions in H file.
- Moved static struct "resource_spec" to C file.
- Removed unwanted static declaration of probe, attach and detach in H file.
- Removed redundant file in C file
Sep 17 2018
Hi Gonzo,
Sep 3 2018
Thank you Gonzo.
Aug 30 2018
Hi Gonzo, Did you get a chance to look at this?