committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r356808||manu||Jan. 16, 2020, 9:25 p.m.||arm64: rockchip: Add RK3399 PWM driver|
|r356807||manu||Jan. 16, 2020, 9:21 p.m.||arm64: rockchip: Add new interface for rk_pinctrl
The gpio controller in rockchips SoC in a child of the pinctrl driver and cannot control pullups and pulldowns. Use the new fdt_pinctrl interface for accessing pin capabilities and setting them. We can now report that every pins is capable of being IN or OUT function and PULLUP PULLDOWN. If the pin isn't in gpio mode no changes will be allowed. Reviewed by: ganbold (previous version) MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D22849ViewVC
|r356806||manu||Jan. 16, 2020, 9:19 p.m.||fdt_pinctrl: Add new methods for gpios
Most of the gpio controller cannot configure or get the configuration of the pin muxing as it's usually handled in the pinctrl driver. But they can know what is the pinmuxing driver either because they are child of it or via the gpio-range property. Add some new methods to fdt_pinctrl that a pin controller can implement. Some methods are : fdt_pinctrl_is_gpio: Use to know if the pin in the gpio mode fdt_pinctrl_set_flags: Set the flags of the pin (pullup/pulldown etc ...) fdt_pinctrl_get_flags: Get the flags of the pin (pullup/pulldown etc ...) The defaults method returns EOPNOTSUPP. Reviewed by: ian, bcr (manpages) MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D23093ViewVC
|r356803||manu||Jan. 16, 2020, 8:52 p.m.||regulator_fixed: Add a get_voltage method|
|r356802||manu||Jan. 16, 2020, 8:19 p.m.||arm: allwinner: ahci: target-supply is optional
The target-supply regulator is optional so don't fail if it's not present. While here disable the clock on detach. MFC after: 2 weeks X-MFC-With: 356600ViewVC
|r356801||krion||Jan. 16, 2020, 8:12 p.m.||Generate MAC address from the FreeBSD OUI range.|
|r356800||manu||Jan. 16, 2020, 8:02 p.m.||arm: allwinner: Add support for bank supply
Each GPIO bank is powered by a different pin and so can be powered at different voltage from different regulators. Add a new config that now hold the pinmux data and the banks available on each SoCs. Since the aw_gpio driver being also the pinmux one it's attached before the PMIC so add a config_intrhook_oneshot function that will enable the needed regulators when the system is fully functional. MFC after: 2 weeksViewVC
|r356799||manu||Jan. 16, 2020, 7:59 p.m.||axp8xx: Add a regnode_init method
This method will set the desired voltaged based on values in the DTS. It will not enable the regulator, this is the job of either a consumer or regnode_set_constraint SYSINIT if the regulator is boot_on or always_on. MFC after: 2 weeksViewVC
|r356798||manu||Jan. 16, 2020, 7:57 p.m.||axp8xx: Add missing voltage regulators offset
This lead to writing the desired voltage value to the wrong register. MFC after: 2 weeksViewVC
|r356797||emaste||Jan. 16, 2020, 5:27 p.m.||pkgbase: move profiling _p.a libs into -development packages
Profiling library archives are part of the development environment; they don't need to be in separate -profile packages. (In fact we can probably just eliminate the _p.a archives assuming that profiling will be done using hwpmc etc., but that is a change for later.) Discussed with: bapt, manu Sponsored by: The FreeBSD FoundationViewVC
|r356796||tuexen||Jan. 16, 2020, 5:15 p.m.||Remove debug code not needed anymore.|
|r356792||gjb||Jan. 16, 2020, 3:07 p.m.||Update release(7) to note OSRELEASE is only relevant when the|
|r356791||arichardson||Jan. 16, 2020, 2:15 p.m.||Allow building bin/cat on non-FreeBSD systems
`cat -l` is needed during the installworld phase and other system's cat don't support that flag. To avoid portability issues when compiling on Linux/macOS (such as the the direct access to &fp->_mbstate), we disable the entire multibyte support when building as a boostrap tool. Reviewed By: brooks, emaste Differential Revision: https://reviews.freebsd.org/D13939ViewVC
|r356790||arichardson||Jan. 16, 2020, 2:14 p.m.||Allow bootstrapping mkimg on macOS/Linux|
|r356789||arichardson||Jan. 16, 2020, 2:14 p.m.||Merge commit 894f742acb from llvm git (by me):
[MIPS][ELF] Use PC-relative relocations in .eh_frame when possible When compiling position-independent executables, we now use DW_EH_PE_pcrel | DW_EH_PE_sdata4. However, the MIPS ABI does not define a 64-bit PC-relative ELF relocation so we cannot use sdata8 for the large code model case. When using the large code model, we fall back to the previous behaviour of generating absolute relocations. With this change clang-generated .o files can be linked by LLD without having to pass -Wl,-z,notext (which creates text relocations). This is simpler than the approach used by ld.bfd, which rewrites the .eh_frame section to convert absolute relocations into relative references. I saw in D13104 that apparently ld.bfd did not accept pc-relative relocations for MIPS ouput at some point. However, I also checked that recent ld.bfd can process the clang-generated .o files so this no longer seems true. Reviewed By: atanasyan Differential Revision: https://reviews.llvm.org/D72228 Merge commit 8e8ccf47 from llvm git (by me) [MIPS] Don't emit R_(MICRO)MIPS_JALR relocations against data symbols The R_(MICRO)MIPS_JALR optimization only works when used against functions. Using the relocation against a data symbol (e.g. function pointer) will cause some linkers that don't ignore the hint in this case (e.g. LLD prior to commit 5bab291) to generate a relative branch to the data symbol which crashes at run time. Before this patch, LLVM was erroneously emitting these relocations against local-dynamic TLS function pointers and global function pointers with internal visibility. Reviewers: atanasyan, jrtc27, vstefanovic Reviewed By: atanasyan Differential Revision: https://reviews.llvm.org/D72571 These two changes should allow using lld for MIPS64 (and maybe also MIPS32) by default. The second commit is not strictly necessary for clang+lld since LLD9 will not perform the R_MIPS_JALR optimization (it was only added for 10) but it is probably required in order to use recent ld.bfd. Reviewed By: dim, emaste MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D23203ViewVC