* [PATCH 7/7] common.c:105 Variable 'gephy' is never used. @ 2015-03-13 13:44 Ameen Ali 2015-03-13 14:08 ` Andrew Lunn 2015-03-13 14:19 ` Russell King - ARM Linux 0 siblings, 2 replies; 5+ messages in thread From: Ameen Ali @ 2015-03-13 13:44 UTC (permalink / raw) To: linux-arm-kernel Variable 'gephy' is assigned a value that is never used. Signed-off-by : <AmeenALi023@gmail.com> --- arch/arm/mach-dove/common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mach-dove/common.c b/arch/arm/mach-dove/common.c index 0d1a892..115a413 100644 --- a/arch/arm/mach-dove/common.c +++ b/arch/arm/mach-dove/common.c @@ -113,7 +113,7 @@ static void __init dove_clk_init(void) orion_clkdev_add(NULL, "orion_spi.1", tclk); orion_clkdev_add(NULL, "orion_wdt", tclk); orion_clkdev_add(NULL, "mv64xxx_i2c.0", tclk); - + orion_clkdev_add(NULL,"mv643xx_eth_port.0",gephy); orion_clkdev_add(NULL, "orion-ehci.0", usb0); orion_clkdev_add(NULL, "orion-ehci.1", usb1); orion_clkdev_add(NULL, "mv643xx_eth_port.0", ge); -- 2.1.0 ^ permalink raw reply related [flat|nested] 5+ messages in thread
* [PATCH 7/7] common.c:105 Variable 'gephy' is never used. 2015-03-13 13:44 [PATCH 7/7] common.c:105 Variable 'gephy' is never used Ameen Ali @ 2015-03-13 14:08 ` Andrew Lunn 2015-03-13 14:19 ` Russell King - ARM Linux 1 sibling, 0 replies; 5+ messages in thread From: Andrew Lunn @ 2015-03-13 14:08 UTC (permalink / raw) To: linux-arm-kernel On Fri, Mar 13, 2015 at 03:44:24PM +0200, Ameen Ali wrote: > Variable 'gephy' is assigned a value that is never used. > > Signed-off-by : <AmeenALi023@gmail.com> > --- > arch/arm/mach-dove/common.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/arm/mach-dove/common.c b/arch/arm/mach-dove/common.c > index 0d1a892..115a413 100644 > --- a/arch/arm/mach-dove/common.c > +++ b/arch/arm/mach-dove/common.c > @@ -113,7 +113,7 @@ static void __init dove_clk_init(void) > orion_clkdev_add(NULL, "orion_spi.1", tclk); > orion_clkdev_add(NULL, "orion_wdt", tclk); > orion_clkdev_add(NULL, "mv64xxx_i2c.0", tclk); > - > + orion_clkdev_add(NULL,"mv643xx_eth_port.0",gephy); It looks like you have used spaces, not a tab? Other than that, this looks sensible. Andrew > orion_clkdev_add(NULL, "orion-ehci.0", usb0); > orion_clkdev_add(NULL, "orion-ehci.1", usb1); > orion_clkdev_add(NULL, "mv643xx_eth_port.0", ge); > -- > 2.1.0 > ^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH 7/7] common.c:105 Variable 'gephy' is never used. 2015-03-13 13:44 [PATCH 7/7] common.c:105 Variable 'gephy' is never used Ameen Ali 2015-03-13 14:08 ` Andrew Lunn @ 2015-03-13 14:19 ` Russell King - ARM Linux 2015-03-13 14:48 ` Andrew Lunn 1 sibling, 1 reply; 5+ messages in thread From: Russell King - ARM Linux @ 2015-03-13 14:19 UTC (permalink / raw) To: linux-arm-kernel On Fri, Mar 13, 2015 at 03:44:24PM +0200, Ameen Ali wrote: > Variable 'gephy' is assigned a value that is never used. > > Signed-off-by : <AmeenALi023@gmail.com> > --- > arch/arm/mach-dove/common.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/arm/mach-dove/common.c b/arch/arm/mach-dove/common.c > index 0d1a892..115a413 100644 > --- a/arch/arm/mach-dove/common.c > +++ b/arch/arm/mach-dove/common.c > @@ -113,7 +113,7 @@ static void __init dove_clk_init(void) > orion_clkdev_add(NULL, "orion_spi.1", tclk); > orion_clkdev_add(NULL, "orion_wdt", tclk); > orion_clkdev_add(NULL, "mv64xxx_i2c.0", tclk); > - > + orion_clkdev_add(NULL,"mv643xx_eth_port.0",gephy); NAK. Just because some variable isn't read doesn't mean that you need to dream up some way to make it used. In any case, this is wrong because it will duplicate this entry: > orion_clkdev_add(NULL, "mv643xx_eth_port.0", ge); which means that 'gephy' will probably be returned instead of 'ge' for this device - and will cause the ethernet to stop working. Please leave the code as it was and ignore this assigned-to-but-unused variable. Thanks. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH 7/7] common.c:105 Variable 'gephy' is never used. 2015-03-13 14:19 ` Russell King - ARM Linux @ 2015-03-13 14:48 ` Andrew Lunn 2015-03-13 15:18 ` Russell King - ARM Linux 0 siblings, 1 reply; 5+ messages in thread From: Andrew Lunn @ 2015-03-13 14:48 UTC (permalink / raw) To: linux-arm-kernel On Fri, Mar 13, 2015 at 02:19:26PM +0000, Russell King - ARM Linux wrote: > On Fri, Mar 13, 2015 at 03:44:24PM +0200, Ameen Ali wrote: > > Variable 'gephy' is assigned a value that is never used. > > > > Signed-off-by : <AmeenALi023@gmail.com> > > --- > > arch/arm/mach-dove/common.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/arch/arm/mach-dove/common.c b/arch/arm/mach-dove/common.c > > index 0d1a892..115a413 100644 > > --- a/arch/arm/mach-dove/common.c > > +++ b/arch/arm/mach-dove/common.c > > @@ -113,7 +113,7 @@ static void __init dove_clk_init(void) > > orion_clkdev_add(NULL, "orion_spi.1", tclk); > > orion_clkdev_add(NULL, "orion_wdt", tclk); > > orion_clkdev_add(NULL, "mv64xxx_i2c.0", tclk); > > - > > + orion_clkdev_add(NULL,"mv643xx_eth_port.0",gephy); > > NAK. Just because some variable isn't read doesn't mean that you need > to dream up some way to make it used. > > In any case, this is wrong because it will duplicate this entry: > > > orion_clkdev_add(NULL, "mv643xx_eth_port.0", ge); Hi Russell Missed that. Sorry. What happens in the DT world is that ge clock is a child of the gephy clock, so that when you enable the ge clock, it walks up towards the parent and enables the gephy clock. I don't see anything like this in the legacy Dove world. Are you just relying on the bootloader turning on the phy and nothing turning it off? Andrew ^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH 7/7] common.c:105 Variable 'gephy' is never used. 2015-03-13 14:48 ` Andrew Lunn @ 2015-03-13 15:18 ` Russell King - ARM Linux 0 siblings, 0 replies; 5+ messages in thread From: Russell King - ARM Linux @ 2015-03-13 15:18 UTC (permalink / raw) To: linux-arm-kernel On Fri, Mar 13, 2015 at 03:48:40PM +0100, Andrew Lunn wrote: > On Fri, Mar 13, 2015 at 02:19:26PM +0000, Russell King - ARM Linux wrote: > > On Fri, Mar 13, 2015 at 03:44:24PM +0200, Ameen Ali wrote: > > > Variable 'gephy' is assigned a value that is never used. > > > > > > Signed-off-by : <AmeenALi023@gmail.com> > > > --- > > > arch/arm/mach-dove/common.c | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > diff --git a/arch/arm/mach-dove/common.c b/arch/arm/mach-dove/common.c > > > index 0d1a892..115a413 100644 > > > --- a/arch/arm/mach-dove/common.c > > > +++ b/arch/arm/mach-dove/common.c > > > @@ -113,7 +113,7 @@ static void __init dove_clk_init(void) > > > orion_clkdev_add(NULL, "orion_spi.1", tclk); > > > orion_clkdev_add(NULL, "orion_wdt", tclk); > > > orion_clkdev_add(NULL, "mv64xxx_i2c.0", tclk); > > > - > > > + orion_clkdev_add(NULL,"mv643xx_eth_port.0",gephy); > > > > NAK. Just because some variable isn't read doesn't mean that you need > > to dream up some way to make it used. > > > > In any case, this is wrong because it will duplicate this entry: > > > > > orion_clkdev_add(NULL, "mv643xx_eth_port.0", ge); > > Hi Russell > > Missed that. Sorry. > > What happens in the DT world is that ge clock is a child of the gephy > clock, so that when you enable the ge clock, it walks up towards the > parent and enables the gephy clock. > > I don't see anything like this in the legacy Dove world. Are you just > relying on the bootloader turning on the phy and nothing turning it > off? See, this is why I hate these trivial patches - they waste people's time and create a load of unnecessary confusion where there's absolutely none needed. Here's the legacy code: gephy = dove_register_gate("gephy", "tclk", CLOCK_GATING_BIT_GIGA_PHY); Here, we have a gate controlled by the CLOCK_GATING_BIT_GIGA_PHY bit between the tclk, and gephy clock. This is immediately followed by: ge = dove_register_gate("ge", "gephy", CLOCK_GATING_BIT_GBE); which is a gate controlled by the CLOCK_GATING_BIT_GBE bit between the gephy clock and the ge clock. This second clock is then registered for use by the ethernet device: orion_clkdev_add(NULL, "mv643xx_eth_port.0", ge); If we look at clk_summary, we see: tclk 12 12 166666667 0 0 gephy 1 1 166666667 0 0 ge 1 1 166666667 0 0 which is the same relationship as in DT: tclk 13 13 166666667 0 0 gephy 1 1 166666667 0 0 ge 2 2 166666667 0 0 There is no problem here; this has been a complete waste of our time while we discuss this non-problem. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-03-13 15:18 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2015-03-13 13:44 [PATCH 7/7] common.c:105 Variable 'gephy' is never used Ameen Ali 2015-03-13 14:08 ` Andrew Lunn 2015-03-13 14:19 ` Russell King - ARM Linux 2015-03-13 14:48 ` Andrew Lunn 2015-03-13 15:18 ` Russell King - ARM Linux
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).