mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev <netdev@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	kernel <kernel@savoirfairelinux.com>, David <davem@davemloft.net>,
	Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next 6/9] net: dsa: mv88e6xxx: rework Switch MAC setter
Date: Fri, 8 Jul 2016 20:03:15 -0400 (EDT)	[thread overview]
Message-ID: <2075477569.472619.1468022595798.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <20160707135253.GO19800@lunn.ch>

Hi Andrew,

On Jul 7, 2016, at 9:52 AM, Andrew Lunn andrew@lunn.ch wrote:

>> Also, note that this indirect access is a single-register which doesn't
>> require to wait for the operation to complete (like Switch MAC, Trunk
>> Mapping, etc.), in contrary to multi-registers indirect accesses with
>> several busy operations (like ATU, VTU, etc.).
> 
> Are you sure about this? The DSDT polls bit 15 of the register.

Every single-register operation (with an "Update" bit, "pointer" and "data"
bits) execute in a single write operation and doesn't need to wait for
completion.

But multiple-register operations like ATU, VTU, etc. with a "Busy" bit,
Operation bits and data registers, do require and explicitly mention to wait
for the operation to complete (by polling the busy bit or via interrupt).

We could add checks but it doesn't sound necessary, we are not doing it for
others Update operations and a badly set switch MAC address would be easily
identifiable.

Thanks,

	Vivien

  reply	other threads:[~2016-07-09  0:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 12:57 [PATCH net-next 0/9] net: dsa: mv88e6xxx: STP and Global 2 cleanup Vivien Didelot
2016-07-07 12:57 ` [PATCH net-next 1/9] net: dsa: mv88e6xxx: remove basic function flags Vivien Didelot
2016-07-07 12:57 ` [PATCH net-next 2/9] net: dsa: mv88e6xxx: split setup of Global 1 and 2 Vivien Didelot
2016-07-07 12:57 ` [PATCH net-next 3/9] net: dsa: mv88e6xxx: extract device mapping Vivien Didelot
2016-07-07 14:55   ` kbuild test robot
2016-07-14 22:24     ` Vivien Didelot
2016-07-07 12:57 ` [PATCH net-next 4/9] net: dsa: mv88e6xxx: extract trunk mapping Vivien Didelot
2016-07-07 12:57 ` [PATCH net-next 5/9] net: dsa: mv88e6xxx: add cap for MGMT Enables bits Vivien Didelot
2016-07-07 12:57 ` [PATCH net-next 6/9] net: dsa: mv88e6xxx: rework Switch MAC setter Vivien Didelot
2016-07-07 13:52   ` Andrew Lunn
2016-07-09  0:03     ` Vivien Didelot [this message]
2016-07-07 12:57 ` [PATCH net-next 7/9] net: dsa: mv88e6xxx: add cap for PVT Vivien Didelot
2016-07-07 12:57 ` [PATCH net-next 8/9] net: dsa: mv88e6xxx: add cap for Priority Override Vivien Didelot
2016-07-07 12:57 ` [PATCH net-next 9/9] net: dsa: mv88e6xxx: add cap for IRL Vivien Didelot

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=2075477569.472619.1468022595798.JavaMail.zimbra@savoirfairelinux.com \
    --to=vivien.didelot@savoirfairelinux.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kernel@savoirfairelinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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

Powered by JetHome