PCI config

[Myles Watson]

The attached patch fixes booting for arima/hdama.

How should we really fix it?  In v3 didn't we just scrap type 2 accesses all
together?

Thanks,
Myles

[Stefan Reinauer]

Myles Watson wrote:
> The attached patch fixes booting for arima/hdama.
>
> How should we really fix it?  In v3 didn't we just scrap type 2
> accesses all together?

We can keep the type 2 support code, but the auto detection at run time
makes absolutely no sense.

I sent a patch for this some days ago, but I think Carl-Daniel didn't
have too much success with it on his board.

Stefan

[Myles Watson]

> > How should we really fix it?  In v3 didn't we just scrap type 2
> > accesses all together?
>
> We can keep the type 2 support code, but the auto detection at run time
> makes absolutely no sense.
>
> I sent a patch for this some days ago, but I think Carl-Daniel didn't
> have too much success with it on his board.

Maybe we could simplify it a little and try again.  It looks like the rs690
changes were pretty extensive.

Thanks,
Myles

[Stefan Reinauer]

Myles Watson wrote:
> > > How should we really fix it?  In v3 didn't we just scrap type 2
> > > accesses all together?
> >
> > We can keep the type 2 support code, but the auto detection at run time
> > makes absolutely no sense.
> >
> > I sent a patch for this some days ago, but I think Carl-Daniel didn't
> > have too much success with it on his board.
>
> Maybe we could simplify it a little and try again.  It looks like the rs690
> changes were pretty extensive.

Generally, we should also change the mainboard code to access pci
devices in ->init, not in ->enable. This should solve the issues.

Then, dropping auto detect could be the next step.

[Myles Watson]

> Myles Watson wrote:
> > > > How should we really fix it?  In v3 didn't we just scrap type 2
> > > > accesses all together?
> > >
> > > We can keep the type 2 support code, but the auto detection at run time
> > > makes absolutely no sense.
> > >
> > > I sent a patch for this some days ago, but I think Carl-Daniel didn't
> > > have too much success with it on his board.
> >
> > Maybe we could simplify it a little and try again.  It looks like the
>
> rs690
> > changes were pretty extensive.
>
> Generally, we should also change the mainboard code to access pci
> devices in ->init, not in ->enable. This should solve the issues.

I thought enable was run at the very beginning, before scan, while init was
run at the end.  That seems like a hard conversion to make.

Thanks,
Myles

[Stefan Reinauer]

Myles Watson wrote:
> I thought enable was run at the very beginning, before scan, while init was
> run at the end.

Yes.
> That seems like a hard conversion to make.

Why?

Stefan

[Myles Watson]

On Thu, Oct 22, 2009 at 9:36 AM, Stefan Reinauer wrote:
> Myles Watson wrote:
> > I thought enable was run at the very beginning, before scan, while init
>
> was
> > run at the end.
>
> Yes.
> > That seems like a hard conversion to make.
>
> Why?

I thought that some of the PCI accesses were to set things up before
scanning the bus and reading the resources.  If we change the order
drastically, we will probably break all kinds of assumptions.

Thanks,
Myles

[Myles Watson]

> Myles Watson wrote:
> > The attached patch fixes booting for arima/hdama.
> >
> > How should we really fix it?  In v3 didn't we just scrap type 2
> > accesses all together?
>
> We can keep the type 2 support code, but the auto detection at run time
> makes absolutely no sense.

The auto detection code is the only place the type 2 struct is referenced.

Thanks,
Myles

[Carl-Daniel Hailfinger]

On 22.10.2009 09:57, Stefan Reinauer wrote:
> Myles Watson wrote:
> > The attached patch fixes booting for arima/hdama.
> >
> > How should we really fix it?  In v3 didn't we just scrap type 2
> > accesses all together?
>
> We can keep the type 2 support code, but the auto detection at run time
> makes absolutely no sense.
>
> I sent a patch for this some days ago, but I think Carl-Daniel didn't
> have too much success with it on his board.

Yes, if I applied the complete patch, the board was hanging. If I
applied parts of the patch (the rs690 part), the board still was
hanging, but I think that was due to a device tree code bug/limitation.
I can dig up the details if you want, becase the patch itself looked
desirable.

Regards,
Carl-Daniel

[Myles Watson]

On Thu, Oct 22, 2009 at 9:45 AM, Carl-Daniel Hailfinger <
[e-mail]> wrote:
> On 22.10.2009 09:57, Stefan Reinauer wrote:
> > Myles Watson wrote:
> > > The attached patch fixes booting for arima/hdama.
> > >
> > > How should we really fix it?  In v3 didn't we just scrap type 2
> > > accesses all together?
> >
> > We can keep the type 2 support code, but the auto detection at run time
> > makes absolutely no sense.
> >
> > I sent a patch for this some days ago, but I think Carl-Daniel didn't
> > have too much success with it on his board.
>
> Yes, if I applied the complete patch, the board was hanging. If I
> applied parts of the patch (the rs690 part), the board still was
> hanging, but I think that was due to a device tree code bug/limitation.
> I can dig up the details if you want, becase the patch itself looked
> desirable.

What if you just take out the init call in the enable function?

Modified patch attached.

Thanks,
Myles