public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH] net: ravb: Fix NULL pointer access
Date: Sat, 19 Sep 2020 14:44:24 +0200	[thread overview]
Message-ID: <684dc047-8b62-942f-33f1-cd2626d99fb7@gmail.com> (raw)
In-Reply-To: <TYBPR01MB5309914AFBAFB11D3056F73D863C0@TYBPR01MB5309.jpnprd01.prod.outlook.com>

On 9/19/20 1:14 PM, Biju Das wrote:
[...]
>>> By looking at [1], only this driver is using writeext.
>>> [1]https://elixir.bootlin.com/u-boot/v2020.10-rc4/A/ident/writeext
>>
>> git grep indicates a couple more sites where the writeext is called.
>> But look into the KSZ9031 datasheet, that particular writeext call seems to be
>> setting up RGMII Clock Pad Skew (MMD Address 2, Register 8), and I think
>> there is a matching DT binding to set those up too, rxc-skew-ps and txc-
>> skew-ps I think.
> 
> Thanks for the pointers.  I checked the configs[2] which uses renesas ravb driver
> and found that we are defining only rxc-skew-ps in all dts.
> 
> since CONFIG DM_ETH is defined it is already picking the value corresponding to "rxc-skew-ps".
> 
> For txc-skew-ps anyway the value is default one. So we don't care.

Are you sure (0xf << 5) | 0x19 is the same as the default value of the
clock pad skew register ?

[...]

  reply	other threads:[~2020-09-19 12:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 14:10 [PATCH] net: ravb: Fix NULL pointer access Biju Das
2020-09-15 14:23 ` Michal Simek
2020-09-16 13:53 ` Marek Vasut
2020-09-16 15:43   ` Biju Das
2020-09-16 21:30     ` Marek Vasut
2020-09-18 15:26       ` Biju Das
2020-09-19  2:48         ` Marek Vasut
2020-09-19 11:14           ` Biju Das
2020-09-19 12:44             ` Marek Vasut [this message]
2020-09-19 18:14               ` Biju Das
2020-09-19 19:12                 ` Marek Vasut
2020-09-20  7:34                   ` Biju Das
2020-09-21 16:26                     ` Marek Vasut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=684dc047-8b62-942f-33f1-cd2626d99fb7@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox