On 12/12/11, Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> On Fri, Dec 09, 2011 at 05:04:41PM +0100, Kamil Debski wrote:
>
>> index 236bbe1..5251e91 100644
>> --- a/arch/arm/mach-exynos/mach-nuri.c
>> +++ b/arch/arm/mach-exynos/mach-nuri.c
>> @@ -1262,6 +1262,7 @@ static struct platform_device *nuri_devices[]
>> __initdata = {
>> &s3c_device_i2c3,
>> &i2c9_gpio,
>> &s3c_device_adc,
>> + &s5p_device_g2d,
>
> For devices like g2d which are always part of the SoC and which don't
> require any external wiring on the board I was thinking we should just
> have the core code for the SoC register the device rather than including
> it in each board individually. It'd save effort and ensure that people
> automatically get to use the feature.
I'm welcome to use these scheme. make a common.c and register it automatically.
but I'm not sure we're ready to use this scheme. and I hope to start
these work at smdk board instead of this patch.
Thank you,
Kyungmin Park
>
> The crypto accelerators are another example of this - it's not really
> board specific if they're useful.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc"
> in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
