lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 18 Apr 2013 18:04:27 +0400
From:	Sergei Shtylyov <>
To:	Nobuhiro Iwamatsu <>
Subject: Re: [PATCH v6] net: sh_eth: Add support of device tree probe


On 17-04-2013 11:54, Nobuhiro Iwamatsu wrote:

>>>>>>> This adds support of device tree probe for Renesas sh-ether driver.

>>>>>>> Signed-off-by: Nobuhiro Iwamatsu <>


>>>>>>> @@ -2391,12 +2451,33 @@ static int sh_eth_drv_probe(struct platform_device
>>>>>>> *pdev)
>>>>>>> goto out_release;
>>>>>>> }
>>>>>>> + if (np) {
>>>>>>> + pd = sh_eth_parse_dt(&pdev->dev, ndev, np);
>>>>>>> + if (pdev->dev.platform_data && pd) {
>>>>>>> + struct sh_eth_plat_data *tmp =
>>>>>>> + pdev->dev.platform_data;
>>>>>>> + pd->set_mdio_gate = tmp->set_mdio_gate;
>>>>>>> + pd->needs_init = tmp->needs_init;

>>>>>> OK, so we can't fully convert this driver to the device tree due to
>>>>>> procedural platform data.

>>>>> > I then would advice just using OF_DEV_AUXDATA() in the platform data

>>>> /sdata/code/.

>>>>> instead of trying to convert the driver to device tree.

>>>> Convert the platfrom data, I meant. But I already wrote about that I think.

>>>>> Yes, I knew about this.

>>>> But still attempted to document and use the data-only device tree properties
>>>> (which was pointless in the light of procediral platfrom data)?

>>> Yes, I added this information to next patch.

>> WHich information, I didn't understand?

> sorry, I was not understand your mail by mistake.
> You believe that without OF_DEV_AUXDATA, that it should be fully migrated to
> the DT from platformdata. right?

    No, the contrary. OF_DEV_AUXDATA should be used and platfrom data 
therefore *not* be convereted to DT propertiies.

>>>>>>> +
>>>>>>> +#ifdef CONFIG_OF
>>>>>>> +static const struct of_device_id sh_eth_match[] = {
>>>>>>> + { .compatible = "renesas,sh-eth-gigabit", },
>>>>>>> + { .compatible = "renesas,sh-eth-sh4", },
>>>>>>> + { .compatible = "renesas,sh-eth-sh3-sh2", },

>>>>> Therefore, the compatible property of this device becomes <CPU>-sh-eth
>>>>> or <CPU>-sh-eth-<ETHER TYPE>.

>>>>> How about this?

>>>> Sounds better. I think however that the conversion of this driver to device
>>>> tree shouldn't be done without getting rid of the current #ifdef mess in it
>>>> (which is still on my agenda). I think that the 'register_type' field should
>>>> move from the platform data to the 'struct sh_eth_cpu_data' in the process.

>>> I see. this problem will fix next step, I think.

>> No, not at all. If we don't get rid of the #ifdef mess, adding device tree
>> support will have to add even more of it.

> But sh-eth was used by SH and sh-mobile.

    So what?

> I think we can migrate to DT.

    I don't think we should do it before removing the #ifdef's.

> However, I think it is not possible to remove idfef completely immediately.

    Immediately or not quite so, it was the task I was given.

>>> Best regards,
>>> Nobuhiro

WBR, Sergei

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists