<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/drivers/misc/Kconfig, branch dev-4.7</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.7</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.7'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2017-01-16T00:19:03+00:00</updated>
<entry>
<title>drivers/misc: Add Aspeed LPC control driver</title>
<updated>2017-01-16T00:19:03+00:00</updated>
<author>
<name>Cyril Bur</name>
<email>cyrilbur@gmail.com</email>
</author>
<published>2017-01-15T23:09:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=5ff1583c7ca2b413689288ff56ad51ed03747b30'/>
<id>urn:sha1:5ff1583c7ca2b413689288ff56ad51ed03747b30</id>
<content type='text'>
In order to manage server systems, there is typically another processor
known as a BMC (Baseboard Management Controller) which is responsible
for powering the server and other various elements, sometimes fans,
often the system flash.

The Aspeed BMC family which is what is used on OpenPOWER machines and a
number of x86 as well is typically connected to the host via an LPC
(Low Pin Count) bus (among others).

The LPC bus is an ISA bus on steroids. It's generally used by the
BMC chip to provide the host with access to the system flash (via MEM/FW
cycles) that contains the BIOS or other host firmware along with a
number of SuperIO-style IOs (via IO space) such as UARTs, IPMI
controllers.

On the BMC chip side, this is all configured via a bunch of registers
whose content is related to a given policy of what devices are exposed
at a per system level, which is system/vendor specific, so we don't want
to bolt that into the BMC kernel. This started with a need to provide
something nicer than /dev/mem for user space to configure these things.

One important aspect of the configuration is how the MEM/FW space is
exposed to the host (ie, the x86 or POWER). Some registers in that
bridge can define a window remapping all or portion of the LPC MEM/FW
space to a portion of the BMC internal bus, with no specific limits
imposed in HW.

I think it makes sense to ensure that this window is configured by a
kernel driver that can apply some serious sanity checks on what it is
configured to map.

In practice, user space wants to control this by flipping the mapping
between essentially two types of portions of the BMC address space:

   - The flash space. This is a region of the BMC MMIO space that
more/less directly maps the system flash (at least for reads, writes
are somewhat more complicated).

   - One (or more) reserved area(s) of the BMC physical memory.

The latter is needed for a number of things, such as avoiding letting
the host manipulate the innards of the BMC flash controller via some
evil backdoor, we want to do flash updates by routing the window to a
portion of memory (under control of a mailbox protocol via some
separate set of registers) which the host can use to write new data in
bulk and then request the BMC to flash it. There are other uses, such
as allowing the host to boot from an in-memory flash image rather than
the one in flash (very handy for continuous integration and test, the
BMC can just download new images).

It is important to note that due to the way the ASpeed chip lets the
kernel configure the mapping between host LPC addresses and BMC ram
addresses the offset within the window must be a multiple of size.
Not doing so will fragment the accessible space rather than simply
moving 'zero' upwards. This is caused by the nature of HICR8 being a
mask and the way host LPC addresses are translated.

Signed-off-by: Cyril Bur &lt;cyrilbur@gmail.com&gt;
[joel: Apply v3 from http://patchwork.ozlabs.org/patch/715545/ with
small fixes]
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>Revert "misc: Add Aspeed BT IPMI host driver"</title>
<updated>2016-11-10T11:31:13+00:00</updated>
<author>
<name>Cédric Le Goater</name>
<email>clg@kaod.org</email>
</author>
<published>2016-10-26T06:57:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=a7949ee6075238fbc28578c2f1c6f8c9de106035'/>
<id>urn:sha1:a7949ee6075238fbc28578c2f1c6f8c9de106035</id>
<content type='text'>
This reverts commit f7b4775fdf656f00f1b692bf3db97b3a8088c057.

Signed-off-by: Cédric Le Goater &lt;clg@kaod.org&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>misc: Add Aspeed BT IPMI host driver</title>
<updated>2016-08-09T06:22:16+00:00</updated>
<author>
<name>Alistair Popple</name>
<email>alistair@popple.id.au</email>
</author>
<published>2015-10-06T00:19:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=f7b4775fdf656f00f1b692bf3db97b3a8088c057'/>
<id>urn:sha1:f7b4775fdf656f00f1b692bf3db97b3a8088c057</id>
<content type='text'>
This patch adds a simple device driver to expose the iBT interface on
Aspeed chips as a character device (/dev/bt).

The iBT interface is used to perform in-band IPMI communication from a
BMC to the host.

Signed-off-by: Alistair Popple &lt;alistair@popple.id.au&gt;
Signed-off-by: Jeremy Kerr &lt;jk@ozlabs.org&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>Merge char-misc-next into staging-next</title>
<updated>2016-02-22T22:46:24+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2016-02-22T22:46:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=bb27d4998a9e8767674e8eda225c82cc149e5bc8'/>
<id>urn:sha1:bb27d4998a9e8767674e8eda225c82cc149e5bc8</id>
<content type='text'>
This resolves the merge issues and confusions people were having with
the goldfish drivers due to changes for them showing up in two different
trees.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc/bmp085: Enable building as a module</title>
<updated>2016-02-08T07:01:45+00:00</updated>
<author>
<name>Ben Hutchings</name>
<email>ben@decadent.org.uk</email>
</author>
<published>2015-12-14T14:29:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=50e6315dba721cbc24ccd6d7b299f1782f210a98'/>
<id>urn:sha1:50e6315dba721cbc24ccd6d7b299f1782f210a98</id>
<content type='text'>
Commit 985087dbcb02 'misc: add support for bmp18x chips to the bmp085
driver' changed the BMP085 config symbol to a boolean.  I see no
reason why the shared code cannot be built as a module, so change it
back to tristate.

Fixes: 985087dbcb02 ("misc: add support for bmp18x chips to the bmp085 driver")
Cc: Eric Andersson &lt;eric.andersson@unixphere.com&gt;
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: pch_phub: allow build on MIPS platforms</title>
<updated>2016-02-08T07:01:45+00:00</updated>
<author>
<name>Paul Burton</name>
<email>paul.burton@imgtec.com</email>
</author>
<published>2015-11-30T16:21:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=46fd8c3426c2de74966480f83ebc8a1ed59b9840'/>
<id>urn:sha1:46fd8c3426c2de74966480f83ebc8a1ed59b9840</id>
<content type='text'>
Allow the pch_phub driver to be build on MIPS platforms, in preparation
for its use on the MIPS Boston board.

Signed-off-by: Paul Burton &lt;paul.burton@imgtec.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: Move panel driver out of staging</title>
<updated>2016-02-03T22:14:22+00:00</updated>
<author>
<name>Ksenija Stanojevic</name>
<email>ksenija.stanojevic@gmail.com</email>
</author>
<published>2016-02-03T11:31:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=305b37bd01c220a7a6285911d43c9884270257be'/>
<id>urn:sha1:305b37bd01c220a7a6285911d43c9884270257be</id>
<content type='text'>
Move panel driver from drivers/staging/panel to drivers/misc.

Signed-off-by: Ksenija Stanojevic &lt;ksenija.stanojevic@gmail.com&gt;
Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: ibmasm: fix build errors</title>
<updated>2016-01-21T01:09:18+00:00</updated>
<author>
<name>Randy Dunlap</name>
<email>rdunlap@infradead.org</email>
</author>
<published>2016-01-20T22:58:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=75339d825ae5b1cd5bd6d4b1db3b4b7c12d7b3e9'/>
<id>urn:sha1:75339d825ae5b1cd5bd6d4b1db3b4b7c12d7b3e9</id>
<content type='text'>
Fix build when CONFIG_SERIAL_8250=m and CONFIG_IBM_ASM=y.

Fixes these build errors:

  drivers/built-in.o: In function `ibmasm_remove_one':
  module.c:(.text+0xf6874): undefined reference to `ibmasm_unregister_uart'
  drivers/built-in.o: In function `ibmasm_init_one':
  module.c:(.text+0xf6c37): undefined reference to `ibmasm_register_uart'

Signed-off-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;
Cc: Max Asbock &lt;masbock@us.ibm.com&gt;
Cc: Vernon Mauery &lt;vernux@us.ibm.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>VMware balloon: Enable notification via VMCI</title>
<updated>2015-10-04T11:59:11+00:00</updated>
<author>
<name>Philip P. Moltmann</name>
<email>moltmann@vmware.com</email>
</author>
<published>2015-08-06T22:18:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=48e3d668b7902cca3c61e9e2098e7f76b5646c28'/>
<id>urn:sha1:48e3d668b7902cca3c61e9e2098e7f76b5646c28</id>
<content type='text'>
Get notified immediately when a balloon target is set, instead of waiting for
up to one second.

The up-to 1 second gap could be long enough to cause swapping inside of the
VM that receives the VM.

Acked-by: Andy King &lt;acking@vmware.com&gt;
Signed-off-by: Xavier Deguillard &lt;xdeguillard@vmware.com&gt;
Tested-by: Siva Sankar Reddy B &lt;sankars@vmware.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ARM: qcom: Add coincell charger driver</title>
<updated>2015-07-29T20:37:18+00:00</updated>
<author>
<name>Tim Bird</name>
<email>tim.bird@sonymobile.com</email>
</author>
<published>2015-07-16T23:55:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=1f26d1c1053ac179b0ee1edea7809cef07fe728e'/>
<id>urn:sha1:1f26d1c1053ac179b0ee1edea7809cef07fe728e</id>
<content type='text'>
This driver is used to configure the coincell charger found in
Qualcomm PMICs.

The driver allows configuring the current-limiting resistor for
the charger, as well as the voltage to apply to the coincell
(or capacitor) when charging.

Signed-off-by: Tim Bird &lt;tim.bird@sonymobile.com&gt;
Reviewed-by: Andy Gross &lt;agross@codeaurora.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
