linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Christian Herzog <herzog-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Subject: Re: [lm-sensors] I2C support for AMD Hudson-1
Date: Thu, 16 Jan 2014 12:45:44 +0100	[thread overview]
Message-ID: <20140116124544.763415dd@endymion.delvare> (raw)
In-Reply-To: <20140109162421.GF25105-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>

Hi Christian,

On Thu, 9 Jan 2014 17:24:22 +0100, Christian Herzog wrote:
> sorry to bother you again, but this might save you some work: I just compiled
> 3.13.0-rc7 on the apu board and i2c works out of the box. I'm pretty stumped
> as I'm pretty sure it didn't work OOTB on -rc3, but now it does.. Are you
> aware of any Hudson-1 specific changes recently?

I am not aware of anything related to Hudson-1. I don't even know the
PCI IDs for that device.

The git history tells that there was no change to the i2c-piix4 driver
since kernel version 3.12-rc1. This is when support for secondary SMBus
on AMD SB800 and AMD FCH chipsets was added. I think FCH and Hudson-2
are the same thing, not sure how Hudson-1 fits into the picture.

Are you certain that the kernel version change fixed it? A BIOS update
could have helped as well, or even just changing some BIOS settings.

Another possibility is that some PCI or architecture quirk was added
meanwhile. However a quick search did not reveal anything between
3.13-rc3 and 3.13-rc7.

If you are really sure that 3.13-rc3 didn't work and 3.13-rc7 does
work, and you really want to understand why, then you can bisect the
git kernel tree between both points and it'll point you to the commit
that fixed it.

As for me, if things work for you now, I see no point in investigating
further. As Wolfram already pointed out, your contribution came in a
format we can't do anything with. The patch is huge, reversed, based on
a source file which had indentation changes, mixes actual changes with
(mostly unjustified) white-space changes, etc. If you ever need to get
changes into the kernel, please follow the rules listed in
Documentation/SubmittingPatches, otherwise nobody will review your
work, no matter how needed you think it is.

-- 
Jean Delvare

  parent reply	other threads:[~2014-01-16 11:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131217063226.GD25105@phys.ethz.ch>
     [not found] ` <20131217063226.GD25105-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>
2013-12-17 18:01   ` [lm-sensors] I2C support for AMD Hudson-1 Guenter Roeck
     [not found]     ` <20131217180131.GB2840-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-12-17 18:10       ` Wolfram Sang
2013-12-17 18:53         ` Jean Delvare
     [not found]           ` <20140106123105.GN25105@phys.ethz.ch>
     [not found]             ` <20140106140522.14e83454@endymion.delvare>
     [not found]               ` <20140109162421.GF25105@phys.ethz.ch>
     [not found]                 ` <20140109162421.GF25105-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>
2014-01-16 11:45                   ` Jean Delvare [this message]
     [not found]                     ` <20140116124544.763415dd-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-01-17  6:57                       ` Christian Herzog
2013-12-20 13:43         ` Christian Herzog
     [not found]           ` <20131220134349.GV25105-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org>
2014-01-13 13:04             ` Wolfram Sang
2014-01-13 13:12               ` Christian Herzog
2014-01-13 13:13               ` Jean Delvare

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=20140116124544.763415dd@endymion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=herzog-vpGm2Noi6jeZvKxeG3EEhw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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;
as well as URLs for NNTP newsgroup(s).