aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/mt7621_beeline_smartbox-flash.dts
blob: d373a801d2f15c4fcdfd0530e34c95128596ad04 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT

#include "mt7621_arcadyan_wg4xx223.dtsi"

/ {
	compatible = "beeline,smartbox-flash", "mediatek,mt7621-soc";
	model = "Beeline SmartBox Flash";

	leds {
		led-0 {
			label = "blue:wan";
			color = <LED_COLOR_ID_BLUE>;
			function = LED_FUNCTION_WAN;
			gpios = <&gpio 14 GPIO_ACTIVE_LOW>;
		};
	};
};
ore a feature is in a release, it is not covered by this policy and may change. Security ~~~~~~~~ One exception to our API stability policy is for security. We will violate this policy as necessary in order to resolve a security issue or harden ``cryptography`` against a possible attack. Deprecation ----------- From time to time we will want to change the behavior of an API or remove it entirely. In that case, here's how the process will work: * In ``cryptography X.Y`` the feature exists. * In ``cryptography X.Y+1`` using that feature will emit a ``PendingDeprecationWarning``. * In ``cryptography X.Y+2`` using that feature will emit a ``DeprecationWarning``. * In ``cryptography X.Y+3`` the feature will be removed or changed. In short, code that runs without warnings will always continue to work for a period of two releases.