microchip,pic32ck-sg-gc-xosc32k

Description

PIC32CK_SG_GC External Crystal Oscillator (XOSC32K)

32.768 kHz External Crystal Oscillator (XOSC32K) Control.

Properties

Properties not inherited from the base binding file.

Name	Type	Details
`xosc32k-enable`	`int`	Oscillator enable control. 0: to disable, 1: to enable Default value: `0` Legal values: `0`, `1`
`xosc32k-xtal-en`	`int`	External clock or crystal oscillator selection. 0 - External clock connected on XIN. XOUT can be used as general-purpose I/O. 1 - Crystal connected to XIN/XOUT. Default value: `0` Legal values: `0`, `1`
`xosc32k-frequency`	`int`	Crystal frequency value. 32.768 kHz frequency. Default value: `0`
`xosc32k-on-demand-en`	`int`	On-demand oscillator control. 0: The oscillator is always on, if standby-en is true, else run in Standby Sleep mode if requested by a peripheral. 1: Run if requested by peripheral. Important: Initializing it with 1, along with clock enabled, can lead to indefinite wait for the clock to be on, if there is no peripheral request for the clock in the sequence of clock Initialization. If required, better to turn on the clock using API, instead of enabling both during startup. Default value: `0` Legal values: `0`, `1`
`xosc32k-control-gain-mode`	`string`	Control the gain of the external crystal oscillator. Default value: `lower-gain-mode-value` Legal values: `lower-gain-mode-value`, `higher-than-cgm0`, `higher-than-cgm1`, `higher-than-cgm2`, `higher-than-cgm3`, `higher-than-cgm4`, `higher-than-cgm5`, `higher-than-cgm6`, `higher-than-cgm7`, `higher-than-cgm8`, `higher-than-cgm9`, `higher-than-cgm10`, `higher-than-cgm11`, `higher-than-cgm12`, `higher-than-cgm13`, `highest-gain-mode-value`
`xosc32k-servo-loop-en`	`int`	XOSC32K servo loop control. 0 - enable 1 - disable Default value: `0` Legal values: `0`, `1`
`xosc32k-gain-boost`	`int`	XOSC32K gain boost control. 0 - enable 1 - disable Default value: `0` Legal values: `0`, `1`
`xosc32k-startup-time`	`int`	Oscillator Start-Up Time in ms Default value: `1000` Legal values: `0`, `1`, `2`, `63`, `125`, `250`, `500`, `1000`, `2000`, `4000`, `8000`
`xosc32k-rtc-clk-selection-en`	`int`	RTC clock source selection. 0: osculp32K 1: osculp1k 2: xosc32k 3: xosc1k Default value: `1`
`xosc32k-cfd-en`	`int`	Clock failure detector enable control. 0: to disable, 1: to enable Default value: `0` Legal values: `0`, `1`
`xosc32k-cfd-prescaler`	`int`	Clock failure detector prescaler. 0: The CFD safe clock frequency is the OSCULP32K frequency. 1: The CFD safe clock frequency is the OSCULP32K frequency divided by 2. Default value: `0` Legal values: `0`, `1`
`xosc32k-cfd-switchback-en`	`int`	Clock switch back control. 0: to disable, 1: to enable Default value: `0` Legal values: `0`, `1`

Properties inherited from the base binding file, which defines common properties that may be set on many nodes. Not all of these may apply to the “microchip,pic32ck-sg-gc-xosc32k” compatible.

Name	Type	Details
`status`	`string`	Indicates the operational status of the hardware or other resource that the node represents. In particular: - "okay" means the resource is operational and, for example, can be used by device drivers - "disabled" means the resource is not operational and the system should treat it as if it is not present For details, see "2.3.4 status" in Devicetree Specification v0.4. Legal values: `okay`, `disabled`, `reserved`, `fail`, `fail-sss` See Important properties for more information.
`compatible`	`string-array`	This property is a list of strings that essentially define what type of hardware or other resource this devicetree node represents. Each device driver checks for specific compatible property values to find the devicetree nodes that represent resources that the driver should manage. The recommended format is "vendor,device", The "vendor" part is an abbreviated name of the vendor. The "device" is usually from the datasheet. The compatible property can have multiple values, ordered from most- to least-specific. Having additional values is useful when the device is a specific instance of a more general family, to allow the system to match the most specific driver available. For details, see "2.3.1 compatible" in Devicetree Specification v0.4. This property is required. See Important properties for more information.
`reg`	`array`	Information used to address the device. The value is specific to the device (i.e. is different depending on the compatible property). The "reg" property is typically a sequence of (address, length) pairs. Each pair is called a "register block". Values are conventionally written in hex. For details, see "2.3.6 reg" in Devicetree Specification v0.4. See Important properties for more information.
`reg-names`	`string-array`	Optional names given to each register block in the "reg" property. For example: / { soc { #address-cells = <1>; #size-cells = <1>; uart@1000 { reg = <0x1000 0x2000>, <0x3000 0x4000>; reg-names = "foo", "bar"; }; }; }; The uart@1000 node has two register blocks: - one with base address 0x1000, size 0x2000, and name "foo" - another with base address 0x3000, size 0x4000, and name "bar"
`ranges`	`compound`	Information used to define a mapping (or translation) between the address space of a bus (the "child address space") and the address space of the bus node's parent (the "parent address space"). The "ranges" property is typically empty, or a sequence of triplets (child bus address, parent bus address, length). If the "ranges" property is empty, it specifies that the parent and child address spaces are identical and no address translation is required. If the "ranges" property is not present in a bus node, it is assumed that no mapping exists between children of the node and the parent address space. For details, see "2.3.8 ranges" in Devicetree Specification v0.4.
`interrupts`	`array`	Information about interrupts generated by the device, encoded as an array of one or more interrupt specifiers. The format of the data in this property varies by where the device appears in the interrupt tree. Devices with the same "interrupt-parent" will use the same format in their interrupts properties. For details, see "2.4 Interrupts and Interrupt Mapping" in Devicetree Specification v0.4. See Important properties for more information.
`interrupts-extended`	`compound`	Extended interrupt specifier for device, used as an alternative to the "interrupts" property. For details, see "2.4 Interrupts and Interrupt Mapping" in Devicetree Specification v0.4.
`interrupt-names`	`string-array`	Optional names given to each interrupt generated by a device. The interrupts themselves are defined in either "interrupts" or "interrupts-extended" properties. For details, see "2.4 Interrupts and Interrupt Mapping" in Devicetree Specification v0.4.
`interrupt-parent`	`phandle`	If present, this refers to the node which handles interrupts generated by this device. For details, see "2.4 Interrupts and Interrupt Mapping" in Devicetree Specification v0.4.
`label`	`string`	Human readable string describing the device. Use of this property is deprecated except as needed on a case-by-case basis. For details, see "4.1.2 Miscellaneous Properties" in Devicetree Specification v0.4. See Important properties for more information.
`clocks`	`phandle-array`	Information about the device's clock providers. In general, this property should follow conventions established in the dt-schema binding: https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
`clock-names`	`string-array`	Optional names given to each clock provider in the "clocks" property.
`#address-cells`	`int`	This property encodes the number of <u32> cells used by address fields in "reg" properties in this node's children. For details, see "2.3.5 #address-cells and #size-cells" in Devicetree Specification v0.4.
`#size-cells`	`int`	This property encodes the number of <u32> cells used by size fields in "reg" properties in this node's children. For details, see "2.3.5 #address-cells and #size-cells" in Devicetree Specification v0.4.
`dma-coherent`	`boolean`	Indicates that the device is capable of coherent DMA operations. For details, see "2.3.10 dma-coherent" in Devicetree Specification v0.4.
`dmas`	`phandle-array`	DMA channel specifiers relevant to the device.
`dma-names`	`string-array`	Optional names given to the DMA channel specifiers in the "dmas" property.
`dma-ranges`	`compound`	The dma-ranges provides a means of defining a mapping or translation between the physical address space of the bus and the physical address space of the parent of the bus. For details, see "2.3.9 dma-ranges" in Devicetree Specification v0.4.
`io-channels`	`phandle-array`	IO channel specifiers relevant to the device.
`io-channel-names`	`string-array`	Optional names given to the IO channel specifiers in the "io-channels" property.
`mboxes`	`phandle-array`	Mailbox / IPM channel specifiers relevant to the device.
`mbox-names`	`string-array`	Optional names given to the mbox specifiers in the "mboxes" property.
`power-domains`	`phandle-array`	Power domain specifiers relevant to the device.
`power-domain-names`	`string-array`	Optional names given to the power domain specifiers in the "power-domains" property.
`#power-domain-cells`	`int`	Number of cells in power-domains property
`hwlocks`	`phandle-array`	HW spinlock id relevant to the device.
`hwlock-names`	`string-array`	Optional names given to the hwlock specifiers in the "hwlocks" property.
`zephyr,deferred-init`	`boolean`	Do not initialize device automatically on boot. Device should be manually initialized using device_init().
`wakeup-source`	`boolean`	Property to identify that a device can be used as wake up source. When this property is provided a specific flag is set into the device that tells the system that the device is capable of wake up the system. Wake up capable devices are disabled (interruptions will not wake up the system) by default but they can be enabled at runtime if necessary.
`zephyr,pm-device-runtime-auto`	`boolean`	Automatically configure the device for runtime power management after the init function runs.
`zephyr,disabling-power-states`	`phandles`	List of power states that will disable this device power.