<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in files</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>a3833b88 - MFS r353184, r353186, r353188, r353190, r353192, r353194, r353196, r353198,</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#a3833b88</link>
        <description>MFS r353184, r353186, r353188, r353190, r353192, r353194, r353196, r353198,r353200, r353203, r353205, r353207, r353209, r353211, r353213, r353215,r353217, r353219, r353221, r353223, r353225, r353227, r353229, r353231,r353233, r353235, r353237, r353239, r353241, r353243, r353245, r353247,r353249, r353251, r353253, r353255, r353257, r353259, r353261, r353263,r353265 and r353267:Update mlx5core, mlx5en(4) and mlx5ib(4).Sponsored by:	Mellanox TechnologiesApproved by:	re (gjb)MFC r352956:Fix reported max SGE calculation in mlx5ib.Add the 512 bytes limit of RDMA READ and the size of remote address to the maxSGE calculation.Linux commit:	288c01b746aaMFC r352957:Update warning and error print formats in mlx5ib.MFC r352958:Make sure the number of IRQ vectors doesn&apos;t exceed 256 in mlx5core.The &quot;intr&quot; field in &quot;struct mlx5_ifc_eqc_bits&quot; is only 8 bits wide.MFC r352959:Check return value of mlx5_vector2eqn() function in mlx5en.MFC r352960:Fix for missing cleanup code in error case in mlx5en.MFC r352961:Implement macro for asserting priv lock in mlx5en.MFC r352962:Add support for Multi-Physical Function Switch, MPFS, in mlx5en.MPFS is a logical switch in the Mellanox device which forward packetsbased on a hardware driven L2 address table, to one or more physical-or virtual- functions. The physical- or virtual- function is requiredto tell the MPFS by using the MPFS firmware commands, which unicastMAC addresses it is requesting from the physical port&apos;s traffic.Broadcast and multicast traffic however, is copied to all listeningphysical- and virtual- functions and does not need a rule in the MPFSswitching table.Linux commit:	eeb66cdb682678bfd1f02a4547e3649b38ffea7eMFC r352963:Cleanup naming of IRQ vectors in mlx5en.Remove unused IRQ naming functions and arrays.MFC r352964:Export channel IRQ number as part of the &quot;hw_ctx_debug&quot; sysctl(8) in mlx5en(4).MFC r352965:Correct and update some counter names in mlx5en(4).MFC r352966:Add port module event software counters in mlx5core.While at it, fixup PME based on latest PRM defines.MFC r352967:Make the mlx5_vsc_wait_on_flag(9) function global.MFC r352968:Move mlx5_ifc_vsc_space_bits and mlx5_ifc_vsc_addr_bits to mlx5_ifc.h.MFC r352969:Use the MLX5_VSC_DOMAIN_SEMAPHORES constant instead of hand-rolled symbolin mlx5core.MFC r352970:Define MLX5_VSC_DOMAIN_SCAN_CRSPACE.MFC r352971:Read rege map from crdump scan space in mlx5core.MFC r352972:Remove no longer needed fwdump register tables from mlx5core.MFC r352973:Add missing blank line at the end of the print in mlx5core.MFC r352974:Add proper print in case of 0x0 health syndrome in mlx5core.In case of health counter fails to increment it indicates a bad device health.In case when the syndrome indicated by firmware is 0x0, this indicates thatfirmware is unable to respond to initialization segment reads.Add proper print in this case.MFC r352975:Unify prints in mlx5core.All prints in mlx5core should use on of the macros:mlx5_core_err/dbg/warnMFC r352976:Unify prints in mlx5en(4).All prints in mlx5en(4) should use on of the macros:mlx5_en_err/dbg/warnMFC r352977:Sort the ports registers definitions numerically in mlx5core.MFC r352978:Add definition for the Port Buffer Status Register in mlx5core.MFC r352979:Update definitons for PPTB and PBMC registers layouts in mlx5core.MFC r352980:Add mlx5e_dbg() compatibility macro.MFC r352981:Import Linux code to query/set buffer state in mlx5en(4).MFC r352982:Add support for buffer parameter manipulations in mlx5en(4).The following sysctls are added:dev.mce.N.conf.qos.cable_lengthdev.mce.N.conf.qos.buffers_sizedev.mce.N.conf.qos.buffers_prioMFC r352983 and r353001:Move EEPROM information query from a sysctl in mlx5en(4) to an ioctlin mlx5core. The EEPROM information is not only a property of themlx5en(4) driver.MFC r352984:Add the ability to query the EEPROM information in mlx5tool(8).MFC r352985:Add sysctl(8) to get and set forward error correction, FEC, configurationin mlx5en(4).MFC r352986:Return an error from ioctl(MLX5_FW_RESET) if reset was rejected in mlx5core.MFC r352987:Remove mkey_be from channel structure in mlx5en(4).Use value from priv structure instead.This saves some space in the channel structure.MFC r352988:Remove unused cpu field from channel structure in mlx5en(4).MFC r352989:Seal transmit path with regards to using destroyed mutex in mlx5en(4).It may happen during link down that the running state may be observednon-zero in the transmit routine, right before the running state iscleared. This may end up using a destroyed mutex.Make all channel mutexes and callouts persistant.Preserve receive and send queue statistics during link toggle.MFC r352991 and 353000:Wait for FW readiness before initializing command interface in mlx5core.Before attempting to initialize the command interface we must wait tillthe fw_initializing bit is clear.If we fail to meet this condition the hardware will drop ourconfiguration, specifically the descriptors page address.  This scenariocan happen when the firmware is still executing an FLR flow and did notfinish yet so the driver needs to wait for that to finish.Linux commits:6c780a0267b8b8a92577f4be.MFC r352992:Use size_t for byte_to_write variable when comparing to eeprom_info_out_lenwhich is also size_t in mlx5tool(8).MFC r352993:Randomize the delay when waiting for VSC flag in mlx5core.The PRM suggests random 0 - 10ms to prevent multiple waiters on the sameinterval in order to avoid starvation.MFC r352994:Improve mlx5_fwdump_prep logging in mlx5core.MFC r352995:Only update lossy buffers config when manual PFC configuration was donein mlx5en(4).MFC r352996:Add print to show user a reason for rejecting buffer size change in mlx5en(4).MFC r352997:Print numeric error_type and module_status in mlx5corein case the strings are not available.MFC r352998:Bump driver version for mlx5core, mlx5en(4) and mlx5ib(4).

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Mon, 07 Oct 2019 13:13:06 +0000</pubDate>
        <dc:creator>Hans Petter Selasky &lt;hselasky@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>fc3777bd - MFC r351196, r351324, r351326:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#fc3777bd</link>
        <description>MFC r351196, r351324, r351326:ng_ubt(4): do not attach Intel Wireless 8260/8265 in bootloader mode.Add helper function for synchronous execution of HCI commands at probestage and use this function to check firmware state of Intel Wireless8260/8265 bluetooth devices found in many post 2016 year laptops.Attempt to initialize FreeBSD bluetooth stack while such a device is inbootloader mode locks the adapter hardly so it requires power on/offcycle to restore.This change blocks ng_ubt attachment unless operational firmware isloaded thus preventing the lock up.PR:			237083Reviewed by:		hps, emaxMFC after:		2 weeksDifferential Revision:	https://reviews.freebsd.org/D21071

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Mon, 09 Sep 2019 18:50:38 +0000</pubDate>
        <dc:creator>Vladimir Kondratyev &lt;wulf@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>785a7de2 - MFC r350685:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#785a7de2</link>
        <description>MFC r350685:Add cdceem(4) driver, for virtual ethernet devices compliantwith Communication Device Class Ethernet Emulation Model (CDC EEM).The driver supports both the device, and host side operation; thereis a new USB template (#11) for the former.This enables communication with virtual USB NIC provided by iLO 5,as found in new HPE Proliant servers.Reviewed by:	hselaskyRelnotes:	yesSponsored by:	Hewlett Packard Enterprise

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Fri, 06 Sep 2019 17:54:51 +0000</pubDate>
        <dc:creator>Edward Tomasz Napierala &lt;trasz@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>2f3cabf9 - MFC r345350, r346441, r346765</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#2f3cabf9</link>
        <description>MFC r345350, r346441, r346765r345350:Rename fuse(4) to fusefs(4)This makes it more consistent with other filesystems, which all end in &quot;fs&quot;,and more consistent with its mount helper, which is already named&quot;mount_fusefs&quot;.Reviewed by:	cem, rgrimesSponsored by:	The FreeBSD FoundationDifferential Revision:	https://reviews.freebsd.org/D19649r346441:Use symlinks for kernel modules rather than hardlinksWhen aliasing a kernel module to a different name (ie if_igb for if_em),it&apos;s better to use symlinks than hard links. kldxref will omit entries forthe links, ensuring that the loaded module has the correct name.Reviewed by:	impSponsored by:	The FreeBSD FoundationDifferential Revision:	https://reviews.freebsd.org/D19979r346765:Don&apos;t symlink fusefs.ko to fuse.ko on PPCSome PPC systems (PowerNV) use msdosfs for /boot, which can&apos;t handle eithersymlinks or hardlinks. So on PPC, copy the module instead. This change fixesinstallkernel on such systems after r345350.Reported by:	Brandon Bergren &lt;git_bdragon.rtk0.net&gt;Reviewed by:	jhibbits, rgrimesMFC-With:	345350, 346441Sponsored by:	The FreeBSD FoundationDifferential Revision:	https://reviews.freebsd.org/D19993

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Fri, 06 Sep 2019 17:21:21 +0000</pubDate>
        <dc:creator>Alan Somers &lt;asomers@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>4791c815 - MFC r351356:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#4791c815</link>
        <description>MFC r351356:  Create a AHCI attachment for nvme.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Thu, 05 Sep 2019 23:02:08 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>8f1b2aef - MFC r351355:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#8f1b2aef</link>
        <description>MFC r351355:  Separate the pci attachment from the rest of nvme

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Thu, 05 Sep 2019 23:01:12 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>e27633af - MFC r350591, r350971, r351724</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#e27633af</link>
        <description>MFC r350591, r350971, r351724r350591:Add a driver for Texas Instruments ADS101x/ADS111x i2c ADC chips.Instances of the device can be configured using hints or FDT data.Interfaces to reconfigure the chip and extract voltage measurements fromit are available via sysctl(8).r350971:Fix the driver name in ads111x.4, and hook the manpage up to the build.The driver was originally written with the name ads1115, but at the lastminute it got renamed to ads111x to reflect its support for many relatedchips, but I forgot to update the manpage to match the renaming beforecommitting it all.r351724:Fix the name of the devicetree bindings document file cited in the manpage.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Thu, 05 Sep 2019 16:37:10 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>17c2a30e - MFC r351488</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#17c2a30e</link>
        <description>MFC r351488netmap: remove obsolete fileThe netmap_pt.c module has become obsolete afterthe refactoring that added netmap_kloop.c.Remove it and unlink it from the build system.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Tue, 03 Sep 2019 18:04:45 +0000</pubDate>
        <dc:creator>Vincenzo Maffione &lt;vmaffione@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>35d47fa2 - MFC r349637 by ganbold:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#35d47fa2</link>
        <description>MFC r349637 by ganbold:Fix build error introduced by r349596.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Fri, 16 Aug 2019 21:28:28 +0000</pubDate>
        <dc:creator>Emmanuel Vadot &lt;manu@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>8f318f29 - MFC r349319, r349328-r349330</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#8f318f29</link>
        <description>MFC r349319, r349328-r349330r349319:Add some i2c slave-device drivers that were missing from NOTES.r349328:The gpiopps(4) driver currently has probe and attach code only for FDT basedsystems, so conditionalize it accordingly in conf/files.r349329:Add gpio(4) and related drivers to NOTES.r349330:Add pwm devices to NOTES.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Sun, 11 Aug 2019 21:15:30 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>597adbfe - MFC r349072, r349316-r349318</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#597adbfe</link>
        <description>MFC r349072, r349316-r349318r349072:Remove pcf8563reg.h, the driver it was associated with was replaced in 2017with the nxprtc multi-chip driver.r349316:Remove some unused header files from the ad7418 driver.r349317:Add the rtc8583 driver to conf/files.  Also, move sy8106a fromfile.allwinner to conf/files... it&apos;s not allwinner-specific, some dayother platforms could use the same regulator chip.r349318:The sy8106a and syr827 drviers require FDT and the ext_resources subsystem.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Sun, 11 Aug 2019 21:12:29 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>ed0429f4 - MFC r345817: Build NVMe CAM transport unrelated to NVMe SIM.</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#ed0429f4</link>
        <description>MFC r345817: Build NVMe CAM transport unrelated to NVMe SIM.Before this I suppose it was impossible load CAM-based NVMe as module.Plus this appeared to be needed to build r345815 without NVMe driver.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Thu, 08 Aug 2019 02:00:11 +0000</pubDate>
        <dc:creator>Alexander Motin &lt;mav@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>bb96de70 - MFC r342008, r342010-r342020</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#bb96de70</link>
        <description>MFC r342008, r342010-r342020r342008:fdt: Add support for simple-mfd busQuoting the binding Documentation :&quot;These devices comprise a nexus for heterogeneous hardware blocks containingmore than one non-unique yet varying hardware functionality.&quot;Reviewed by:	loosSponsored by:	Rubicon Communications, LLC (&quot;Netgate&quot;)Differential Revision:	https://reviews.freebsd.org/D17751r342010:arm64: Add new SoC type MARVELL_8KSponsored by:	Rubicon Communications, LLC (&quot;Netgate&quot;)r342011:arm64: mvebu_pinctrl: Add driver for Marvell Pinmux ControllerAdd a driver compatible with Marvell mvebu-pinctrl and add ap806-pinctrlsupport.Sponsored by:	Rubicon Communications, LCC (&quot;Netgate&quot;)r342012:arm64: marvell: Add driver for Marvell Ap806 System ControllerThe first two clocks are for the clusters and their frequencies can befound reading a register. Then a fixed 1200Mhz clock is present and twofixed clocks, &apos;mss&apos; which is 1200 / 6 and &apos;sdio&apos; which is 1200 / 3.Sponsored by:	Rubicon Communications, LLC (&quot;Netgate&quot;)r342013:arm64: mv_gpio: Add Marvell 8K supportWhile here put the interrupts setup in it&apos;s own functionSponsored by:	Rubicon Communications, LCC (&quot;Netgate&quot;)r342014:arm64: marvell: Add cp110 clock controller supportThe cp110 clock controller controls the clocks and gate of the CP110hardware block.Every clock/gate are implemented except the NAND clock.Sponsored by:	Rubicon Communications, LLC (&quot;Netgate&quot;)r342015:twsi: Clean up marvell part and add support for Marvell 7k/8kSponsored by:	Rubicon Communications, LLC (&quot;Netgate&quot;)r342016:arm64: Add mv_cp110_icu and mv_cp110_gicpicu is a interrupt concentrator in the CP110 block and gicpis a gic extension to allow interrupts in the CP block to be turnedinto GIC SPI interruptsSponsored by:	Rubicon Communications, LLC (&quot;Netgate&quot;)r342017:sdhci_xenon: Add Marvell 8k compatible stringSponsored by:	Rubicon Communications, LLC (&quot;Netgate&quot;)r342018:mv_gpio: Since it&apos;s also an interrupt controller, attach soonerSponsored by:	Rubicon Communications, LLC (&quot;Netgate&quot;)r342019:arm64: mv_cp110_icu: Fix buildr342020:mv_thermal: Add thermal driver for AP806 and CP110 thermal sensorSponsored by:	Rubicon Communications, LLC (&quot;Netgate&quot;)

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Mon, 05 Aug 2019 17:43:44 +0000</pubDate>
        <dc:creator>Emmanuel Vadot &lt;manu@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>e5d84f7f - MFC r340845-r340848, r340971, r340981, r342076</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#e5d84f7f</link>
        <description>MFC r340845-r340848, r340971, r340981, r342076r340845:Derive PHY class to new one specialized for USB PHY functions.Submitted by:	mmelr340846:aw_usbphy: Convert to usbphy subclassInstead of routing the phy when enabling it, do the configurationand routing in the phynode_usb_set_mode function.While here, if we don&apos;t have a vbus detection method, enable the phyif requested.r340847:a10_ehci: Always set the phy to host moder340848:axp8xx: Rework the enable part and add the GPIOXLDO regulatorsr340971:aw_usbphy: Do not error if it&apos;s not phy 0Only phy0 can switch between host/otg, do not error if we requesthost mode on phy != 0.X-MFC with:	r340846r340981:release: arm64: Add PINEBOOK configAdd a configuration for PINEBOOK image.Pinebook is a arm64 laptop based on a Pine64 board.Since the usb trackpad need a quirk, add a common function for addingquirk for arm board.A default one is supplied as most board to not need quirks.Reviewed by:	gjbDifferential Revision:	https://reviews.freebsd.org/D18337r342076:arm64: allwinner: axp81x: Fix double invertion for FLDO1This fix booting on A64 boards when disabling the unused regulators at boot.We did disable all the regulator handled by register 0x13 which of course containmandatory regulators for the board to be up.Reported by:	Mark Millard &lt;marklmi@yahoo.com&gt;X-MFC-With:	r340848

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Mon, 05 Aug 2019 16:36:11 +0000</pubDate>
        <dc:creator>Emmanuel Vadot &lt;manu@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>187f36e9 - MFC r343826, r346698, r349057-r349060, r349073-r349077, r349080-r349086, r349088,</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#187f36e9</link>
        <description>MFC r343826, r346698, r349057-r349060, r349073-r349077, r349080-r349086, r349088,    r349091-r349097, r349115, r349119, r349130-r349132, r349143-r349145,    r349164-r349168, r349174, r349269-r349273r343826 by yuripv:pwm.8: fix markup in synopsis, add -f descriptionr346698 by manu:arm: allwinner: aw_pwm: compile it as module toor349057:Allow pwm(9) components to be selected individually, while &apos;device pwm&apos;still includes it all.r349058:In detach(), check for failure of bus_generic_detach(), only releaseresources if they got allocated (because detach() gets called from attach()to handle various failures), and delete the pwmbus child if it got created.r349059:Don&apos;t call pwmbus_attach_bus(), because it may not be present if thisdriver is compiled into the kernel but pwmbus will be loaded as a modulewhen needed (and because of that, pwmbus_attach_bus() is going away inthe near future).  Instead, just directly do what that function did:register the fdt xfef handle, and attach the pwmbus.r349060:Handle failure to enable the clock or obtain its frequency.r349073:Do not include pwm.h here, it is purely a userland interface file containingioctl defintions for the pwmc driver. It is not part of the pwmbus interface.r349074:Move/rename the sys/pwm.h header file to dev/pwm/pwmc.h.  The file containsioctl definitions and related datatypes that allow userland control of pwmhardware via the pwmc device.  The new name and location better reflects itsassocation with a single device driver.r349075:Remove pwmbus_attach_bus(), it no longer has any callers.  Also remove acouple prototypes for functions that never existed (and never will).r349076:Use device_delete_children() instead of a locally-rolled copy of it thatleaks the device-list memory.r349077:Add a missing #include.  I suspect this used to get included via some headerpollution that was cleaned up recently, and this file got missed in thecleanup because it&apos;s not attached to the build unless you specificallyrequest this device in a custom kernel config.r349080:Make pwmbus driver and devclass vars static; they&apos;re not mentioned in anyheader file, so they can&apos;t be used outside this file anyway.r349081:Unwrap prototype lines so that return type and function name are on thesame line.  No functional changes.r349082:Spell unsigned int as u_int and channel as chan; eliminates the need to wrapsome long lines.r349083:Give the aw_pwm driver a module version.r349084:Rename the channel_max method to channel_count, because that&apos;s what it&apos;sreturning.  (If the channel count is 2, then the max channel number is 1.)r349085:Destroy the cdev on device detach.  Also, make the driver and devclassstatic, because nothing outside this file needs them.r349086:Restructure the pwm device hirearchy and interfaces.The pwm and pwmbus interfaces were nearly identical, this merges them into asingle pwmbus interface.  The pwmbus driver now implements the pwmbusinterface by simply passing all calls through to its parent (the hardwaredriver).  The channel_count method moves from pwm to pwmbus, and theget_bus method is deleted (just no longer needed).The net effect is that the interface for doing pwm stuff is now the sameregardless of whether you&apos;re a child of pwmbus, or some random driverelsewhere in the hierarchy that is bypassing the pwmbus layer and is talkingdirectly to the hardware driver via cross-hierarchy connections establishedusing fdt data.The pwmc driver is now a child of pwmbus, instead of being its sibling(that&apos;s why the get_bus method is no longer needed; pwmc now gets thedevice_t of the bus using device_get_parent()).r349088:Make pwm channel numbers unsigned.r349091:The pwm interface was replaced with pwmbus, include the right header file.r349092:Make channel number unsigned, and spell unsigned int u_int.  This shouldhave been part of r349088.r349093:This code no longer uses fdt/ofw stuff, no need to include ofw headers.r349094:Add module makefiles for pwm.r349095:Split the dtb MODULES_EXTRA line to a series of += lines, making it easierto maintain and keep in alphabetical order, and paving the way for addingsome other modules that aren&apos;t dtb-related.r349096:Add module makefiles for Texas Instruments ARM SoCs.The natural place to look for them based on how other SoCs are organizedwould be sys/modules/ti, but that&apos;s already taken.  Drop a clue intomodules/ti/Makefile directing people to modules/arm_ti if they&apos;re lookingfor ARM modules.r349097:Build SoC-specific modules with GENERIC for the SoCs that have them.r349115:Rename pwmbus.h to ofw_pwm.h, because after all the recent changes, thereis nothing left in the file that related to pwmbus at all.  It just containsprototypes for the functions implemented in dev/pwm.ofw_pwm.c, so name itaccordingly and fix the include protect wrappers to match.A new pwmbus.h will be coming along in a future commit.r349119:Rework pwmbus and pwmc so that each child will handle a single PWM channel.Previously, there was a pwmc instance for each instance of pwm hardwareregardless of how many pwm channels that hardware supported.  Now therewill be a pwmc instance for each channel when the hardware supportsmultiple channels.  With a separate instance for each channel, we can have&quot;named channels&quot; in userland by making devfs alias entries in /dev/pwm.These changes add support for ivars to pwmbus, and use an ivar to track thechannel number for each child.  It also adds support for hinted children.In pwmc, the driver checks for a label hint, and if present, it&apos;s used tocreate an alias for the cdev in /dev/pwm.  It&apos;s not anticipated that hintswill be heavily used, but it&apos;s easy to do and allows quick ad-hoc creationof named channels from userland by using kenv to create hint.pwmc.N.label=hints.  Upcoming changes will add FDT support, and most labels willprobably be specified that way.r349130:Add ofw_pwmbus to enumerate pwmbus devices on systems configured with fdtdata.  Also, add fdt support to pwmc.r349131:Implement the ofw_bus_get_node method in aw_pwm(4) so that ofw_pwmbus canfind its metadata for instantiating children.r349132:Add back a const qualifier I somehow fumbled away between test-buildingand committing recent changes.r349143:Put the pwmc cdev filenames under the pwm directory along with any labelnames.  I.e., everything related to pwm now goes in /dev/pwm.  This willmake it easier for userland tools to turn an unqualified name into a fullyqualified pathname, whether it&apos;s the base pwmcX.Y name or a label name.r349144:Follow changes in the pwmc(4) driver in relation to device filenames.The driver now names its cdev nodes pwmcX.Y where X is unit number andY is the channel within that unit.  Change the default device name frompwmc0 to pwmc0.0.  The driver now puts cdev files and label aliases inthe /dev/pwm directory, so allow the user to provide unqualified nameswith -f and automatically prepend the /dev/pwm part for them.Update the examples in the manpage to show the new device name formatand location within /dev/pwm.r349145:Put periods at the ends of argument descriptions.  Explain the relationshipbetween the period and duty arguments.r349164:Remove everything related to channels from the pwmc public interface, nowthat there is a pwmc(4) instance per channel and the channel number ismaintained as a driver ivar rather than being passed in from userland.r349165:Explain the relationship between PWM hardware channels being controlled andpwmc(4) device filenames.  Also, use uppercase PWM when the term is beingused as an acronym, and expand the acronym where it&apos;s first used.r349166:Rearrange the argument checking and processing so that enable and disablecan be combined with configuring the period and duty cycle (the same ioctlsets all 3 values at once, so there&apos;s no reason to require the user to runthe program twice to get all 3 things set).r349167:Oops, it seems I left out the word &apos;cycle&apos;, fix it.r349168:Add a pwmc(4) manpage.r349174:Handle labels specified with hints even on FDT systems.  Hints are theeasiest thing for a user to control (via loader.conf or kenv+kldload), sohandle them in addition to any label specified via the FDT data.r349269:Some mundane tweaks and cleanups to help de-clutter the diffs of someupcoming functional changes.Add an ofw_compat_data table for probing compat strings, and use it to addPNP data.  Remove some stray semicolons at the end of macro definitions,and add a PWM_LOCK_ASSERT macro to round out the usual suite.  Move thedevice_t and driver_methods structs to the end of the file.  Tweak comments.r349270:Add support for the PWM(9) API.  This allows configuring the pwm output usingpwm(9), but also maintains the historical sysctl config interface forcompatiblity with existing apps.  The two config systems are not compatiblewith each other; if you use both interfaces to change configurations you&apos;relikely to end up with incorrect output or none at all.r349271:Catch up with recent changes in pwmbus(9).  The pwm(9) and pwmbus(9)interfaces were unified into pwmbus(9), and the PWMBUS_CHANNEL_MAX methodwas renamed PWMBUS_CHANNEL_COUNT.  The pwmbus_attach_bus() function justwent away completely.  Also, fix a few typos such as s/is/if/.r349272:Do some general cleanup and light wordsmithing.Sort methods alphabetically.  Wrap long lines.  Start sentences on a newline.  Remove contractions (not because it&apos;s a good idea, just to silenceigor).  Add some explanation of the units for the period and duty argumentsand the convention for channel numbers.r349273:Add pwm to the armv7 GENERIC kernel, it&apos;s now used by TI and Allwinner.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Wed, 26 Jun 2019 17:28:55 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>ac07e6c7 - MFC r341268, r342003-r342007, r342087-r342088, r342091</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#ac07e6c7</link>
        <description>MFC r341268, r342003-r342007, r342087-r342088, r342091r341268 by manu:arm64: allwinner: Add a dtbo to have cpu operating pointsThis enables cpufreq on A64 boards.r342003 by manu:Add a pwm subsystem so we can configure pwm controller from kernel and userland.The pwm subsystem consist of API for PWM controllers, pwmbus to register themand a pwm(8) utility to talk to them from userland.Reviewed by:	oshgobo (capsicum), bcr (manpage), 0mp (manpage)Differential Revision:	https://reviews.freebsd.org/D17938r342004 by manu:arm64: allwinner: Add pwm driverAdd a pwm driver for Allwinner PWMAdd pwm and aw_pwm to the GENERIC kernelr342005 by manu:arm64: allwinner: Add DTSO for pwm and r_pwmThose are both dtso (overlays) for the two pwm controllers found on the A64.r342006 by manu:arm64: allwinner: Fix pwm dtsoDouble patched files ended up in the treeReported by:	kevansr342007 by manu:pwm: Fix some arches by using %ju and casting to uintmax_tReported by:	ci.freebsd.orgr342087 by manu:pwm: Convert period and duty to unsigned intWe don&apos;t need a 64 bits value to store nanosecondsDiscused with:	ian, jhibbitsr342088 by manu:pwm(8): Add percentage value support for duty cycler342091 by manu:allwinner: aw_pwm: Read value at attachThe booloaded might have configured the pwm controller so read the values.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Wed, 26 Jun 2019 15:34:35 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>0090dbfa - MFC r341386 (by manu):</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#0090dbfa</link>
        <description>MFC r341386 (by manu):Add Silergy SYR827 PMIC driverSYR827 is a PMIC that can output a voltage from 0.7125V to 1.5V in 12.5mV stepsIt&apos;s controlled via I2C.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Sun, 23 Jun 2019 16:05:53 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>420eca25 - MFC r347974, r348001, r348006, r348013, r348016, r348018, r348020</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#420eca25</link>
        <description>MFC r347974, r348001, r348006, r348013, r348016, r348018, r348020FDT support for if_muge and if_smsc drivers...r347974:Add common support functions for USB devices configured via FDT data.FDT data is sometimes used to configure usb devices which are hardwired intoan embedded system. Because the devices are instantiated by the usbenumeration process rather than by ofwbus iterating through the fdt data, itis somewhat difficult for a usb driver to locate fdt data that belongs toit. In the past, various ad-hoc methods have been used, which can lead toerrors such applying configuration that should apply only to a hardwireddevice onto a similar device attached by the user at runtime. For example,if the user adds an ethernet device that uses the same driver as the builtinethernet, both devices might end up with the same MAC address.These changes add a new usb_fdt_get_node() helper function that a driver canuse to locate FDT data that belongs to a single unique instance of thedevice. This function locates the proper FDT data using the mechanismdetailed in the standard &quot;usb-device.txt&quot; binding document [1].There is also a new usb_fdt_get_mac_addr() function, used to retrieve themac address for a given device instance from the fdt data. It usesusb_fdt_get_node() to locate the right node in the FDT data, and attempts toobtain the mac-address or local-mac-address property (in that order, thesame as linux does it).The existing if_smsc driver is modified to use the new functions, both as anexample and for testing the new functions. Rpi and rpi2 boards use thisdriver and provide the mac address via the fdt data.[1] https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/usb/usb-device.txtDifferential Revision:	https://reviews.freebsd.org/D20262r348001 by emaste:muge: configure LEDs per dtb (for Raspberry Pi 3B+)Also apply some style(9) and remove the message about EEPROM configuration(if there&apos;s an EEPROM the hardware handles LED configuration itself).PR:		237325Reviewed by:	ianSubmitted by:	Ralf &lt;iz-rpi03@hs-karlsruhe.de&gt;r348006 by emaste:muge: update FDT LED configurationAlso use LED mode settings from the FDT to set the PHY.From v3 of the patch submitted in the PR.I moved the sc_led_modes and sc_led_modes_mask default setting outsideof the #ifdef FDT case.PR:		237325Submitted by:	Ralf &lt;iz-rpi03@hs-karlsruhe.de&gt;Reviewed by:	ianMFC with:	r348001Event:		Waterloo Hackathon 2019Differential Revision:	https://reviews.freebsd.org/D20325r348013:Use the new usb fdt support functions to locate the proper fdt node forthe device instance, and to get the MAC address for the device instance.The ad-hoc code this replaces could find the wrong instance if multipledevices were present.r348016:Don&apos;t detour through sc-&gt;sc_ue when we have a direct pointer to ue in handalready.  Also, shorten a variable name for nicer line-wrapping.No functional changes.r348018:A MAC adddress from FDT data should override anything stored in eeprom orOTP registers (because the user is in control of the fdt data).  Remove theearly returns from the code that tries to find a good mac address, so thatthe execution always flows through the routine to get an address from FDTdata last, when on FDT-enabled systems.r348020:Reverse the bit logic of sc_led_modes_mask.  Instead of initializing it toall-ones then carving out blocks of zeroes where specified values go, initit to all-zeroes, put in ones where values need to be masked, then use itas value &amp;= ~sc_led_modes_mask.  In addition to being more idiomatic, thismeans everything related to FDT data is initialized to zero along with therest of the softc, and that allows removing some #ifdef FDT sections andwrapping the whole muge_set_leds() function in a single ifdef block.This also deletes the early-out from muge_set_leds() when an eeprom exists.Even if there is an eeprom with led config in it, the fdt data (if present)should override that, because the user is in control of the fdt data.

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Thu, 30 May 2019 14:40:23 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>92182fab - MFC r345405,345406,346228,346657,348195,348198: UART SPCR fixes.</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#92182fab</link>
        <description>MFC r345405,345406,346228,346657,348195,348198: UART SPCR fixes.r345405: Obey SPCR AccessWidth parameter.r345406: Initialize uart_bus_space_mem on arm64.r346228: Add quirk to ignore AccessWidth on PL011 UART.r346657: Handle SPCR BaudRate = 0.r348195: Extract arm64 SPCR code and make it MI; use on x86 too.r348198: Fix for r348195.This unbreaks the console on EC2 a1.* and *.metal instances.Sponsored by:	https://www.patreon.com/cperciva

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Tue, 28 May 2019 22:22:40 +0000</pubDate>
        <dc:creator>Colin Percival &lt;cperciva@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>9b6caabf - LinuxKPI: Register new linuxkpi and lindebugfs source files.</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/files#9b6caabf</link>
        <description>LinuxKPI: Register new linuxkpi and lindebugfs source files.This change is a partial MFC of r344487.Reviewed by:	hpsApproved by:	imp (mentor), hpsObtained from:	mmacy

            List of files:
            /freebsd-12.1/sys/conf/files</description>
        <pubDate>Sat, 25 May 2019 18:03:17 +0000</pubDate>
        <dc:creator>Johannes Lundberg &lt;johalun@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
