MAJOR=10
MINOR=231
DEVNAME=snapshot
ˆ
ƒM·ÂÁÀ ¯
Index of /FSS-OZR/root/sys/dev/char/4:57/subsystem/tty24
Index of /FSS-OZR/root/sys/dev/char/4:57/subsystem/tty24
ˆ
ƒN·ÂÁÀ Ã
Index of /FSS-OZR/root/sys/dev/char/13:66/subsystem/input5/id
Index of /FSS-OZR/root/sys/dev/char/13:66/subsystem/input5/id
*
ˆl–Ü4ý( ©
³( Å€fàB¦-ÿ¿
ƒi—_†I|¥�+ÃÂ
/* SPDX-License-Identifier: GPL-2.0-or-later */
/* Copyright (C) 2021 ROHM Semiconductors */
#ifndef __LINUX_MFD_BD957X_H__
#define __LINUX_MFD_BD957X_H__
enum {
BD957X_VD50,
BD957X_VD18,
BD957X_VDDDR,
BD957X_VD10,
BD957X_VOUTL1,
BD957X_VOUTS1,
};
/*
* The BD9576 has own IRQ 'blocks' for:
* - I2C/thermal,
* - Over voltage protection
* - Short-circuit protection
* - Over current protection
* - Over voltage detection
* - Under voltage detection
* - Under voltage protection
* - 'system interrupt'.
*
* Each of the blocks have a status register giving more accurate IRQ source
* information - for example which of the regulators have over-voltage.
*
* On top of this, there is "main IRQ" status register where each bit indicates
* which of sub-blocks have active IRQs. Fine. That would fit regmap-irq main
* status handling. Except that:
* - Only some sub-IRQs can be masked.
* - The IRQ informs us about fault-condition, not when fault state changes.
* The IRQ line it is