From: "Souza, Jose" <jose.souza@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/display: Use unions per platform in intel_dpll_hw_state
Date: Thu, 24 Feb 2022 13:49:36 +0000 [thread overview]
Message-ID: <d91dc9dc9f015a279dddfe45f88bd1ec0cbec013.camel@intel.com> (raw)
In-Reply-To: <YheHMunjbW0z4tg2@intel.com>
On Thu, 2022-02-24 at 15:25 +0200, Ville Syrjälä wrote:
> On Thu, Feb 24, 2022 at 01:17:35PM +0000, Souza, Jose wrote:
> > On Thu, 2022-02-24 at 12:20 +0200, Ville Syrjälä wrote:
> > > On Wed, Feb 23, 2022 at 12:55:51PM -0800, José Roberto de Souza wrote:
> > > <snip>
> > > > + union {
> > > > + /* icl+ TC */
> > > > + struct {
> > > > + u32 mg_refclkin_ctl;
> > > > + u32 mg_clktop2_coreclkctl1;
> > > > + u32 mg_clktop2_hsclkctl;
> > > > + u32 mg_pll_div0;
> > > > + u32 mg_pll_div1;
> > > > + u32 mg_pll_lf;
> > > > + u32 mg_pll_frac_lock;
> > > > + u32 mg_pll_ssc;
> > > > + u32 mg_pll_bias;
> > > > + u32 mg_pll_tdc_coldst_bias;
> > > > + u32 mg_pll_bias_mask;
> > > > + u32 mg_pll_tdc_coldst_bias_mask;
> > > > + };
> > > > +
> > > > + /* bxt */
> > > > + struct {
> > > > + /* bxt */
> > > > + u32 ebb0;
> > > > + u32 ebb4;
> > > > + u32 pll0;
> > > > + u32 pll1;
> > > > + u32 pll2;
> > > > + u32 pll3;
> > > > + u32 pll6;
> > > > + u32 pll8;
> > > > + u32 pll9;
> > > > + u32 pll10;
> > > > + u32 pcsdw12;
> > > > + };
> > >
> > > Wasn't there some funny compiler bug around anonymous unions?
> > > git log --grep='anon.*union' seems to agree. Please double check
> > > that stuff to make sure this is actually safe.
> >
> > I don't see any patch referring to compiler issues with 'git log --grep='anon.*union', what I see is other subsystems making use of it too.
> > Can you share the commit hash that you are referring to?
>
> $ git log --format=oneline --grep='anon.*union' -- drivers/gpu/drm/i915
>
I see issues with initialization of anonymous union but we don't initialize intel_dpll_hw_state.
Also it was fixed on GCC 4.6 that is older than current GCC requirement to build kernel(GCC 5.1).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10676
next prev parent reply other threads:[~2022-02-24 13:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 20:55 [Intel-gfx] [PATCH v2] drm/i915/display: Use unions per platform in intel_dpll_hw_state José Roberto de Souza
2022-02-24 10:20 ` Ville Syrjälä
2022-02-24 13:17 ` Souza, Jose
2022-02-24 13:25 ` Ville Syrjälä
2022-02-24 13:49 ` Souza, Jose [this message]
2022-02-24 15:39 ` Ville Syrjälä
2022-02-24 17:48 ` Souza, Jose
2022-02-24 17:55 ` Ville Syrjälä
2022-02-24 18:02 ` Imre Deak
2022-02-24 15:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: Use unions per platform in intel_dpll_hw_state (rev3) Patchwork
2022-02-24 16:02 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
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=d91dc9dc9f015a279dddfe45f88bd1ec0cbec013.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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