Rotate a 3D vector on a plane

This solution might be quite specific to your needs.

As mentioned in the comments, it is probably best to have a mainshorthand for the inreference that can be inherited from the mvreference.

This is done via a custom data model file called refinherit.dbx, you will have to place this file somewhere LaTeX can find it.

\ProvidesFile{refinherit.dbx}[2014/04/03]
\RequireBiber[3]

\DeclareDatamodelFields[type=field,datatype=literal]{mainshorthand}
\DeclareDatamodelEntryfields{mainshorthand}
\endinput

In the MWE below this is achieved with filecontents, obviously you will have the file in an appropriate place in your actual use case.

We load this datamodel via the datamodel option

\usepackage[style=verbose-ibid, backend=biber, datamodel=refinherit]{biblatex}

We then declare the inheritance

\DeclareDataInheritance{mvreference}{inreference,reference}{%
  \inherit{shorthand}{mainshorthand}
  \noinherit{volumes}
}

That is, mvreference's shorthand becomes inreference's mainshorthand

Finally, we modify the inreference driver to omit some information and print the mainshorthand instead if that is available

\DeclareBibliographyDriver{inreference}{%
  \usebibmacro{bibindex}%
  \usebibmacro{begentry}%
  \usebibmacro{author/translator+others}%
  \setunit{\labelnamepunct}\newblock
  \printtext{Art.}%added
  \newunit%added
  \usebibmacro{title}%
  \newunit
  \printlist{language}%
  \newunit\newblock
  \usebibmacro{byauthor}%
  \newunit\newblock
  \usebibmacro{in:}%
  \iffieldundef{mainshorthand}
    {\usebibmacro{maintitle+booktitle}%
     \usebibmacro{byeditor+others}%
     \newunit\newblock
     \printfield{edition}}%
    {\printfield{mainshorthand}}%
  \newunit
  \printfield{volume}%
  \printfield{part}%
  \newunit
  \iffieldundef{mainshorthand}
    {\printfield{volumes}%
     \newunit\newblock
     \usebibmacro{series+number}%
     \newunit\newblock
     \printfield{note}%
     \newunit\newblock
     \usebibmacro{publisher+location+date}}%
    {}%
  \newunit\newblock
  \usebibmacro{chapter+pages}%
  \newunit\newblock
  \iftoggle{bbx:isbn}
    {\printfield{isbn}}
    {}%
  \newunit\newblock
  \usebibmacro{doi+eprint+url}%
  \newunit\newblock
  \usebibmacro{addendum+pubstate}%
  \setunit{\bibpagerefpunct}\newblock
  \usebibmacro{pageref}%
  \newunit\newblock
  \iftoggle{bbx:related}
    {\usebibmacro{related:init}%
     \usebibmacro{related}}
    {}%
  \usebibmacro{finentry}}

MWE

\documentclass[ngerman]{article}
\usepackage{filecontents}
\begin{filecontents*}{refinherit.dbx}
\ProvidesFile{refinherit.dbx}[2014/04/03]
\RequireBiber[3]

\DeclareDatamodelFields[type=field,datatype=literal]{mainshorthand}
\DeclareDatamodelEntryfields{mainshorthand}
\endinput
\end{filecontents*}
\usepackage{babel}
\usepackage{csquotes}
\usepackage[style=verbose-ibid, backend=biber, datamodel=refinherit]{biblatex}

\begin{filecontents*}{\jobname.bib}
@mvreference{NG,
  title       = {The new Grove dictionary of music and musicians},
  editor      = {Stanley Sadie},
  editora     = {Grove, George},
  editoratype = {founder},
  year        = {1980},
  volumes     = {20},
  shorthand   = {NG},
  location    = {London},
  publisher   = {Macmillan},
}

@reference{NG-BD11,
  crossref  = {NG},
  title     = {Lindeman -- Mean-tone},
  volume    = {11},
  year      = {1980},
}

@inreference{author-NG-ML,
  crossref  = {NG-BD11},
  author    = {Arnold Uthor},
  title     = {Firstname Lastname},
  pages     = {30--40},
}

\end{filecontents*}
\addbibresource{\jobname.bib}

\DeclareDataInheritance{mvreference}{inreference,reference}{%
  \inherit{shorthand}{mainshorthand}
  \noinherit{volumes}
}

%what to print out?
\DeclareBibliographyDriver{inreference}{%
  \usebibmacro{bibindex}%
  \usebibmacro{begentry}%
  \usebibmacro{author/translator+others}%
  \setunit{\labelnamepunct}\newblock
  \printtext{Art.}%added
  \newunit%added
  \usebibmacro{title}%
  \newunit
  \printlist{language}%
  \newunit\newblock
  \usebibmacro{byauthor}%
  \newunit\newblock
  \usebibmacro{in:}%
  \iffieldundef{mainshorthand}
    {\usebibmacro{maintitle+booktitle}%
     \usebibmacro{byeditor+others}%
     \newunit\newblock
     \printfield{edition}}%
    {\printfield{mainshorthand}}
  \newunit
  \printfield{volume}%
  \printfield{part}%
  \newunit
  \iffieldundef{mainshorthand}
    {\printfield{volumes}%
     \newunit\newblock
     \usebibmacro{series+number}%
     \newunit\newblock
     \printfield{note}%
     \newunit\newblock
     \usebibmacro{publisher+location+date}}%
    {}%
  \newunit\newblock
  \usebibmacro{chapter+pages}%
  \newunit\newblock
  \iftoggle{bbx:isbn}
    {\printfield{isbn}}
    {}%
  \newunit\newblock
  \usebibmacro{doi+eprint+url}%
  \newunit\newblock
  \usebibmacro{addendum+pubstate}%
  \setunit{\bibpagerefpunct}\newblock
  \usebibmacro{pageref}%
  \newunit\newblock
  \iftoggle{bbx:related}
    {\usebibmacro{related:init}%
     \usebibmacro{related}}
    {}%
  \usebibmacro{finentry}}


\begin{document}
\nocite{*}
\noindent{}The author wrote something about my subject.\autocite[35]{author-NG-ML}
\printshorthands
\printbibliography[nottype=mvreference, nottype=reference]
\end{document}

-- "Old" question, I know, but still wanted to answer, on this, the eve of my return --

The filtering is most likely intended to keep the VDDCORE noise out of the VDDPLL, to increase its accuracy.

As such the values are probably calculated for its likely-to-be-used core clock speed.

Usually in the Design Checklist they use values that are calculated and rounded to known values that offer slightly better filtering. Of course, it is up to you or any other designer to decide if you can do with less filtering (because your core speed is going to stay above a certain level, for example), or need more (because you will also use lower speeds or heavy I/O at lower speeds).

Generally Atmel's dev-board engineers try to err on the safe side, so I can imagine them just upping the filtering properties.

The series R on the large cap is a little smothering trick, whose value is generally dictated inside a reasonable window by the cap (and inductor)'s sizes, so it's no real wonder the R increases, although not exactly to the same factor.

If you want you can try to leave out the filtering, but you should expect some clock jitter here and there, whether that's a problem for you, is up to you. Although some of the hardware in the SAM might very much not like the jitter in a bad way, so if you're not sure what the parameters on that are for all the internals you will be activating, best to keep the filtering in.

Want to be safe? Take the dev-board values. Want a calculated good value at slightly lower component cost? The design guide will do you just fine in just about all cases I can vividly imagine.