linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] Fix mpc7448hpc2 tsi108 device_type bug
@ 2007-07-11  6:39 Zang Roy-r61911
  2007-07-11 11:55 ` Segher Boessenkool
  2007-07-12  7:39 ` Kumar Gala
  0 siblings, 2 replies; 6+ messages in thread
From: Zang Roy-r61911 @ 2007-07-11  6:39 UTC (permalink / raw)
  To: Paul Mackerras; +Cc: linuxppc-dev list, David Gibson

From: Roy Zang <tie-fei.zang@freescale.com>

Fix mpc7448hpc2 tsi108 device_type bug.
Wrong device type will break the board startup.

Signed-off-by: Roy Zang <tie-fei.zang@freescale.com>
---
Please apply this patch. The bug breaks the board
startup.
Please copy patches about 74xx and tsi bridge
to me.

 arch/powerpc/boot/dts/mpc7448hpc2.dts |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/powerpc/boot/dts/mpc7448hpc2.dts b/arch/powerpc/boot/dts/mpc7448hpc2.dts
index 0e3d314..b9158eb 100644
--- a/arch/powerpc/boot/dts/mpc7448hpc2.dts
+++ b/arch/powerpc/boot/dts/mpc7448hpc2.dts
@@ -45,7 +45,7 @@
 		#address-cells = <1>;
 		#size-cells = <1>;
 		#interrupt-cells = <2>;
-		device_type = "tsi108-bridge";
+		device_type = "tsi-bridge";
 		ranges = <00000000 c0000000 00010000>;
 		reg = <c0000000 00010000>;
 		bus-frequency = <0>;
-- 
1.5.1

^ permalink raw reply related	[flat|nested] 6+ messages in thread

* Re: [PATCH] Fix mpc7448hpc2 tsi108 device_type bug
  2007-07-11  6:39 [PATCH] Fix mpc7448hpc2 tsi108 device_type bug Zang Roy-r61911
@ 2007-07-11 11:55 ` Segher Boessenkool
  2007-07-11 14:59   ` Zang Roy-r61911
  2007-07-12  7:39 ` Kumar Gala
  1 sibling, 1 reply; 6+ messages in thread
From: Segher Boessenkool @ 2007-07-11 11:55 UTC (permalink / raw)
  To: Zang Roy-r61911; +Cc: linuxppc-dev list, Paul Mackerras, David Gibson

> Fix mpc7448hpc2 tsi108 device_type bug.
> Wrong device type will break the board startup.

> -		device_type = "tsi108-bridge";
> +		device_type = "tsi-bridge";

The OS code shouldn't use "device_type" at all for this,
but "compatible" instead.  You might want to fix that.
This patch is fine until you do of course.


Segher

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] Fix mpc7448hpc2 tsi108 device_type bug
  2007-07-11 11:55 ` Segher Boessenkool
@ 2007-07-11 14:59   ` Zang Roy-r61911
  2007-07-11 17:51     ` Segher Boessenkool
  0 siblings, 1 reply; 6+ messages in thread
From: Zang Roy-r61911 @ 2007-07-11 14:59 UTC (permalink / raw)
  To: Segher Boessenkool; +Cc: linuxppc-dev list, Paul Mackerras, David Gibson

On Wed, 2007-07-11 at 19:55, Segher Boessenkool wrote:
> > Fix mpc7448hpc2 tsi108 device_type bug.
> > Wrong device type will break the board startup.
> 
> > -             device_type = "tsi108-bridge";
> > +             device_type = "tsi-bridge";
> 
> The OS code shouldn't use "device_type" at all for this,
> but "compatible" instead.  You might want to fix that.
I can understand you. Should we separate it into two steps:
(1) Fix the bug in old style to ensure the  board work. I can see other
code in kernel tree will be affected by removing "device_type".
(2) Using compatible instead of device_type for all associated boards
and code.
> This patch is fine until you do of course.
That is fine.
Roy

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] Fix mpc7448hpc2 tsi108 device_type bug
  2007-07-11 14:59   ` Zang Roy-r61911
@ 2007-07-11 17:51     ` Segher Boessenkool
  0 siblings, 0 replies; 6+ messages in thread
From: Segher Boessenkool @ 2007-07-11 17:51 UTC (permalink / raw)
  To: Zang Roy-r61911; +Cc: linuxppc-dev list, Paul Mackerras, David Gibson

>>> Fix mpc7448hpc2 tsi108 device_type bug.
>>> Wrong device type will break the board startup.
>>
>>> -             device_type = "tsi108-bridge";
>>> +             device_type = "tsi-bridge";
>>
>> The OS code shouldn't use "device_type" at all for this,
>> but "compatible" instead.  You might want to fix that.
> I can understand you. Should we separate it into two steps:
> (1) Fix the bug in old style to ensure the  board work. I can see  
> other
> code in kernel tree will be affected by removing "device_type".
> (2) Using compatible instead of device_type for all associated boards
> and code.

Yes, good plan.

>> This patch is fine until you do of course.
> That is fine.

This is your step (1) :-)


Segher

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] Fix mpc7448hpc2 tsi108 device_type bug
  2007-07-11  6:39 [PATCH] Fix mpc7448hpc2 tsi108 device_type bug Zang Roy-r61911
  2007-07-11 11:55 ` Segher Boessenkool
@ 2007-07-12  7:39 ` Kumar Gala
  2007-07-12  8:17   ` Zang Roy-r61911
  1 sibling, 1 reply; 6+ messages in thread
From: Kumar Gala @ 2007-07-12  7:39 UTC (permalink / raw)
  To: Zang Roy-r61911; +Cc: linuxppc-dev list, Paul Mackerras, David Gibson


On Jul 11, 2007, at 1:39 AM, Zang Roy-r61911 wrote:

> From: Roy Zang <tie-fei.zang@freescale.com>
>
> Fix mpc7448hpc2 tsi108 device_type bug.
> Wrong device type will break the board startup.
>
> Signed-off-by: Roy Zang <tie-fei.zang@freescale.com>
> ---
> Please apply this patch. The bug breaks the board
> startup.
> Please copy patches about 74xx and tsi bridge
> to me.
>
>  arch/powerpc/boot/dts/mpc7448hpc2.dts |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/boot/dts/mpc7448hpc2.dts b/arch/powerpc/ 
> boot/dts/mpc7448hpc2.dts
> index 0e3d314..b9158eb 100644
> --- a/arch/powerpc/boot/dts/mpc7448hpc2.dts
> +++ b/arch/powerpc/boot/dts/mpc7448hpc2.dts
> @@ -45,7 +45,7 @@
>  		#address-cells = <1>;
>  		#size-cells = <1>;
>  		#interrupt-cells = <2>;
> -		device_type = "tsi108-bridge";
> +		device_type = "tsi-bridge";

Is there a reason we don't add:

                 compatible = "tsi108-bridge";

like the holly dts has?

- k

>  		ranges = <00000000 c0000000 00010000>;
>  		reg = <c0000000 00010000>;
>  		bus-frequency = <0>;
> -- 
> 1.5.1
>
>
>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] Fix mpc7448hpc2 tsi108 device_type bug
  2007-07-12  7:39 ` Kumar Gala
@ 2007-07-12  8:17   ` Zang Roy-r61911
  0 siblings, 0 replies; 6+ messages in thread
From: Zang Roy-r61911 @ 2007-07-12  8:17 UTC (permalink / raw)
  To: Kumar Gala; +Cc: linuxppc-dev list, Paul Mackerras, David Gibson

On Thu, 2007-07-12 at 15:39, Kumar Gala wrote:
> On Jul 11, 2007, at 1:39 AM, Zang Roy-r61911 wrote:
> 
> > From: Roy Zang <tie-fei.zang@freescale.com>
> >
> > Fix mpc7448hpc2 tsi108 device_type bug.
> > Wrong device type will break the board startup.
> >
> > Signed-off-by: Roy Zang <tie-fei.zang@freescale.com>
> > ---
> > Please apply this patch. The bug breaks the board
> > startup.
> > Please copy patches about 74xx and tsi bridge
> > to me.
> >
> >  arch/powerpc/boot/dts/mpc7448hpc2.dts |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/powerpc/boot/dts/mpc7448hpc2.dts b/arch/powerpc/ 
> > boot/dts/mpc7448hpc2.dts
> > index 0e3d314..b9158eb 100644
> > --- a/arch/powerpc/boot/dts/mpc7448hpc2.dts
> > +++ b/arch/powerpc/boot/dts/mpc7448hpc2.dts
> > @@ -45,7 +45,7 @@
> >               #address-cells = <1>;
> >               #size-cells = <1>;
> >               #interrupt-cells = <2>;
> > -             device_type = "tsi108-bridge";
> > +             device_type = "tsi-bridge";
> 
> Is there a reason we don't add:
> 
>                  compatible = "tsi108-bridge";
> 
> like the holly dts has?
I noticed it.
Until now, it does not affect the function.
I plan to update the mpc7448hpc2 dts file reflecting tsi109 chip.
I will add the compatible field in that patch.
Please apply this one first.
Roy

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2007-07-12  8:17 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-11  6:39 [PATCH] Fix mpc7448hpc2 tsi108 device_type bug Zang Roy-r61911
2007-07-11 11:55 ` Segher Boessenkool
2007-07-11 14:59   ` Zang Roy-r61911
2007-07-11 17:51     ` Segher Boessenkool
2007-07-12  7:39 ` Kumar Gala
2007-07-12  8:17   ` Zang Roy-r61911

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).