summaryrefslogtreecommitdiff
path: root/drivers/clk/st
diff options
context:
space:
mode:
authorjbrunet <jbrunet@baylibre.com>2016-12-19 15:05:38 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-07-05 12:40:20 (GMT)
commit8bface142a8d4bc5766bc71c94a618f234ed2bc6 (patch)
tree14681403cbe90914b0efc1707fe7b1054d8d7317 /drivers/clk/st
parent3897ae12b706bfc47c07a1eef58fe6ce328784cf (diff)
downloadlinux-8bface142a8d4bc5766bc71c94a618f234ed2bc6.tar.xz
dt: bindings: net: use boolean dt properties for eee broken modes
[ Upstream commit 308d3165d8b2b98d3dc3d97d6662062735daea67 ] The patches regarding eee-broken-modes was merged before all people involved could find an agreement on the best way to move forward. While we agreed on having a DT property to mark particular modes as broken, the value used for eee-broken-modes mapped the phy register in very direct way. Because of this, the concern is that it could be used to implement configuration policies instead of describing a broken HW. In the end, having a boolean property for each mode seems to be preferred over one bit field value mapping the register (too) directly. Cc: Florian Fainelli <f.fainelli@gmail.com> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/clk/st')
0 files changed, 0 insertions, 0 deletions