On 4 February 2016 at 01:58, Timur Tabi <timur@xxxxxxxxxxxxxx> wrote: > Fu Wei wrote: >> >> I have posted GTDT support separately :https://lkml.org/lkml/2016/2/1/660 >> >> devicetree driver and GTDT driver both export sbsa gwdt info to >> "platform resource". >> >> this driver get hardware info from platform resource. > > > I must be missing something. How does the driver probe? It only has an maybe you miss a line of code for platform resource : --------------------- static const struct platform_device_id sbsa_gwdt_pdev_match[] = { { .name = "sbsa-gwdt", }, {}, }; MODULE_DEVICE_TABLE(platform, sbsa_gwdt_pdev_match); --------------------- > entry for device tree: > > + .of_match_table = sbsa_gwdt_of_match, > > Doesn't there need to be an ACPI match table to probe on an ACPI system? No, we don't. And this have been tested. -- Best regards, Fu Wei Software Engineer Red Hat Software (Beijing) Co.,Ltd.Shanghai Branch Ph: +86 21 61221326(direct) Ph: +86 186 2020 4684 (mobile) Room 1512, Regus One Corporate Avenue,Level 15, One Corporate Avenue,222 Hubin Road,Huangpu District, Shanghai,China 200021 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
