[LinuxBIOS] where do board-specific superio settings belong?

[Ward Vandewege]

I'm planning to add some EC initialization to the it8716f superio that I
suspect to be specific for the board I'm working on (gigabyte m57sli-s4) -
the offsets for the thermal sensors to make them output sane values, etc.

In what file should those changes go? Somewhere under the
mainboard/gigabyte/m57sli directory I presume, but where would be the best
place, and from where should they be called?

Thanks,
Ward.

[yhlu]

in cache_as_ram_auto.c or mainboard.c

depends on if the initialization need it asap for example start the FAN asap

YH

On 5/1/07, Ward Vandewege  wrote:
> I'm planning to add some EC initialization to the it8716f superio that I
> suspect to be specific for the board I'm working on (gigabyte m57sli-s4) -
> the offsets for the thermal sensors to make them output sane values, etc.
>
> In what file should those changes go? Somewhere under the
> mainboard/gigabyte/m57sli directory I presume, but where would be the best
> place, and from where should they be called?
>
> Thanks,
> Ward.

[Ward Vandewege]

On Tue, May 01, 2007 at 12:59:40PM -0700, yhlu wrote:
> in cache_as_ram_auto.c or mainboard.c
>
> depends on if the initialization need it asap for example start the FAN asap

Actually the fans default to full-speed at power on, so that's not a problem.

I'm now working on the Tyan s2881 board. I need to set a few temperature
offsets for the adt7463 chip, again, specific for this motherboard.

I tried adding them to mainboard.c, but that is too early in the process; if
I add a mainboard_init there (hooked into the init action of
mainboard_operations), this code is executed quite a bit before the adt7463
chip is enabled, which is not what I want.

Is there a way to get mainboard specific code to be executed much later in
the boot process, after all devices have been enabled?

Thanks,
Ward.

[yhlu]

On 5/11/07, Ward Vandewege  wrote:
> On Tue, May 01, 2007 at 12:59:40PM -0700, yhlu wrote:
> I tried adding them to mainboard.c, but that is too early in the process; if
> I add a mainboard_init there (hooked into the init action of
> mainboard_operations), this code is executed quite a bit before the adt7463
> chip is enabled, which is not what I want.
>
> Is there a way to get mainboard specific code to be executed much later in
> the boot process, after all devices have been enabled?

two way
1. some thing like debug_dev. and you set the in your MB config. the
device will under mainboard/tyan/s2881/mb

2. in mainboard.c you allocate one device dynamcally, and make it the
under second link of root device. that will be the real last one..

YH

[Ward Vandewege]

On Fri, May 11, 2007 at 11:46:19AM -0700, yhlu wrote:
> On 5/11/07, Ward Vandewege  wrote:
> > On Tue, May 01, 2007 at 12:59:40PM -0700, yhlu wrote:
> > I tried adding them to mainboard.c, but that is too early in the process; 
> > if
> > I add a mainboard_init there (hooked into the init action of
> > mainboard_operations), this code is executed quite a bit before the adt7463
> > chip is enabled, which is not what I want.
> >
> > Is there a way to get mainboard specific code to be executed much later in
> > the boot process, after all devices have been enabled?
>
> two way
> some thing like debug_dev. and you set the in your MB config. the
>
> device will under mainboard/tyan/s2881/mb
> in mainboard.c you allocate one device dynamcally, and make it the
>
> under second link of root device. that will be the real last one..

Is there an example of another board doing something like this? I'm not sure
I understand the details of this.

Thanks,
Ward.

[Peter Stuge]

On Tue, May 01, 2007 at 02:31:19PM -0400, Ward Vandewege wrote:
> I'm planning to add some EC initialization to the it8716f superio
> that I suspect to be specific for the board I'm working on
> (gigabyte m57sli-s4) - the offsets for the thermal sensors to make
> them output sane values, etc.

We should think about this for v3 as well. Could defaults be set in
the superio dts with board-specific settings in the mainboard dts?

//Peter

[ron minnich]

On 5/1/07, Peter Stuge  wrote:
> We should think about this for v3 as well. Could defaults be set in
> the superio dts with board-specific settings in the mainboard dts?

there's not going to be a superio dts. All you get is the mainboard
dts. This is to avoid the config file confusion of V2 and V1.

ron

[Peter Stuge]

On Fri, May 11, 2007 at 04:20:45PM -0700, ron minnich wrote:
> > Could defaults be set in the superio dts with board-specific
> > settings in the mainboard dts?
>
> there's not going to be a superio dts. All you get is the mainboard
> dts. This is to avoid the config file confusion of V2 and V1.

Hm, ok, but where spec superio options that can be set in the
mainboard dts then?

//Peter

[Stefan Reinauer]

* Peter Stuge  [070514 02:57]:
> On Fri, May 11, 2007 at 04:20:45PM -0700, ron minnich wrote:
> > > Could defaults be set in the superio dts with board-specific
> > > settings in the mainboard dts?
> >
> > there's not going to be a superio dts. All you get is the mainboard
> > dts. This is to avoid the config file confusion of V2 and V1.
>
> Hm, ok, but where spec superio options that can be set in the
> mainboard dts then?

They are put as code into the mainboard dts at the moment.