From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: Contributor meeting notes 19-Jan-21
Date: Wed, 20 Jan 2021 21:11:07 -0700 [thread overview]
Message-ID: <CAPnjgZ3nugDy0R8fdNJsPnRJ3HQDfROySsJAo-B+e--pEXudEg@mail.gmail.com> (raw)
In-Reply-To: <e1dd7721-c63b-3728-3e51-2eb378a41d4d@xilinx.com>
Hi Michal,
On Wed, 20 Jan 2021 at 08:50, Michal Simek <michal.simek@xilinx.com> wrote:
>
>
>
> On 1/20/21 4:44 PM, Simon Glass wrote:
> > Hi Michal,
> >
> > On Wed, 20 Jan 2021 at 00:46, Michal Simek <michal.simek@xilinx.com> wrote:
> >>
> >> Hi,
> >>
> >> On 1/19/21 7:54 PM, Simon Glass wrote:
> >>> Hi,
> >>>
> >>> Thank you for attending!
> >>>
> >>> Full notes at [1]
> >>>
> >>> Tuesday 19 January 2021
> >>>
> >>> Present: Daniel Schwierzeck, Heinrich Schuchardt, Michal Simek, Sean
> >>> Anderson, Simon Glass, Walter Lozano
> >>>
> >>> Notes:
> >>> [all] Introductions
> >>> [all] Timing of call
> >>> - Current time is the best across US, Europe, India. But not any good
> >>> for East Asia
> >>> - Simon might send out survey
> >>> - Send invitation to maintainer group - DONE
> >>> [Simon] New sequence numbers
> >>
> >> I can't see any issue with it on zynqmp platform. There is only issue
> >> with i2c which was there for quite a long time that i2c mux is
> >> considered as chip on the subbus as is visible below.
> >
> > Do you mean the naming of the device, or something else? What happens
> > if you type 'i2c bus'?
>
> If look at log below. mux is at address 74 which is i2c_mux_bus_drv
> and when you run i2c dev <any i2c mux channel> and run i2c probe i2c mux
> itself is assigned to to i2c_generic_chip_drv.
> Below you see it multiple times as generic_74 with ID 2/8/12/14/20. All
> of them are just targeting i2c mux.
That's strange. I wonder if it is failing to find it and creating
multiple copies?
+Heiko Schocher too
Regards,
Simon
next prev parent reply other threads:[~2021-01-21 4:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210119185647epcas1p28c1e9198cc00381af05c0e205ce8077b@epcas1p2.samsung.com>
2021-01-19 18:54 ` Contributor meeting notes 19-Jan-21 Simon Glass
2021-01-19 20:27 ` Marek Vasut
2021-01-19 23:44 ` Simon Glass
2021-01-20 0:25 ` Alex Sadovsky
2021-01-20 15:05 ` Marek Vasut
2021-01-21 8:14 ` Stefano Babic
2021-01-27 21:31 ` Simon Glass
2021-01-28 9:24 ` Stefano Babic
2021-02-09 4:29 ` Simon Glass
2021-01-27 21:31 ` Simon Glass
2021-01-20 1:55 ` Bin Meng
2021-01-21 10:41 ` Heinrich Schuchardt
2021-01-21 10:48 ` Michal Simek
2021-01-20 7:46 ` Michal Simek
2021-01-20 15:44 ` Simon Glass
2021-01-20 15:50 ` Michal Simek
2021-01-21 4:11 ` Simon Glass [this message]
2021-01-21 8:09 ` Michal Simek
2021-01-26 5:14 ` Heiko Schocher
2021-01-20 10:08 ` Igor Opaniuk
2021-01-20 10:12 ` Michal Simek
2021-01-20 10:19 ` Lukasz Majewski
2021-01-20 23:18 ` Jaehoon Chung
2021-01-20 23:25 ` Sean Anderson
2021-01-21 3:26 ` Simon Glass
2021-01-21 4:09 ` Jaehoon Chung
2021-01-21 8:05 ` Michal Simek
2021-01-21 9:13 ` Jaehoon Chung
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=CAPnjgZ3nugDy0R8fdNJsPnRJ3HQDfROySsJAo-B+e--pEXudEg@mail.gmail.com \
--to=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.